Dan,
This was definitely an TCP/IP issue. But why? The network is stable
so the issues must be client server communication. Why does this
burp periodically. Most of client our using port 1500.
Below is the error we received. Its pretty generic.
ADSTAR Distributed Storage Manager
Command Line Administrative Interface - Version 2, Release 1, Level
0.2 (C) Copyright IBM Corporation, 1990, 1995, All Rights Reserved.
ANS5658E TCP/IP failure.
ANS5519E Unable to establish session with server.
ANS5103I Highest return code was -50.
I appreciate your feedback and any additional suggestions.
Brian Jones
Union Bank of Switzerland
______________________________ Reply Separator _________________________________
Subject: PUBLIC: Re: Server Daemon hangs and nodes not resched
Author: thompsod (thompsod AT USAA DOT COM) at nyux
Date: 7/13/97 1:11 PM
Brian,
We experience problems similar to this when our TCP/IP network
experiences problems. It appears as if the NT clients do not acknowledge
the loss of a session and hang. You did not specifiy what caused your
problems originally so I do not know if it is the same problem.
I do think that IBM should enhance the client end as far as locked or lost
sessions are concerned.
Dan T.
----------
> From: Brian Jones <brian.jones AT NY.UBS DOT COM>
> From: Brian Jones <brian.jones AT NY.UBS DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Server Daemon hangs and nodes not rescheduled
> Date: Friday, July 11, 1997 10:19 AM
>
|