2k Server, XP Pro, DNS, Event ID 5781

  • Thread starter Thread starter John
  • Start date Start date
J

John

Hello.

I have a 2000 Server that is continually issuing NetLogon
Error 5781 "Dynamic registration or deregistration of one
or more DNS records failed because no DNS servers are
available."

Other than this error filling up the Event Log, I have had
no problems out of this server, however I have added a
Windows XP Pro client to the network (previous clients
were NT 4.0 Workstation) and I have several issues with
this client.

Relavent information:
The server is Windows 2000 Server.
It is the only DC in the network.
The domain name ends with ".com".
The entries, "_msdcs, _sites, _tcp, _udp" DO NOT appear
under the Primary Forward Lookup Zone in the DNS MMC as
they usually do.
The client IPs DO NOT appear in the DNS MMC in the right
hand pane.
I have deleted and recreated the lookup zones several
times to try to resolve this issue.
I have tried to enable a DNS Forwarder to resolve this
issue, but to no avail.

At the XP Pro client:
The DC IP is listed as the DNS Server on the client.
The DC IP is listed as the WINS Server on the client.
I have tried to add the Domain Users Group to the Local
Power Users group in order to get proper priviledges for
Domain users at the Local Machine, however the Domain DOES
NOT APPEAR in the "Locations" options when attempting this
operation.
The network shares on the XP Pro client DO NOT appear and
are not available to the other clients on the network.
All Authentication operations on the client are very, very
slow to respond.

I feel that the DNS issues on the server are the reason
for all of the issues I am having on this workstation. Is
it possible that the ".com" extension on the Domain Name
is causing these issues?

Please respond as soon as possible with any suggestions
you have.

Thank you,
John
 
In
John said:
Hello.

I have a 2000 Server that is continually issuing NetLogon
Error 5781 "Dynamic registration or deregistration of one
or more DNS records failed because no DNS servers are
available."

Other than this error filling up the Event Log, I have had
no problems out of this server, however I have added a
Windows XP Pro client to the network (previous clients
were NT 4.0 Workstation) and I have several issues with
this client.

Relavent information:
The server is Windows 2000 Server.
It is the only DC in the network.
The domain name ends with ".com".
The entries, "_msdcs, _sites, _tcp, _udp" DO NOT appear
under the Primary Forward Lookup Zone in the DNS MMC as
they usually do.
The client IPs DO NOT appear in the DNS MMC in the right
hand pane.
I have deleted and recreated the lookup zones several
times to try to resolve this issue.
I have tried to enable a DNS Forwarder to resolve this
issue, but to no avail.

At the XP Pro client:
The DC IP is listed as the DNS Server on the client.
The DC IP is listed as the WINS Server on the client.
I have tried to add the Domain Users Group to the Local
Power Users group in order to get proper priviledges for
Domain users at the Local Machine, however the Domain DOES
NOT APPEAR in the "Locations" options when attempting this
operation.
The network shares on the XP Pro client DO NOT appear and
are not available to the other clients on the network.
All Authentication operations on the client are very, very
slow to respond.

I feel that the DNS issues on the server are the reason
for all of the issues I am having on this workstation. Is
it possible that the ".com" extension on the Domain Name
is causing these issues?
Click to expand...

Not likely, but the primary DNS suffix must match the AD domain name.
Please respond as soon as possible with any suggestions
you have.

Thank you,
John
Click to expand...

One bit of information missing, What DNS is listed on the DC for DNS?
It should be its own IP address ONLY.
This is about the best guess anyone can make without the ipconfig /all and
the AD Domain name from ADUC. If you will post that info, a better diagnosis
can be made, at least it would make a good starting point.
 
IP is 192.168.10.5
Sub is 255.255.255.0
Gateway is 192.168.10.1
DNS is 192.168.10.5
WINS is 192.168.10.5

The domain name is not registered, it is only local.


What is ADUC?

John
 
In (e-mail address removed) <[email protected]>
posted a question
Then Kevin replied below:
IP is 192.168.10.5
Sub is 255.255.255.0
Gateway is 192.168.10.1
DNS is 192.168.10.5
WINS is 192.168.10.5
Click to expand...

Actually I need you to post the ipconfig /all I need to see the primary DNS
suffix.
The domain name is not registered, it is only local.
Click to expand...
Internal domains do not need to be registered.

What is ADUC?
Click to expand...
Active Directory Users & Computers
The reason I need this info is the primary DNS suffix and the domain name in
ADUC must match exacrtly.
 
The ipconfig information I listed is from the DC. As you
can see, the IP of the DC and the DNS are identical. The
ONLY DNS listed in the TCP/IP properties for the NIC of
the DC is its own. It as been configured this way all
along.

I had the domain name registered and parked at an external
IP address and this resolved all DNS issues on the local
domain. Once the domain name enjoyed external, Internet
DNS resolution (I pinged the domain name on the Internet
and received IP resolution rather than "Host does not
exist" to ensure the DNS entry had propogated), I again
deleted and recreated the Forward and Reverse Lookup Zones
at the DC. This time the 4 sub-catagories appeared as
they should under the Forward Lookup Zone, the NetLogon
errors disappeared, the Domain containers were available
to the XP Pro client, and the shared resources of the XP
Pro client were available to all clients on the network.

I had a feeling that the ".com" extension on the local
domain was the root of the issue and it proved to be true.

Thank you for all your help and I hope this post is
usefull to the community.

John
-----Original Message-----
In (e-mail address removed)
Click to expand...
 
Back
Top