| Event Id | 5781 |
| Source | Netlogon |
| Description | Dynamic registration or deregistration of one or more DNS records failed because no DNS servers are available. |
| Event Information | Cause: This event occurs after Domain Controller Changes Domain. Resolution: 1. Stop the Netlogon service. 2. Rename the Netlogon.dns file to Netlogon.old, and then rename the Netlogon.dnb file to Netlogon.old2. 3. Start the Netlogon service or restart your computer. Additional Information: Following information from a newsgroup post may help: There are a number of issues that can cause this problem, two of which Im aware. 1) Netlogon wants to start before the DNS server and the registration cannot take place. You can verify this by looking at the Event Viewer times for when Netlogon loads and when DNS loads. On my system, DNS always loads after Netlogon. 2) When use used the AD wizard to create the AD and automatically integrate the DNS server, the utility that actually does the process (dcpromo.exe) does not create or update the DNS client configuration information. Now, I have read in this group that a possible cure for (2) is to issue the following command line statement, just before shutdown. On the next reboot, the problem should vanish. It hasnt worked for me. Command line statement: Net Stop DNS I have also read that some individuals were able to resolve the issue, by making a Registry entry to make the Netlogon startup "Depend On DNS". When I tried to do the latter, it did not work. Instead, Netlogon would not automatically start, at all. After a long wait enter the GUI, I was able to manually start the Netlogon service. the Event viewer recorded ID 7024 and 2138, events. |
| Reference Links | Troubleshooting Netlogon Event 5774, 5775, and 5781 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.