after demoting DC, can't contact domain controller
Posted on 2008-11-17
Computers on domain dont get connected to shares or printers automatically (can be mapped manually).
active directory is configured improperly somewhere and its not recognizing 2k3 DC "a" as the DC since the original 2k DC was demoted (I swear I followed all appropriate steps by transfering FSMO roles and seizing the them on the old DC). The AD is visible and running. However, it's not being acknowledged that 2k3 DC "a" as the primary DC. I thought it might be because its 2k3, but its running in mixed mode which means it can play with 2k servers. I checked the following:
-srv records on the dns server (which is not a DC) and appears that all the neccessary entries exist
-nslookup, set type=all, Type _ldap._tcp.dc._msdcs.(Domain_Name) and responded with the right ip addresses
-ran netdiag and notice this error message: "the system volume has not been completely replicated to the local machine. this machine is not working properly as a dc".
Appears that the old 2k DC was holding on to something and it didn't properly transfer over. I don't know what i missed; i thought all i had to do was transfer FSMO roles, seize the old one, and demote..as soon as i demoted, "can't contact domain controller".