UNSOLVED
Event ID 5719 (System) and 1054 (Application)
I get the below couple of errors in the event log of every XP PRO machine that I boot up in my Win2000 domain (this does not occur with 2000 Pro machines):
System Error: event ID 5719 / Source NETLOGON:
No Domain Controller is available for domain XXX: there are currently no logon servers available
Application Error: event ID 1054 / Source Userenv:
Windows cannot obtain the domain controller name for your computer network.
This does not prevent the users to use the network & servers but sometimes... the machine becomes very slow
Any idea ?
Michel
System Error: event ID 5719 / Source NETLOGON:
No Domain Controller is available for domain XXX: there are currently no logon servers available
Application Error: event ID 1054 / Source Userenv:
Windows cannot obtain the domain controller name for your computer network.
This does not prevent the users to use the network & servers but sometimes... the machine becomes very slow
Any idea ?
Michel
tim.benjamin
1 Message
1007
0
Posted January 16th, 2003 14:00
We have the same issue as well with Cisco 3524 and 4006 switches. All ports have port fast enabled and are locked down to 100FDX. Our issue only occurs on the GX260 with its integrated 3c905c NIC. Try the following on the A11 and above driver Enable LnkChk and turn down poll rate to 64. Also try setting the nic and the switch to auto-negotiate. A combination of these fixes has given us some success. We however have not been able to determine the cause of our issue. All of the machines are NT4 SP6a.Message Edited by tim.benjamin on 01-16-2003 10:49 AM
tdwalka
1 Message
1007
0
Posted December 18th, 2002 08:00
Hi,
We have been having the same problems here.
We have over 2000 boxes, 1000 GX240 and 1000 GX260.
The errors seem to be sporadic and we have done numorous tests and still none the wiser.
We have Cisco Switches which we have checked the Spanning Tree Algorithm on as per www.Eventid.net suggestion.
We also have a call out with Dell and Microsoft and so far no joy. This is causing a big problem due to Group Policy Failures now as we are trying to use a very secure environment.
Regards