Forum Discussion
DC issiues
- On DC03 I'd disable the unused adapter
- On dc02 connection properties has a DNS error 1.12.0.61 should be 10.12.0.61
- you didn't post the problem member so I can't tell what issue there might be there.
- Looks like there may be replication problems so I'd check the event logs on each domain controller and correct the issues found.(please don't forget to mark helpful replies)
goes down then everthing stop working
I'd check the DHCP server is handing out other domain controller IP's as alternate DNS to the problem members.
1) the dc are statically assigned and none of them point to this dc including itself.
2) check dns server nothing is pointing to this dc
None of that makes any sense.
Please run;
- dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
- repadmin /showrepl >C:\repl.txt
- ipconfig /all > C:\dc1.txt
- ipconfig /all > C:\dc2.txt
- (etc. as other DC's exist)
- ipconfig /all > C:\problemworkstation.txt
then put unzipped text files up on OneDrive and share a link
Dave Patrick let me try to clarify we have 4 from dc2 to dc5 . there are a mixture of 2013 and 2016
When dc02 goes down anyone who has not logged into the domain yet will not log in
Anywho has login prior still will able to login since its cache
We also have thin clients that no longer can not login into our domain if dc02 goes down again no other dc has this effect
The Thin client is the best way for me to test this since even after login it does not cache login
The DC02 has a static IP with static DNS all dc do.
The DNS of DC2 points to dc04 and dc05
every other dc dns point to other dc none of them point to dc02
The dchp configuration has nothing point to or referring to dc02
I enclosed all you want in a zip file
