Netlogon Errors

I am seeing the following error a few times a day on a domain controller that is the PDC emulator for the domain. DNS is configured correctly. Any ideas?

Event Type:      Error
Event Source:      NETLOGON
Event Category:      None
Event ID:      5719
Date:            6/12/2008
Time:            11:49:36 AM
User:            N/A
Computer:      *
This computer was not able to set up a secure session with a domain controller in domain * due to the following:
There are currently no logon servers available to service the logon request.  
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.  

If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.

For more information, see Help and Support Center at

Who is Participating?
kunalclkConnect With a Mentor Commented:
Is this is the only DC for the domain?
mikegaston3127Author Commented:
No there is another DC in the same site.
Try to telnet to port 135 from both DC's to each other and check if it is successful or not.
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

mikegaston3127Author Commented:
I can telnet from both DC's to one another.
mikegaston3127Author Commented:
The information the link has to offer regarding error 5719 is concerned with problems with MTU sizes in network routers. These two DC's are connected via a 24 port switch.
ChiefITConnect With a Mentor Commented:
When did you bring this DC on line?

When you first bring a DC on line, you have to manually register the DC's SRV and host A records. Also, multihomed domain controllers can make a difference. And the Preferred DNS server can make a difference. In either case, this error is usually a problem with DNS. It could even be a cached DNS entry on this server. Check out this article and see if it helps you out.
mikegaston3127Author Commented:
I will look into the link. So busy right now almost no time to breathe.
mikegaston3127Author Commented:
This one got lost in the woodwork. Sorry for the late responce.
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.