Sure you don't have 2 nodes configured with the same nodename? TSM will remember the IP/port of the last scheduler task to make contact. Check the IP address in the messages when TSM was trying to contact the client.
Also, does this client have multiple NIC's and IP addresses? You may want to specify the TCPCLIENTADDRESS in the option file to make sure the one you want and that is accessible to the TSM server is used. You could also try POLLING... Let the client do it all. Bill Boyer DSS, Inc. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Lee, Gary D. Sent: Wednesday, November 19, 2003 1:12 PM To: [EMAIL PROTECTED] Subject: Re: Strange Windows scheduler problem Had this problem recently with a windows 2000box running client v5.1.6, talking to a server solaris 2.8 v5.1.6.2. Somehow the wrong tcp/ip address got associated with the client. Filled in the tcp/ip address and got it resolved. I'll try and dig up the diagnosis messages from support. Involved digging deeply into the database, where I'd never been before. Anyway I ramble. Try filling in the client tcp/pip address manually. Hope this helps.
