PROBLEM:How to bring online a domain controller (DC) that was offline for an extended amount of time?
ActiveDirectory_DomainService 1865 "The Knowledge Consistency Checker (KCC) was unable to form a complete spanning tree network topology. As a result, the following list of sites cannot be reached from the local site."
ActiveDirectory_Domain_Service 1311 "The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition."
ActiveDirectory_Domain_Service 1566 "All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable."
DNS-Server-Service 4013 "The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed."
Above and beyond these issues using the portqry.exe tool I was able to figure out that the server was not listening on any of the relevant domain controller ports, TCP 137-139 or UDP port 53.
TROUBLE SHOOTINGRepadmin /syncall /AdePq- Performs a synchronization for a server with all of its replication partners, the modifiers help in performing the sync in a multisite environment
Repadmin /replsum- Summarizes the state of replication of the forest
Repadmin /kcc *- Forces a recalculation of the topology, has the effect of rebuilding the automatically created partner connections in Sites and Services
Dcdiag /test:Connectivity- dcdiag over all is great, but using the /test modifier you are able to run only specific tests as needed
SOLUTION:1.) Open "Sites and Services", and move the problem DC into a site with a working DC.
2.) Open an Administrative Command Prompt (CMD running as Admin).
3.) Run the following commands.
repadmin /kcc *repadmin /syncall.