Answered by:
Primary DC Not Coming back up and syncing

-
I have a problem. We have two DC's at one site. DC1 (dbserver) and DC1(DC10). DC2 is operating fine and is 2k8R2 server, DC1 is SBS 2011 and is not doing so well. I tried restores from three different backups and none are working properly. DC1 exchange, ad, dns, are not working properly. I thought this started as a DNS issue, now it seems to be a AD issue. Here is the dcdiag:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = DBSERVER
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\DBSERVER
Starting test: Connectivity
The host 8a83a76e-e7a5-47fc-8818-522e9d1d02f2._msdcs.db.local could
not be resolved to an IP address. Check the DNS server, DHCP, server
name, etc.
Got error while checking LDAP and RPC connectivity. Please check your
firewall settings.
......................... DBSERVER failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\DBSERVER
Skipping all tests, because server DBSERVER is not responding to
directory service requests.
Running partition tests on : ForestDnsZones
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Running partition tests on : DomainDnsZones
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
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 : db
Starting test: CheckSDRefDom
......................... db passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... db passed test CrossRefValidation
Running enterprise tests on : db.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(KDC_REQUIRED) call failed, error 1355
A KDC could not be located - All the KDCs are down.
......................... db.local failed test LocatorCheck
Starting test: Intersite
......................... db.local passed test Intersite
Any help or direction is appreciated!
Question
Answers
-
Hi,
Thanks for posting in the forum.
Regarding the issue, since Dcdiag.exe does not pass the FsmoCheck test and generates the error 1355, I suggest you could refer to the following article for troubleshooting. As it mentioned, the issue generally occurs only if the domain controller that you restore is the only domain controller in the domain, or if all of the domain controllers in the domain have also been restored.
The Sysvol and Netlogon Shares Are Missing After You Restore a Domain Controller from Backup
http://support.microsoft.com/kb/316790
In addition, you mentioned these two DCs failed to sync with each other, please also refer to the following article to troubleshoot the replication issue.
Troubleshooting Active Directory Replication Problems
http://technet.microsoft.com/en-us/library/cc738415(v=ws.10).aspx
Hope this helps.
Best Regards,
Andy Qi
- Marked as answer by Andy QiMicrosoft contingent staff, Moderator Monday, November 04, 2013 5:35 PM