We installed a Windows Server 2016 standard on a network that had a failing Windows 2012 Small Business Server. We made the new 2016 server a domain controller and a DNS server. Our intention was to remove the 2012 server, reinstall the OS and add it back on as a 2nd domain controller. Unfortunately, the server crashed shortly after we installed the new server and management decided not to do anything with it.
I've just noticed that we cannot access AD from our 2016 server. It says it "can't find a domain controller" even though AD shows that it's running as well as DNS is running. My initial investigation into this problem indicated that it may be a DNS issue and the server is not recognize itself as the DNS server (again, even though it's running).
I didn't want to remove the DNS role and re-add it until I investigated this further
I have never experienced this before when adding a server to a network and then taking the old one off line.
Any ideas on what caused this and how to correct it. I can't access active directory on the server so I'm kind of "dead in the water" as far as AD management is concerned.
Thoughts??? jtingley@verizon.net