Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have Server 2003 SP2 Standard Edition. This past week it has been logging an event called NETLOGON Warning 5781 at various times of the day. When this happens client computers lose access to the AD as their network folders disappear. It mentions issues with the DNS. The TCP/IP properties have no preferred DNS set - so by default the server will reference itself.

The only way to correct this issue seems to be restarting the server several times a day. I have tried editing the registry so that Netlogon is dependant on DNS as I suspected that Netlogon was starting before DNS and therefore causing the error. But now I get DNSApi error logs on the client computers.

How can I fix this? All Microsift support says is restart the server. Nothing has changed on the server in the 4 years we have had it. Then all of a sudden it throws up this error. I can't run Nltest.exe as I don't have the Serrver resource CD.

Any ideas on how to resolve this issue, please?

share|improve this question
Even though it has been working for years without it, I'm suspicious of the lack of DNS settings on the TCP/IP properties tab for this server. Is this server also a domain controller? Is it also providing DNS for your clients? – JasonAzze Jan 17 '13 at 11:48
When the issue occurs, you need to determine if you can ping the server by name and ip address. Also, nltest is available from several other locations, including the Microsoft download center. – Greg Askew Jan 17 '13 at 11:57

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.