ADSM-L
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

And yet another ANR9999D..

1996-10-22 12:31:54
Subject: And yet another ANR9999D..
From: Bob Booth - CSO <booth AT CHIANTI.CSO.UIUC DOT EDU>
Date: Tue, 22 Oct 1996 10:31:54 -0600 
Any know how to track this one down:

ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.
ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.
ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.
ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.
ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.
ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.
ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.
ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.
ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.
ANR9999D tcpcomm.c(352): Unknown TCPIP Failure.


Is there a trace level that can be performed, or a 'command' that will shed
some light on this?  They have been appearing in groups like this all night.

Thanks again!

Bob Booth
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  W95 Client, restore possibilities, Rovers, G (GRO)
Next by Date:  And yet another ANR9999D ..., Heiko Andresen
Previous by Thread:  W95 Client, restore possibilities, Rovers, G (GRO)
Next by Thread:  Re: And yet another ANR9999D.., W. Baur
Indexes:  [Date] [Thread] [Top] [All Lists]