ADSM-L

TCP/IP connection failure/time out

1998-04-20 15:50:22
Subject: TCP/IP connection failure/time out
From: "David H. Wentworth" <David.Wentworth AT UCOP DOT EDU>
Date: Mon, 20 Apr 1998 12:50:22 -0700
We have two Windows 95 machines that have started getting "TCP/IP
connection failure" on nearly every backup attempt. The failures always
happen on the same files which are fairly large, 16MB in one case and 36MB
in the other. The DSMERROR.LOG reports the following:

03/16/1998 16:02:31  TcpFlush: Error 10054 sending data on Tcp/Ip socket 9.
03/16/1998 16:02:31  sessSendVerb: Error sending Verb, rc: -50
03/16/1998 16:02:31  TcpFlush: Error 10054 sending data on Tcp/Ip socket 9.
03/16/1998 16:02:33  TcpFlush: Error 10038 sending data on Tcp/Ip socket
4294967295.
03/16/1998 16:02:33  sessSendVerb: Error sending Verb, rc: -50

The server activity log shows the connection timed out.

The server is MVS ADSM v2.1.0.13. It is running IBM TCP/IP 3.2 with PTF
UQ03848. the client is ADSM for Win32 v2.1.0.6.

Our administrator increased the timeout value on the server from 120
seconds to 240 but it didn't help

We've also tried the following settings on the client:

TCPBuffsize 4
TCPWindowsize 8

Upgrading the client to v3.1.0.1 helped in one case. We don't want to
upgrade the client in the other case because of support issues.

Does anyone have comments or suggestions?

                Dave

+-----------------------------------------------------+
| David Wentworth          | University of California |
| Programmer/Analyst       | Office of the President  |
| E-mail:                  | Information Resources    |
| David.Wentworth AT ucop DOT edu |   & Communications       |
+-----------------------------------------------------+
<Prev in Thread] Current Thread [Next in Thread>