This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(124.80000000000001, 66%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMH%3C/text%3E%3C/svg%3E)
I have a Server 2008R2 domain controller. I run Azure AD Connect to sync the AD up to Azure so I can authenticate my Office 365 against it. Azure AD Connect stopped syncing. I went looking as to why.
I discovered that DNS was not running on the server anymore. It couldn't load the AD zones because AD wasn't up. I did indeed see errors in AD.
I went to check my Server 2019 domain controller, only to figure out that it wasn't a domain controller after all.
I have a pair of old Server 2003 boxes that were still domain controllers but powered down. I powered them up. One of them still has DNS running and is mostly complete. I did a variety of restarts and troubleshooting to see why my 2008 box wasn't coming back alive, but no success. If I point the NIC DNS to the 2003 box running DNS, dcdiag reports fewer errors, but I have little confidence that it's actually working any better, given that it was a powered down DC.
I can create a new user in the 2008 Users and Computers and login to it via RDP, so not everything is hosed. I'm kind of stuck where to go from here.
I've attached an output of: Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.txt
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(176, 16%, 27%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EHX%3C/text%3E%3C/svg%3E)
Hello,
Thank you so much for posting here.
We are checking in to see if the provided information was helpful. If the reply is helpful, we would appreciate you to accept it as answer.
Please let us know if you would like further assistance. Thanks.
Best Regards,
Hannah Xiong
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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
ipconfig /all > C:\dc3.txt
then put unzipped text files up on OneDrive and share a link.
I'm having issues logging into dc3, so I don't yet have it's ipconfig.
svr-file-rch remove 208.89.144.170 listed for DNS
DNA-170 is multi-homed and should have a single adapter addressed on LAN with own static ip address listed for DNS and no others such as router or public DNS
These were show stoppers so I did not look at other files. If problems persist after fixing these items put up new files to look at.
--please don't forget to Accept as answer if the reply is helpful--
I have uploaded new files, just now in the v3 subfolder.
Looks like you ran dcdiag on DNA-170 which was never initialized so likely is unusable. Might try the others, also missing the ipconfig /all file for the third one. Also check the route exists between the networks 208.89.144.161 <-> 192.168.8.1 and no firewalls blocking required ports.
https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/config-firewall-for-ad-domains-and-trusts
--please don't forget to Accept as answer if the reply is helpful--