Thanks for your response. FYI...It turns out that our admin that runs our virus protector turned on protection for outgoing data as well. After that was turned off the errors have disappeared and the server backed up.
Bud Brown Information Services Systems Administrator 303-436-5986 -----Original Message----- From: Prather, Wanda [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 19, 2002 9:47 AM To: [EMAIL PROTECTED] Subject: Re: TCP Errors The error -50 is generic TCP/IP error that says the session died. Check the server ACTLOG at the exact time and see what message was issued on the server end; you can usually at least tell whether the client killed the session or the server did. Check the dsmsched.log file on the client, see if you get anything consistent about WHERE the client dies, is it in the same part of the filesystem each time, etc. -----Original Message----- From: Brown, Bud [mailto:[EMAIL PROTECTED]] Sent: Tuesday, March 19, 2002 8:47 AM To: [EMAIL PROTECTED] Subject: TCP Errors All, I am all of a sudden beginning to get the following errors on a file server. The client is w2k with b-a 4.2.0, and the server is AIX 4.3.3 w/ 4.1.4.1. This node has been backing up fine up until last monday. The NIC settings are hard set to 100/FULL as well as the switch port. There are no collisions or CRC's to speak of. Any ideas? Is this a simple client upgrade? I don't see anything obvious in the readme to suggest that one is necessary. 03/19/2002 06:09:13 TcpRead(): recv(): errno = 10053 03/19/2002 06:09:16 sessRecvVerb: Error -50 from call to 'readRtn'. 03/19/2002 06:09:22 ANS1809E Session is lost; initializing session reopen procedure. 03/19/2002 06:09:31 ANS1809E Session is lost; initializing session reopen procedure. 03/19/2002 06:09:42 ANS1810E TSM session has been reestablished. Any feedback is appreciated, Bud Brown Information Services Systems Administrator 303-436-5986
