daily DNS failure resolved by stopping and restarting NETLOGON
Each day I have a server that can't contact the GCS(error 1355) and fails DCDIAG tests CONNECTIVITY and FSMOCHECK and reports "Skipping all tests because server GE-PM is not responding to directory service requests"
I found a previous EE article that pointed out some DNS IP config issues with the Primary and Secondary DNS settings. Resolved this by ensuring all DNS role servers had ONLY their own IP addy in the DNS settings. The server in question IS a DNS role server.
This server is also an apllication and DB server for an SQL environment. The above issue appears to be connected to an error in the SQL environment that results in an error message that says "not enough memory to complete the operation." There is over 60 gigs of drive space on all of my servers so it is NOT a hard drive issue.
I believe the DNS failure is preventing access to the SYSVOL share(s) and thus user authentication is failing causing the above app environment error.
My problem is that I can't clear the instability in DNS and keep it running. None of my other DNS servers seem to be having any trouble. I am getting bored with having to stop and restart the NETLOGON service each morning...
If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.