Receive Event ID 5781 with no apparent fix

  • Thread starter Thread starter Chris
  • Start date Start date
C

Chris

Hello,

I keep receiving this event viewer error:

Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5781
Date: 8/22/2003
Time: 11:36:02 AM
User: N/A
Computer: Homer
Description:
Dynamic registration or deregistration of one or more DNS
records failed because no DNS servers are available.
Data:
0000: 000005b4

This doesn't make any sense because I do indeed have a DNS
server. At any rate, Q257462 acknowledges this is a
problem and the fix is to have a service pack above SP1.
I do indeed have a SP greater than 1 but I'm still
receiving this error. I cannot find any other guidance
other than what the Knowledge Base article states is a
fix. Any suggestions would be greatly appreciated.

BTW, I'm running Server 2000 with 7 other Professional
clients. We're a small development area that is not
connected to a ISP. The server has been promoted. Any
box can ping any other box by name.

Thanks a million,

--Chris
 
In
Chris said:
Hello,

I keep receiving this event viewer error:

Event Type: Warning
Event Source: NETLOGON
Event Category: None
Event ID: 5781
Date: 8/22/2003
Time: 11:36:02 AM
User: N/A
Computer: Homer
Description:
Dynamic registration or deregistration of one or more DNS
records failed because no DNS servers are available.
Data:
0000: 000005b4

This doesn't make any sense because I do indeed have a DNS
server. At any rate, Q257462 acknowledges this is a
problem and the fix is to have a service pack above SP1.
I do indeed have a SP greater than 1 but I'm still
receiving this error. I cannot find any other guidance
other than what the Knowledge Base article states is a
fix. Any suggestions would be greatly appreciated.

BTW, I'm running Server 2000 with 7 other Professional
clients. We're a small development area that is not
connected to a ISP. The server has been promoted. Any
box can ping any other box by name.

Thanks a million,

--Chris

Chris, are all your machines (including the DC) only pointing to your own
internal server and updates set to yes on the zone?
Is your AD DNS domain name a single label name or is it the proper format of
"domain.com"?
Is the AD DNS domain name spelled the same as the zone in DNS?
Is the Primary DNS Suffix of the DC spelled exactly as the AD DNS domain
name and the zone name?

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Hello Chris,

Usually 5781 error in relation to DNS is caused by misconfigured TCP/IP
settings and/or misconfigured DNS. There can be however (although rare)
other causes of the 5781 error.

After the computer starts, the DNS server service may need to wait for
active directory to finish initialization. Active directory may be busy
performing active directory replication. This process may take 15 minutes
or longer, depending on the amount of replication taking place. I doubt if
this is the cause due to the size of your domain only consisting of 7 W2K
Pro.

Active directory integrated zones with secure updates DNS uses the Kerberos
authentication mechanism to validate secure updates. Immediately after the
computer starts, Kerberos-related services may not be initialized to
provide necessary services.

Large DNS zones. The DNS server service may need extra time to load zones
with thousands of records. This process may take 15 minutes or longer,
depending on zone size. This is a common error with one AD\DNS server with
a huge zone with 1000's of records and is often corrected by implementing
an additional AD\DNS server. Which should be done anyway on such a large
zone to take some of the work load off of a single server. (especially when
scavenging aged records, but that's another discussion) I doubt that this
is your issue because your zone is not that large.

This issue can be caused by stale entries in the DNS zone for the old
domain that a domain controller belonged to.



You can try the below steps that have given me positive results with this
error.

1.) Stop the Netlogon service.

2.)Move the Netlogon.dns and Netlogon.dnb files to a backup folder. The
efault location for these files is in the %SystemRoot%\System32\Config
folder.

3.) Restart the computer. The Netlogon service automatically restarts. You
can just restart the Netlogon service, but you should consider restarting
the computer. If you do not restart the computer and the event is logged
again, you should retry the steps again, and then restart the computer.


I would ignore this as a nuisance error if you can verify that all records
in the %SystemRoot%\System32\Config\Netlogon.dns folder are registered
correctly. You must manually verify that these records are registered

OR

The event 5781 is logged only once after the computer starts. For example,
if the error message is not logged again after 10 minutes, 20 minutes, 40
minutes, or every 2 hours. Note that if event 5781 is logged every 2 hours,
the error message is occurring every hour; the error message is logged
every 2 hours to keep the event log from filling.


Questions
************
Does nslookup resolve as expected?
Does netdiag and dcdiag come back pretty clean?


Shane Brasher
MCSE (2000,NT),MCSA, A+
Microsoft Platforms Support
Windows NT/2000 Networking
 
Back
Top