Event ID: 5719 on Windows 2000 CLIENT
From: Tom (Tom_at_discussions.microsoft.com)
Date: 06/15/04
- Next message: Alun: "Re: networking requirements - do I need a domain controller?!"
- Previous message: Tina Smith: "Remote via RAS"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 15 Jun 2004 05:29:02 -0700
I had the following error during bootup of a W2K Client on a Windows Server 2003 lan:
System Netlogon Event ID: 5719
No Domain Controller is available for domain <YourDomainName> due to the
following: There are currently no logon servers available to service
the logon request...
This was (in my case) associated in the Event Log with the Netlogon attempt coming before the network card was up and running. After bootup, I could not see other computers on the lan using Network Neighborhood.
I notice that other people on this newsgroup have had a similar problem with a network client booting up and the replies they get are for KB articles dealing with this error on Servers, which won't fix the problem if it's on one of your clients.
One person I know of with the same issue swapped out the NIC and since the new card came up faster, the problem went away.
In my case, I tried swapping the NIC out, with no effect. However, I did discover that turning off Norton Personal Firewall made the problem go away. Investigating further, I found that Norton Intenet Security needed to have the following fix:
Click on 'Personal Firewall'
Click the 'Home Networking' tab
Click the 'Trusted' tab
Add the range of IP addresses your DHCP uses. (If you have fixed IP addresses, you can add them here, also)
Now I have no error on bootup and I can see (and be seen on) the lan.
Good luck
- Next message: Alun: "Re: networking requirements - do I need a domain controller?!"
- Previous message: Tina Smith: "Remote via RAS"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
