Computer losing Network connection

  • Thread starter Thread starter Ed Walters
  • Start date Start date
E

Ed Walters

Last night at 00:46 I got the following series of event messages

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4201
Date: 17/10/2003
Time: 00:46:27
User: N/A
Computer: RESEARCH
Description:
The system detected that network adapter
\DEVICE\TCPIP_{2C595EB8-DE3B-463A-A839-EE14511769ED} was connected to
the network, and has initiated normal operation over the network
adapter.


Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 17/10/2003
Time: 00:46:39
User: N/A
Computer: RESEARCH
Description:
No Windows NT or Windows 2000 Domain Controller is available for
domain IKOS. The following error occurred:
There are currently no logon servers available to service the logon
request.

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4202
Date: 17/10/2003
Time: 00:46:39
User: N/A
Computer: RESEARCH
Description:
The system detected that network adapter
\DEVICE\TCPIP_{2C595EB8-DE3B-463A-A839-EE14511769ED} was disconnected
from the network, and the adapter's network configuration has been
released. If the network adapter was not disconnected, this may
indicate that it has malfunctioned. Please contact your vendor for
updated drivers.

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 17/10/2003
Time: 00:46:39
User: N/A
Computer: RESEARCH
Description:
No Windows NT or Windows 2000 Domain Controller is available for
domain IKOS. The following error occurred:
There are currently no logon servers available to service the logon
request.

Event Type: Information
Event Source: Tcpip
Event Category: None
Event ID: 4201
Date: 17/10/2003
Time: 00:46:49
User: N/A
Computer: RESEARCH
Description:
The system detected that network adapter
\DEVICE\TCPIP_{2C595EB8-DE3B-463A-A839-EE14511769ED} was connected to
the network, and has initiated normal operation over the network
adapter.

So we lost a few machines off the network at 00:46 and they immediatly
recovered, looking further into the event viewers shows that a number
of XP workstations are configured for hibernation and when they
hibernate they dissapear from the Network as well.
Also for our time synchronisation we use Tardis and K9 on our servers
which works fine, most of the workstations have been left to fend for
themselves as far as time is concerned as we haven't configured the DC
to get time from outside, it gets the time from Tardis as well.

Is it possible that W32 could have knocked machines off the network at
the same time, I have sorted the W32 issue out on those machine and
they haven't left the network since then.

Could anyone explain the implications of having W32time trying to hard
to get a time and continously failing.

Thanks

Ed
 
Back
Top