I would suspect they are re-booting the NT server for some reason or you need to
get the network connections checked out.  This is generally what we run into
when
we see these errors. It could be a bad network card.

Brenda




From: O1=INET00/C=US/A=IBMX400/P=STATEFARM/DD.RFC-822=ADSM-L\@VM.MARIST.EDU on
12/09/99 05:20:12 AM
To:   ADSM-L
cc:
Subject:  NT servers as ADSM clients

Server: NT V3.1.2.20
Clients: NT V3.1.0.6

We have a mixture of NT, UNIX and Novell clients. We also have some Exchange
and SQL agents. All seems to work smoothly, except that each night it seems
that one or two (taken at random) of the NT Servers fail in their
backups.....

Does anyone else have this experience of NT servers not completing for
seemingly no reason??

We stop and start the ADSM Schedule Service on these machines, and all is OK
again for the next night (until its their "turn" to be one of the 0, 1 or 2
that fail each night!).
Looking through the ADSM Server log files shows 2 errors from the node
because of locked files (normal), and then:
12/08/1999 22:42:34 ANR0480W Session 422 for node OXFS11456 (WinNT)
terminated - connection with client severed.
12/09/1999 01:00:01 ANR2580E Schedule NT_SERVERS1 in domain UK1_NT for node
OXFS11456 failed.

Errors from the client are:
11/22/1999 03:16:06 TcpFlush: Error 10054 sending data on Tcp/Ip socket 64.
11/22/1999 03:16:06 sessSendVerb: Error sending Verb, rc: -50
11/22/1999 03:16:06 TcpFlush: Error 10054 sending data on Tcp/Ip socket 64.
11/22/1999 03:16:06 ANS1809E Session is lost; initializing session reopen
procedure.
11/22/1999 03:16:06 ANS1809E Session is lost; initializing session reopen
procedure.
11/22/1999 03:17:10 TcpOpen: TCP/IP error connecting to server.
11/22/1999 03:17:10 sessOpen: Failure in communications open call. rc: -50

Cheers, Chris