Event ID 5782

[Will]

All,
I recieve Warnings every 2 hours from the Netlogon
service with an EventID of 5782. The text of the error is:

Dynamic registration or deregistration of one or more DNS
records failed with the following error:
No DNS servers configured for local system.

This is on a single server W2K SP4 running as a DC with
DNS, WINS, IIS, Exchange, and SQL. I know it is not the
best setup, so please don't laugh too hard (not my server
just helping out). Addtionally the server has one NIC that
has multiple IPs/web sites assigned to it.

Can anyone explain this?

Thanks so much,
Will

 

[Will]

Okay all....i got it worked out, thanks to the following
article:

http://www.tuketu.com/technology/win2k-event id%
205782.htm

 

[Sergey Y.]

http://www.eventid.net/display.asp?eventid=5782&source=Netlogon

 

[Ace Fekay [MVP]]

In

All,
I recieve Warnings every 2 hours from the Netlogon
service with an EventID of 5782. The text of the error is:

Dynamic registration or deregistration of one or more DNS
records failed with the following error:
No DNS servers configured for local system.

This is on a single server W2K SP4 running as a DC with
DNS, WINS, IIS, Exchange, and SQL. I know it is not the
best setup, so please don't laugh too hard (not my server
just helping out). Addtionally the server has one NIC that
has multiple IPs/web sites assigned to it.

Can anyone explain this?

Thanks so much,
Will

I will not laugh. Just want to comment that a DC is not recommended to be
hosting Exchange, SQL and multiple websites, especially with mutliple IP
addresses. The mutliple IPs alone causes numerous issues with DNS
registration.

Usually a 5782 is due to a foreign DNS address in the IP properties and/or
dynamic updates not enabled. The article that you posted referred to pre-SP1
and SP1 changes that don;t apply anymore with the newer updates. So not sure
what part of that article helped you out. Was it the foreign DNS addresses?
You have to be careful too with the mutliple IPs registering since that can
cause some concern with clients trying to find this DC/GC (if it is a GC
too) with all those addresses. Which I guess may or may not hurt, but not
best practice.



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

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

 

[Michael Johnston [MSFT]]

Verify that the server only points to itself for DNS. Then in the DNS forward lookup zones, verify that you have a zone by the
same name as the Active Directory. Also verify that this zone accepts dynamic updates.

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.