Friday, February 01, 2013 12:55 PM
When I logon to our Win03 server I get a message stating:
"Failed to connect to a windows service"
Windows could not connect to the Group Policy Client service.
Reviewing my event logs i get the error below.
I've reviewed my fsmo roles and everything is fine.
I am seeing a DNS warning saying that "name_ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.FortisSecurity.local" timed out.
Anyone have any suggestions on this?
I started this discussion over on the server forum but as of today haven't been able to resolve this and was hoping someone here might.
Log Name: System
Date: 2/1/2013 7:14:42 AM
Event ID: 5719
Task Category: None
This computer was not able to set up a secure session with a domain controller in domain FORTISSECURITY 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.
- Edited by Dave1023 Friday, February 01, 2013 1:00 PM
Monday, February 04, 2013 7:06 AMModerator
First, make sure configure the correct DNS settings in your domain as below:
Best practices for DNS client settings on Domain Controller.
Then，Event ID 5719 can be caused by many factors, such as network connectivity, non-paged memory leak occurs in Tcpip.sys, or out of buffer space in the NetBT datagram buffer.
Refer to the below link for corresponding steps of the error "This computer was not able to set up a secure session with a domain controller":
Active Directory: Event ID 5719 Source Netlogon (dsforum2wiki)
Hope it helps.