ADSM-L

Re: TCP/IP Connection Failure Jerry Lawson

2015-10-04 18:00:05
Subject: Re: TCP/IP Connection Failure Jerry Lawson
From: INTERNET.OWNERAD at SNADGATE
To: Jerry Lawson at ASUPO
Date: 3/12/98 3:53PM
______________________________ Forward Header
__________________________________
Subject:        Re: TCP/IP Connection Failure
        Author:  INTERNET.OWNERAD at SNADGATE
Date:   3/12/98 3:53 PM


We also get the TCP/IP connection failure occasionally.  However, we
also get it on clients connected to the same subnet.  The problem comes
and goes with no evident trigger.  Below is content of ADSM error log
from BACLIENT.  What is interesting is that most of our NT clients have
multiple hard drives (C:, D:, etc.) and the TCP/IP connection failure
only seems to happen to one drive.  In other words the C: drive may
backup and D: drive fail or the D: may backup and the C: fail.
03/12/1998 03:11:51  TcpRead: Zero byte buffer read.
03/12/1998 03:11:51  sessRecvVerb: Error -50 from call to 'readRtn'.
03/12/1998 03:11:51  ANS4017E Session rejected: TCP/IP connection
failure
03/12/1998 03:11:51  ANS4017E Session rejected: TCP/IP connection
failure
03/12/1998 03:28:30  TcpRead: Zero byte buffer read.
03/12/1998 03:28:30  sessRecvVerb: Error -50 from call to 'readRtn'.
03/12/1998 03:28:30  ANS4017E Session rejected: TCP/IP connection
failure
03/12/1998 03:28:30  ANS4017E Session rejected: TCP/IP connection
failure
03/12/1998 03:50:57  TcpRead: Zero byte buffer read.
 03/12/1998 03:50:57  sessRecvVerb: Error -50 from call to 'readRtn'.
03/12/1998 03:50:58  ANS4017E Session rejected: TCP/IP connection
failure
03/12/1998 03:50:58  ANS4017E Session rejected: TCP/IP connection
failure
03/12/1998 03:50:58  ANS4847E Scheduled event 'SNIPE_SCHED' failed.
Return code = 1.
Anyone make sense of this?
M. Casey
<Prev in Thread] Current Thread [Next in Thread>
  • Re: TCP/IP Connection Failure Jerry Lawson, INTERNET . OWNERAD at SNADGATE <=