Peter,

  Look in the event logs and see if there are any error or warning messages
that occur around the same time.  I have seen both TCP/IP related messages
and RAM shortage related messages be generated.  Obviously, if this is
occuring at the same time on several clients it may actually be a problem
at or near the server.  Also, if it is a specific set of clients you may
attempt to find out if there is a common network component.

Has anyone else noticed how easy it is to come up with ideas (good or
otherwise) when you don't have to do the work?

Good Luck,
 Dan T.

----------
> From: Peter Thomas <Peter_Thomas AT MANULIFE DOT COM>
> From: Peter Thomas <Peter_Thomas AT MANULIFE DOT COM>
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Errors on Windows/NT Client with TCP/IP
> Date: Wednesday, July 30, 1997 5:03 PM
>
> I'm finding that some of my scheduled backups are "dieing" with the
> following messages in DSMERROR.LOG.
>
>
>
> (20 minutes later, the backup restarts, and completes quite happily)!
>
>
>
> Any suggestions from the Net?
>
>
>
> 1997 23:18:37  TcpRead: Error reading data, rc: 10054
> 1997 23:18:37  sessRecvVerb: Error -50 from call to 'readRtn'.
> 1997 23:18:37  cuConfirm: Received rc: -50 trying to receive ConfirmResp
> verb
> 1997 23:18:37  TcpFlush: Error 10038 sending data on Tcp/Ip socket
> 4294967295.
> 1997 23:18:37  sessSendVerb: Error sending Verb, rc: -50
> 1997 23:18:37  ANS4017E Session rejected: TCP/IP connection failure
> 1997 23:18:38  ANS4017E Session rejected: TCP/IP connection failure
>
>
>
> Thanks
>
>
>
> Peter T