Quantcast
Channel: Symantec Connect - Backup and Recovery - Discussions
Viewing all articles
Browse latest Browse all 8635

Possible to reinstate DC after recovery if you didn't check off the option?

$
0
0
I need a solution

Hi,

I had to recover my server from an unexpected rollback yesterday using Backup Exec System Recovery 8.0 to restore an image from earlier in the week (10/29). I didn't realize I needed to check off the Preserve domain trust token on destination option that perserves the Active Directory information when doing the restore and now I have a PDC that cannot communicate with any other computers on my network.  (The network is only 1 PDC which is WIndows 2003 SBS and 5 Windows XP clients.)

When running dcdiag, I am getting the following:

 

C:\Documents and Settings\Administrator>dcdiag 
 
Domain Controller Diagnosis 
 
Performing initial setup: 
   Done gathering initial info. 
 
Doing initial required tests 
 
   Testing server: Default-First-Site-Name\SERVER 
      Starting test: Connectivity 
         The host bd51ce3c-796b-4435-8cdf-df9b31afeb05._msdcs.coltsnecknursery.l 
ocal could not be resolved to an 
         IP address.  Check the DNS server, DHCP, server name, etc 
         Although the Guid DNS name 
         (bd51ce3c-796b-4435-8cdf-df9b31afeb05._msdcs.coltsnecknursery.local) 
         couldn't be resolved, the server name (SERVER.coltsnecknursery.local) 
         resolved to the IP address (192.168.2.5) and was pingable.  Check that 
         the IP address is registered correctly with the DNS server. 
         ......................... SERVER failed test Connectivity 
 
Doing primary tests 
 
   Testing server: Default-First-Site-Name\SERVER 
      Skipping all tests, because server SERVER is 
      not responding to directory service requests 
 
   Running partition tests on : ForestDnsZones 
      Starting test: CrossRefValidation 
         ......................... ForestDnsZones passed test CrossRefValidation 
 
      Starting test: CheckSDRefDom 
         ......................... ForestDnsZones passed test CheckSDRefDom 
 
   Running partition tests on : DomainDnsZones 
      Starting test: CrossRefValidation 
         ......................... DomainDnsZones passed test CrossRefValidation 
 
      Starting test: CheckSDRefDom 
         ......................... DomainDnsZones passed test CheckSDRefDom 
 
   Running partition tests on : Schema 
      Starting test: CrossRefValidation 
         ......................... Schema passed test CrossRefValidation 
      Starting test: CheckSDRefDom 
         ......................... Schema passed test CheckSDRefDom 
 
   Running partition tests on : Configuration 
      Starting test: CrossRefValidation 
         ......................... Configuration passed test CrossRefValidation 
      Starting test: CheckSDRefDom 
         ......................... Configuration passed test CheckSDRefDom 
 
   Running partition tests on : coltsnecknursery 
      Starting test: CrossRefValidation 
         ......................... coltsnecknursery passed test CrossRefValidati 
on 
      Starting test: CheckSDRefDom 
         ......................... coltsnecknursery passed test CheckSDRefDom 
 
   Running enterprise tests on : coltsnecknursery.local 
      Starting test: Intersite 
         ......................... coltsnecknursery.local passed test Intersite 
      Starting test: FsmoCheck 
         ......................... coltsnecknursery.local passed test FsmoCheck 
Also, there are the following messages in the DNS log:
Event Type: Error 
Event Source: DNS 
Event Category: None 
Event ID: 4000 
Date: 11/3/2012 
Time: 11:18:28 PM 
User: N/A 
Computer: SERVER 
Description: 
The DNS server was unable to open Active Directory.  This DNS server is configured to obtain and use information from the directory for this zone and is unable to load the zone without it.  Check that the Active Directory is functioning properly and reload the zone. The event data is the error code. 
 
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. 
Data: 
0000: 2d 23 00 00               -#..    

Is there a way to fix this problem after the fact without resinstalling the OS, rebuilding the network, and then restoring the system checking off the option to preserve the new network information?

Thanks.

Keith


Viewing all articles
Browse latest Browse all 8635

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>