Active Directory Services Can't Connect to Domain

Question

I removed Active Directory services form a server running 2012. I then went to reinstall and reconfigure it, but I keep running into issues. When I launch active directory admin center it gives me an error that it can't connect to any domain, and I can't
make any changes. The local server has already been promoted to the domain controller. Here is the output from dcdiag:
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = ACSSVR
   * Identified AD Forest. 
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\ACSSVR
      Starting test: Connectivity
         ......................... ACSSVR passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\ACSSVR
      Starting test: Advertising
         Fatal Error:DsGetDcName (ACSSVR) call failed, error 1355
         The Locator could not find the server.
         ......................... ACSSVR failed test Advertising
      Starting test: FrsEvent
         ......................... ACSSVR passed test FrsEvent
      Starting test: DFSREvent
         There are warning or error events within the last 24 hours after the
         SYSVOL has been shared.  Failing SYSVOL replication problems may cause
         Group Policy problems. 
         ......................... ACSSVR failed test DFSREvent
      Starting test: SysVolCheck
         ......................... ACSSVR passed test SysVolCheck
      Starting test: KccEvent
         A warning event occurred.  EventID: 0x80000B46
            Time Generated: 03/02/2015   12:00:00
            Event String:
            The security of this directory server can be significantly enhanced by configuring the server to reject SASL (Negotiate,  Kerberos, NTLM, or Digest) LDAP binds that do not request signing (integrity verification)
and LDAP simple binds that  are performed on a cleartext (non-SSL/TLS-encrypted) connection.  Even if no clients are using such binds, configuring the server to reject them will improve the security of this server. 
         A warning event occurred.  EventID: 0x80000734
            Time Generated: 03/02/2015   12:00:37
            Event String:
            The local domain controller could not connect with the following domain controller hosting the following directory partition to resolve distinguished names. 
         ......................... ACSSVR passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... ACSSVR passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... ACSSVR passed test MachineAccount
      Starting test: NCSecDesc
         ......................... ACSSVR passed test NCSecDesc
      Starting test: NetLogons
         Unable to connect to the NETLOGON share! (\\ACSSVR\netlogon)
         [ACSSVR] An net use or LsaPolicy operation failed with error 67,
         The network name cannot be found..
         ......................... ACSSVR failed test NetLogons
      Starting test: ObjectsReplicated
         ......................... ACSSVR passed test ObjectsReplicated
      Starting test: Replications
         ......................... ACSSVR passed test Replications
      Starting test: RidManager
         ......................... ACSSVR passed test RidManager
      Starting test: Services
         ......................... ACSSVR passed test Services
      Starting test: SystemLog
         A warning event occurred.  EventID: 0x000003F6
            Time Generated: 03/02/2015   11:21:34
            Event String:
            Name resolution for the name teredo.ipv6.microsoft.com. timed out after none of the configured DNS servers responded.
         A warning event occurred.  EventID: 0x000727A5
            Time Generated: 03/02/2015   11:21:58
            Event String:
            The WinRM service is not listening for WS-Management requests. 
         An error event occurred.  EventID: 0xC0001B58
            Time Generated: 03/02/2015   11:26:01
            Event String:
            The Vstor2 Virtual Storage Driver service failed to start due to the following error: 
         An error event occurred.  EventID: 0xC0001B58
            Time Generated: 03/02/2015   11:26:01
            Event String:
            The Vstor2 MntApi 2.0 Driver (shared) service failed to start due to the following error: 
         A warning event occurred.  EventID: 0x000003F6
            Time Generated: 03/02/2015   11:26:16
            Event String:
            Name resolution for the name teredo.ipv6.microsoft.com. timed out after none of the configured DNS servers responded.
         An error event occurred.  EventID: 0x0000002E
            Time Generated: 03/02/2015   11:34:32
            Event String:
            The time service encountered an error and was forced to shut down. The error was: 0x80070700: An attempt was made to logon, but the network logon service was not started.
         An error event occurred.  EventID: 0xC0001B6F
            Time Generated: 03/02/2015   11:34:32
            Event String:
            The Windows Time service terminated with the following error: 
         A warning event occurred.  EventID: 0x000727A5
            Time Generated: 03/02/2015   11:35:01
            Event String:
            The WinRM service is not listening for WS-Management requests. 
         A warning event occurred.  EventID: 0x000003F6
            Time Generated: 03/02/2015   11:39:08
            Event String:
            Name resolution for the name _ldap._tcp.dc._msdcs.ACS.local. timed out after none of the configured DNS servers responded.
         An error event occurred.  EventID: 0xC0001B58
            Time Generated: 03/02/2015   11:39:27
            Event String:
            The Vstor2 Virtual Storage Driver service failed to start due to the following error: 
         An error event occurred.  EventID: 0xC0001B58
            Time Generated: 03/02/2015   11:39:27
            Event String:
            The Vstor2 MntApi 2.0 Driver (shared) service failed to start due to the following error: 
         A warning event occurred.  EventID: 0x000727AA
            Time Generated: 03/02/2015   11:39:40
            Event String:
            The WinRM service failed to create the following SPNs: WSMAN/ACSSVR.ACS.local; WSMAN/ACSSVR. 
         A warning event occurred.  EventID: 0x0000000C
            Time Generated: 03/02/2015   11:39:39
            Event String:
            Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in
the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the
authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
         A warning event occurred.  EventID: 0xC000042B
            Time Generated: 03/02/2015   11:42:01
            Event String:
            The RD Session Host server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: The specified domain either does not exist or could not be contacted.
         An error event occurred.  EventID: 0x00000469
            Time Generated: 03/02/2015   11:44:31
            Event String:
            The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain
controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
         An error event occurred.  EventID: 0x00000469
            Time Generated: 03/02/2015   11:45:05
            Event String:
            The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain
controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
         An error event occurred.  EventID: 0x0000168F
            Time Generated: 03/02/2015   11:55:22
            Event String:
            The dynamic deletion of the DNS record 'ACS.acsolutionsinc.net. 600 IN A 192.168.56.1' failed on the following DNS server:  
         A warning event occurred.  EventID: 0x000003F6
            Time Generated: 03/02/2015   11:55:22
            Event String:
            Name resolution for the name acsolutionsinc.net timed out after none of the configured DNS servers responded.
         An error event occurred.  EventID: 0x0000168F
            Time Generated: 03/02/2015   11:55:47
            Event String:
            The dynamic deletion of the DNS record '_ldap._tcp.ACS.acsolutionsinc.net. 600 IN SRV 0 100 389 ACSSVR.ACS.acsolutionsinc.net.' failed on the following DNS server:  
         A warning event occurred.  EventID: 0x000727A5
            Time Generated: 03/02/2015   11:55:53
            Event String:
            The WinRM service is not listening for WS-Management requests. 
         A warning event occurred.  EventID: 0x000003F6
            Time Generated: 03/02/2015   11:55:53
            Event String:
            Name resolution for the name _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.ACS.local. timed out after none of the configured DNS servers responded.
         A warning event occurred.  EventID: 0x000003F6
            Time Generated: 03/02/2015   11:59:53
            Event String:
            Name resolution for the name _ldap._tcp.dc._msdcs.ACS.local. timed out after none of the configured DNS servers responded.
         An error event occurred.  EventID: 0xC0001B58
            Time Generated: 03/02/2015   12:00:13
            Event String:
            The Vstor2 Virtual Storage Driver service failed to start due to the following error: 
         An error event occurred.  EventID: 0xC0001B58
            Time Generated: 03/02/2015   12:00:13
            Event String:
            The Vstor2 MntApi 2.0 Driver (shared) service failed to start due to the following error: 
         A warning event occurred.  EventID: 0x000727AA
            Time Generated: 03/02/2015   12:00:25
            Event String:
            The WinRM service failed to create the following SPNs: WSMAN/ACSSVR.ACS.local; WSMAN/ACSSVR. 
         A warning event occurred.  EventID: 0x0000000C
            Time Generated: 03/02/2015   12:00:25
            Event String:
            Time Provider NtpClient: This machine is configured to use the domain hierarchy to determine its time source, but it is the AD PDC emulator for the domain at the root of the forest, so there is no machine above it in
the domain hierarchy to use as a time source. It is recommended that you either configure a reliable time service in the root domain, or manually configure the AD PDC to synchronize with an external time source. Otherwise, this machine will function as the
authoritative time source in the domain hierarchy. If an external time source is not configured or used for this computer, you may choose to disable the NtpClient.
         A warning event occurred.  EventID: 0xC000042B
            Time Generated: 03/02/2015   12:02:47
            Event String:
            The RD Session Host server cannot register 'TERMSRV' Service Principal Name to be used for server authentication. The following error occured: The specified domain either does not exist or could not be contacted.
         An error event occurred.  EventID: 0x00000469
            Time Generated: 03/02/2015   12:05:17
            Event String:
            The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain
controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
         An error event occurred.  EventID: 0x00000469
            Time Generated: 03/02/2015   12:05:17
            Event String:
            The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain
controller and Group Policy has successfully processed. If you do not see a success message for several hours, then contact your administrator.
         ......................... ACSSVR failed test SystemLog
      Starting test: VerifyReferences
         ......................... ACSSVR passed test VerifyReferences
   Running partition tests on : Schema
      Starting test: CheckSDRefDom
         ......................... Schema passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Schema passed test CrossRefValidation
   Running partition tests on : Configuration
      Starting test: CheckSDRefDom
         ......................... Configuration passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... Configuration passed test CrossRefValidation
   Running partition tests on : ACS
      Starting test: CheckSDRefDom
         ......................... ACS passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... ACS passed test CrossRefValidation
   Running enterprise tests on : ACS.local
      Starting test: LocatorCheck
         Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
         A Global Catalog Server could not be located - All GC's are down.
         Warning: DcGetDcName(TIME_SERVER) call failed, error 1355
         A Time Server could not be located.
         The server holding the PDC role is down.
         Warning: DcGetDcName(GOOD_TIME_SERVER_PREFERRED) call failed, error
         1355
         A Good Time Server could not be located.
         Warning: DcGetDcName(KDC_REQUIRED) call failed, error 1355
         A KDC could not be located - All the KDCs are down.
         ......................... ACS.local failed test LocatorCheck
      Starting test: Intersite
         ......................... ACS.local passed test Intersite
I've been trying to debug errors one at a time, but I'm having a hard time finding any information that pertains to this issue as a whole. Anything you can tell me about this would be great, thank you for reading. 

Answer 1

It was the only server in the network, the only dc in the old forest. When I re-installed ad ds I gave the new forest different name, but I guess the old settings are still in the system somewhere conflicting with the new setup? Is there a way to
purge the old setup entirely and start over with ad ds, or am I going to have to re-install the whole OS? Thanks again for the help.
Honestly, the best way to handle this is to rebuild the server. There are many things that are "left behind" when you remove the Domain / Forest from a Domain Controller. In fact many articles will say after using ADMT (active directory migration
tool) you should decommission the original Domain Controller (aka reinstall the OS).
While you could spend more time trying to get that domain controller working, it absolutely is going to be 1) More reliable 2) faster to reinstall the OS on the old domain controller. If you are still leveraging storage, or services on that domain controller,
you will want to back them up, or have a transition plan before reinstalling everything on the server. I have a feeling if you choose to keep troubleshooting this, you will run into more issues down the road.
Entrepreneur, Strategic Technical Advisor, and Sr. Consulting Engineer - Strategic Services and Solutions Check out my book - Powershell 3.0 - WMI: http://amzn.to/1BnjOmo | Mastering PowerShell Coming in April 2015!