Active Directory - Event ID 5719 Netlogon - Asked By Rex Midas on 08-Sep-09 03:56 AM

In first place sorry for my english....
When I login to a member server 2003 using Terminal Services,I am getting the following error messages and unable to login as a domain user. I could login only as a local user.
The system cannot log you on due to the following error:
1.The RPC Server is unavailable
2.There are currently no netlogon servers available to service the logon
request.
The domain controller is functioning fine and all other computers are
successfully able to login to the domain.
The above issues occur sometimes not always. When I restart the computer,I am
able to login,but again the problem repeats after some time.
Can someone please help me in resolving this issue...

In Event Viewer appears the following events:
Event Type:	Error
Event Source:	NETLOGON
Event Category:	None
Event ID:	5719
Date:		08/09/2025
Time:		0:16:03
User:		N/A
Computer:	CENTAURO1
Description:
This computer was not able to set up a secure session with a domain controller in domain T-SALUD 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.  
ADDITIONAL INFO 
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 http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0               ^..À    


Event Type: Error Event Source: W32Time Event Category: None Event ID: 29 Date: 08/09/2025 Time: 0:16:27 User: N/A Computer: CENTAURO1 Description: The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 15 minutes. NtpClient has no source of accurate time. For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Thanks

Couple of things to check. - [)ia6l0 iii replied to Rex Midas on 08-Sep-09 11:24 AM

Firstly,  the domain user must be added to the RemoteDesktop group on the server as well as on the domain. 

If that is not the case, the NetLogon service (as your error log points out) might have failed to start, and would hence make all remote requests fail. Figure out from the event viewer why the netlogon service failed. 

An alternate step would be to update the service packs on the server.



netlogon problem - Rex Midas replied to [)ia6l0 iii on 08-Sep-09 11:46 AM

Thanks for your answer.

The users are on RemoteDesktop group.
Netlogon service starts correctly because when I restart the server everything works correctly, the problem appears after 15 or 20 minutes, then is not possible log in the server with a domain account and event 5719 is registered.

The unique information that I have in the event viewer is the one that i have put in first post.

Thanks
Mike Audet replied to Rex Midas on 28-Apr-10 10:23 AM
I had that same issue and it turned out that the developer who also manages some apps on this server was running an LDAP server which was, in turn, causing an authentication problem for both the computer account and anyone trying to log on with domain credentials.  If you log on locally it worked fine.
 Another part of the problem was that this LDAP SERVICE that they were running was using up all the HEAP pool.  Sysinternals has some excellent free tools to help with monitoring these processes running on the box....use them all the time and most will help narrow down the cause of problems quickly.

Not sure if this is too late or even useful...hope so...just had the problem last week and tracked it down to the above issues....

good luck...