One DC cannot communicate with another DC. Error: "There are currently no logon servers available to service the logon request."

A DC in a remote office cannot communicate with any other computers on its LAN or to the main DC.  When I try to browse to any other computer thru My Network Places or thru Run,\\<computername>, the above error appears.  I'm able to make a PC Anywhere connection to the machine, though.

Additionally, when the computers on the remote subnet try to access the remote DC, they get the same error message.  However, I'm able to browse to any computer on the remote subnet from my computer (which is on the same LAN as the main DC).

When I try to open Active Directory from the remote DC (Users and Computers, Sites and Services, or Domains and Trusts) the error states: "Naming information cannot be located because: No authority can be contacted for authentication.  Contact your system administrator to verify that your domain is properly configured and is currently online."

There are tons of Event log errors on the remote DC from the NTDS KCC stating that the configuration for replication is SMTP, which is not supported for DCs in the same domain.  However, replication is set to IP.  Any ideas or places to start looking would be appreciated.  Thanks!

Who is Participating?
SkegeConnect With a Mentor Commented:
Do you have configured DNS.
That´s sounds like you have probles with DNS..

Check to see that the zones on your DNS server are configured correctly and that your DNS server has authority for the zone that contains the Active Directory domain name.
Is there a trust relationship between the DCs?
jqualteriAuthor Commented:
Yes there's a trust.  These are both domain controllers for the same domain.  The one in the remote office is unable to authenticate any domain users because it cannot verify them from the main DC.  I don't think it has been getting replication for 4 days.
jqualteriAuthor Commented:
DNS is configured on the remote DC, yes.  I'm pretty certain its configured correctly because the machine was having no problems as of last week, and nobody has touched it.  The remote computer is the authority for its zone.
JamesDSConnect With a Mentor Commented:
This is certainly DNS, most AD problems are

Right then, configure BOTH DCs with DNS servers, AD Integrate your DNS ZONE if possible and MAKE SURE that each DC is pointing to the other one for its primary DNS settings - leave secondary blank to aboid the problem of DNS island.

At each DC command line run:


Check the DNS zone on each DNS server to make sure the _MSDCS sub domain is in place and then use NSLOOKUP from the command line to make sure you can resolve the fully qualified domain name of each DC from the other one

Once you have success on this open up the snapin AD Sites and Services and navigate down the sites tree to the connection objects on each server and initiate replication in each direction

Check the logs for the next 20 minutes and iff all is clear your domain will be running again.


Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.