To: OAS     --LMS1

FROM: Betsy Moir (TTCEDM) Ext 85020
      VM Tech Services
      email:  elizabeth.moir AT vm.ssw.abbott DOT com
Subject: TCP/IP connection failure

When we first started using ADSM we would run in to this kind of problem a
lot.  Very often it turned out to be the version of TCP/IP we were using.  When
we upgraded the IP, the problem went away.

Betsy
*** Forwarding note from OWNERAD1--INTERNET 96/12/13 08:56 ***





TO:          INTERNET  ADSM-L AT VM.MARIST DOT EDU
FROM: OWNERAD1 INTERNET  OWNER-ADSM-L AT VM.MARIST DOT EDU
DATE: 12/13/96 08:56
SUBJECT: TCP/IP connection failure
COPYLIST:
I have a problem with an older 3.11 Netware server that continues to
disconnect itself from the ADSM AIX server.  It seems to timeout on
larger files (in excess of 50MB).  The documentation for the error
listed below is very nondescript.  In a nutshell, the documentation is
saying that either the LAN connection went down or the job was
cancelled.  I have changed the client communication timeout to 300
seconds in the dsmserv.opt, to no avail.  I have not altered the
TCPBuffersize of TCPWindowsize in the dsm.opt client file.

Has anyone done this?  If so what are the ramifications of doing such?
 Lastly, am I barking up the wrong tree?

Any comments would be appreciated.

Thanks!

12/12/1996 20:22:51  TcpFlush: Error 60 sending data on Tcp/Ip socket
78439588.
12/12/1996 20:22:51  sessSendVerb: Error sending Verb, rc: -50
12/12/1996 20:22:51  TcpFlush: Error 32 sending data on Tcp/Ip socket
78439588.
12/12/1996 20:22:51  TcpFlush: Error 4 sending data on Tcp/Ip socket
4294967295.
12/12/1996 20:22:51  sessSendVerb: Error sending Verb, rc: -50
12/12/1996 20:22:51  ANS4017E Session rejected: TCP/IP connection
failure