NetLogon Error 5774

[Guest]

From what I've read, this error occurs because the NetLogon server tries to
register the logon request and cannot find a DNS with the domain name listed.

The server is W2K; it is the PDC and the DNS for the AD is on this server.
This DNS is a root DNS.

If the IP for this machine is placed at the top of the NIC's DNS entrys, the
5774 error problem dissapears. However, in that case, this machine will not
be able to resolve external domain names either with a Ping command or from
the browser for example.

It appears that even though the ISP's lookup DNS is listed second and third
on the NIC's list of DNS servers, those DNS will not be used to lookup domain
names that are not returned by the local DNS.

The Local DNS server properties has a forwarders tab which should forward
all unresolved requrest to another DNS IP but this function is disabled
apparently because this is a root DNS server.

There is a need to resolve other domain names from this machine for other
software running on it. Can any one suggest how to resolve this issue?

 

[Ace Fekay [MVP]]

In

From what I've read, this error occurs because the NetLogon server
tries to register the logon request and cannot find a DNS with the
domain name listed.

The server is W2K; it is the PDC and the DNS for the AD is on this
server. This DNS is a root DNS.

If the IP for this machine is placed at the top of the NIC's DNS
entrys, the 5774 error problem dissapears. However, in that case,
this machine will not be able to resolve external domain names either
with a Ping command or from the browser for example.

It appears that even though the ISP's lookup DNS is listed second and
third on the NIC's list of DNS servers, those DNS will not be used to
lookup domain names that are not returned by the local DNS.

The Local DNS server properties has a forwarders tab which should
forward all unresolved requrest to another DNS IP but this function
is disabled apparently because this is a root DNS server.

There is a need to resolve other domain names from this machine for
other software running on it. Can any one suggest how to resolve this
issue?

Simply put, this is a classic issue caused by using some other DNS server in
it's IP properties. You cannot use any other DNS other than the DNS servers
that host the AD zone because multiple entries is not a load balancing
mechanism, but rather a fault tolerant mechanism. If you are after Internet
resolution, your DNS will do that anyway by using the Root hints but you
can make it more efficient by configuring a forwarder.

The AD cardinal rule:
ONLY use the internal DNS, and configure a forwarder for efficient Internet
access, or expect issues resulting from it, as you are currently
experiencing. Do Not ever use your ISP's or any other DNS in IP properties
that does not either host the AD DNS zone or that does not have a reference
to it (such as your ISP's).

See this on how to configure a forwarder (choose your operating system):

323380 - HOW TO Configure DNS for Internet Access in Windows Server 2003 :
http://support.microsoft.com/?id=323380

300202 - HOW TO Configure DNS for Internet Access in Windows Server 2000 :
http://support.microsoft.com/?id=300202

--
Ace

This posting is provided "AS-IS" with no warranties or guarantees and
confers no rights.

If this post is viewed at a non-Microsoft community website, and you were to
respond to it through that community's website, I may not see your reply
unless that website posts replies back to the original Microsoft forum.
Therefore, please direct all replies ONLY to the Microsoft public newsgroup
this thread originated in so all can benefit or ensure the web community
posts it back to the original forum.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft MVP - Windows Server Directory Services
Microsoft Certified Trainer
Infinite Diversities in Infinite Combinations.
=================================

 

[Guest]

Your advice worked perfectly. Thank you.

 

[Ace Fekay [MVP]]

In

Your advice worked perfectly. Thank you.

Glad it helped! Pass the word...


Cheers!

Ace

 

[Jorge_de_Almeida_Pinto]

From what I've read, this error occurs because the NetLogon
server tries to
register the logon request and cannot find a DNS with the
domain name listed.

The server is W2K; it is the PDC and the DNS for the AD is on
this server.
This DNS is a root DNS.

If the IP for this machine is placed at the top of the NIC's
DNS entrys, the
5774 error problem dissapears. However, in that case, this
machine will not
be able to resolve external domain names either with a Ping
command or from
the browser for example.

It appears that even though the ISP's lookup DNS is listed
second and third
on the NIC's list of DNS servers, those DNS will not be used
to lookup domain
names that are not returned by the local DNS.

The Local DNS server properties has a forwarders tab which
should forward
all unresolved requrest to another DNS IP but this function is
disabled
apparently because this is a root DNS server.

There is a need to resolve other domain names from this
machine for other
software running on it. Can any one suggest how to resolve
this issue?

Configure internal servers to point only to internal DNS servers. Do
not configure them with ISP DNS servers. To be able to resolve
external DNS names configure forwarders. To be able to configure
forwarders to DNS server must not host a root zone ( . ).


for more info see:
http://support.microsoft.com/default.aspx?scid=kb;en-us;323380
http://support.microsoft.com/default.aspx?scid=kb;en-us;300202&sd=tech