Server DNS issue and Second DC

[Shadow_Walker]

One of our domain controllers seems to have tripped itself over whilst i was away. It is throwing back a lot of errors mainly DNS however no fixes seem to be working. Our second DC is handling requests fine however the other DC will log them in however not all GPOs are working. I have found a client which is trying to connect to the Main DC is there a way i can force clients to use the second DC just for the time being?

[Davit2005]

One of our domain controllers seems to have tripped itself over whilst i was away. It is throwing back a lot of errors mainly DNS however no fixes seem to be working. Our second DC is handling requests fine however the other DC will log them in however not all GPOs are working. I have found a client which is trying to connect to the Main DC is there a way i can force clients to use the second DC just for the time being?

 

Run the DCDIAG tests with all the relevant switches at the command prompt. We had an issue with one DC at the last place on few occasions and it simply required a reboot. I think we solved it permanently but can't remmeber how. We found the problematic DC by being on a PC which was trying to logon but taking ages, when it did finally log us on we ran %logonserver% at the run box to see what server we were logged into.

Edited September 1, 2017 by Davit2005

[Shadow_Walker]

I ran the %logonserver% and it is saying the backup one but when I ping .local it gives me the ip of the first DC.

[Shadow_Walker]

Let's say if I turned off the Main DC should the second one service all requests?

[Davit2005]

It should do, how about DNS and DHCP, are both servers running the same services? Is their any service on one DC but not the other?