Sorry, here's more details:

Client sees ADSM hang in the middle of a file (usually a large file)
& I get the following at the server:

  ANR0481W SESSION 1833 TERMINATED - CLIENT DID NOT RESPOND WITHIN 999
       (if running an Incremental directly from GUI)
or
  ANR0480W SESSION 7235 TERMINATED - CONNECTION WITH CLIENT SEVERED.
       (if running an Incremental via Scheduler)

The user is at a 'remote' location and so I thought it was the link being slow
but I've increased COMMTIMEOUT from 999 to 1999 and it just times out
1000 seconds later, after hanging.

I remember having this problem with Macs because they had a duplicate file-
spaces in some cases or the tcpbuffer tcpwindow parms were at maximum but those
situations are not the case this time.

  ... joe.f.


SPGJAF @ CMSA.Berkeley.Edu    also ... USUCA886 @ IBMMAIL via x.400
University of Calif. at Berkeley  510-642-7638 (work) 527-1933 (home)

On Wed, 24 Sep 1997 17:36:53 PDT "Joseph A. Faracchio" said:
>We have a couple of users that switched from a Windows 31 workstation
>to a Windows 95 (Dell) computer and they cannot get the first incremental
>backup to complete on their new computers.
>
>These users installed the win32 client (it says "PTF 6" in the program popup)
>and are re-using the same nodeid name.
>
>I've search IBM Link and looked over recent ADSM-l mail I've been
>accumulating but have found no clues.
>
>Is this familiar to anyone or should I open up a problem report with IBM???
>
>thanks ... joe.f.