Almost every computer on campus has the problem that I will be describing. This option is located in:Computer Configuration > Administrative Templates > System > LogonIn our situation this option was already turned on.Issue was fixed by enabling "Startup Policy Processing Wait Time" and Afterward, Group Policy applies every 90 to 120 minutes. All the DNS servers are our own. this contact form
This setting is located under Computer Configuration\Administrative Templates\System\Logon in the Group Policy Object Editor. For IT career related questions, please visit /r/ITCareerQuestions Please check out our Frequently Asked Questions, which includes lists of subreddits, webpages, books, and other articles of interest that every sysadmin should NETLOGON 5719 : This computer was not able to set up a secure session with a domain controller in domain OURDOMAIN due to the following: There are currently no logon servers permalinkembedsaveparentgive gold[–]talmx6 4 points5 points6 points 4 years ago(0 children)I had a similar hair-tearing situation at one of my clients recently.
We have more than 3000 Windows Desktops situated in roughly 20+ buildings around campus. Go to an affected machine and telnet dc1 389: Does this connect or timeout? They exhibit the same problems. dc4.ourdomain.edu 1:26:18 - The LDAP call to connect and bind to Active Directory completed.
Below are a bunch of logs: First being the netlogon.log file: http://pastebin.com/XKksB6ZA