Novell Problem

kimjm

ADSM.ORG Member
Joined
Oct 29, 2003
Messages
3
Reaction score
0
Points
0
Website
Visit site
We are running NetWare 5.1 SP6 along with eDirectory 8.6.2 SP4. We are running TSM client version 4.2.3.0 as our archive and retrieve software. The TSM server is on version 4.2.3.4.

We print special interest magazines and we store a lot of images in this manner for placement into the magazines. TSM is set up on a NetWare server

whose job is to retrieve images as they are requested to go into the magazines. It will then put the image on another NetWare server. The TSM

manager is in a separate tree from the one it is restoring to. This has not been an issue and it is not an issue with other servers in the receiving tree. The operator runs a script which launches TSM along with the file name range that is requested. At this point the TSM returns a list of files for the operator to choose from (pick list). This list should appear almost immediately, however, it is taking up to 10 or 15 minutes to return this list. The best we can determine it is bogging down when logging into the

receiving server. When retrieving to any other server this delay is not seen. Below is a trace log taken on one of our retrieval servers. Notice the 3

minute delay from the login request to the actual login. This occurs at 11/03/2003 11:13:34.0400. Sometimes there is a 15 minute delay. Once

the connection has been made requests will connect immediately until there is a 15 or 20 minute time span between requests. At that point I think the

connection has been broken and must be established. I will have a sniffer put in place to try and get more information. There is a replica of root

on the server that the retrieval server is trying to connect to.

11/03/2003 11:13:33.0130 : pstsa.cpp (1818): attempting to

connect

to ******* for user *********

11/03/2003 11:13:33.0240 : pstsa.cpp (1845): Leave

checkUserInFile. rc=0

11/03/2003 11:13:33.0240 : pstsa.cpp (2190): module informations

for requester :

11/03/2003 11:13:33.0240 : pstsa.cpp (2191): 'Netware' Version

5.0.10

11/03/2003 11:13:33.0240 : pstsa.cpp (2196): 'SMDR.NLM' Version

6.50.3

11/03/2003 11:13:33.0240 : pstsa.cpp (2164): module informations

for responder ******* :

11/03/2003 11:13:33.0240 : pstsa.cpp (2166): 'Netware' Version

5.0.0

11/03/2003 11:13:33.0240 : pstsa.cpp (2171): 'SMDR.NLM' Version

6.50.10

11/03/2003 11:13:33.0240 : pstsa.cpp (2177): 'TSA500.NLM'

Version 5.5.10

11/03/2003 11:13:33.0240 : procopts.cpp (12062): AddNWPasswordEntry:

parsed server 'SHPROD1' user **********

11/03/2003 11:13:33.0300 : pstsa.cpp (1589): LoginToNDS:

NWDSCreateContextHandle, serverName='*******', user=*********', rc='0'

11/03/2003 11:13:33.0300 : pstsa.cpp (1598):

NWDSCreateContextHandle: NDS context is '0'.

11/03/2003 11:13:33.0350 : pstsa.cpp (1602): LoginToNDS:

NWDSLogin

rc=0

11/03/2003 11:13:34.0400 : pstsa.cpp (1633): LoginToNDS:

NWCCOpenConnByName returned 0

11/03/2003 11:13:34.0400 : pstsa.cpp (1651): LoginToNDS:

NWIsDSAuthenticated() - NO.

11/03/2003 11:16:26.0260 : pstsa.cpp (1654): LoginToNDS:

NWDSAuthenticate returned FFFFFD63

11/03/2003 11:16:26.0260 : pstsa.cpp (1693):

NWDSGetCurrentUser():

user handle after NWDSLogin is '-933785120'.

11/03/2003 11:16:26.0260 : pstsa.cpp (1696): LoginToNDS: Login

rc=0



Thanks for any help or suggestions.

[email protected] :confused:
 
Back
Top