having issues with a restored dc in vmware

Im doing a dr test off our virtual servers and my dc isnt working correctly. For a sample test I restored a few servers including the DC, all looks fine I can console into them but I cannot logon to a none dc server using domain creds it states domain cannot be found. I have verified the clocks on all the servers are correct. I was able to remove one server from the domain but when I attempted to re-join the domain I got the same error cant connect to domain. Our DC is also a file share and I can access those from the other servers or my laptop and when the dc does log the security event and shows Im using a domain account to connect to the file share but when my domain logon fails when logging on to a device I DO NOT get a security log error from it, I dont get any log from the attempt on the dc. I can ping back and forth between servers. Any ideas???????????
My servers are 2003 2003 R2
Im using ESXI 5.0.0
bankadminAsked:
Who is Participating?
 
bankadminConnect With a Mentor Author Commented:
This is what I ended up doing to get it to work


1.       Stop the File Replication service on the domain controller.

2.       Start Registry Editor (Regedt32.exe).

3.       Locate and then click the BurFlags value under the following key in the registry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NtFrs\Parameters\Backup/Restore\Process at Startup

4.       On the Edit menu, click DWORD, click Hex, type D4, and then click OK.

5.       Quit Registry Editor.

6.       Move data out of the PreExisting folder.

7.       Restart the File Replication Service.
0
 
Chris HInfrastructure ManagerCommented:
Is this the only domain controller?  If not, I recommend only restoring one DC out of the group (Definitely a global catalog server) and seizing all FSMO roles.  Then adjust DHCP and DNS along with removing any abandoned domain controllers:


Seize roles
http://support.microsoft.com/kb/255504

Delete abandoned DC(s):
http://support.microsoft.com/kb/555846
0
 
IanThCommented:
have you got restore mode passwords for the dc ?
0
Never miss a deadline with monday.com

The revolutionary project management tool is here!   Plan visually with a single glance and make sure your projects get done.

 
Andrew Hancock (VMware vExpert / EE MVE^2)VMware and Virtualization ConsultantCommented:
could you describe layout?

one dc, or two dcs.

how did you restore, using what?

check eventlogs, dcdiag etc
0
 
Chris HInfrastructure ManagerCommented:
Also, when you restore a windows 2003 machine in VMWARE, it recognizes the new NIC card and re-installs (even though it's the same hardware).  A lot of the time, this re-enables DHCP on the client nic of the restored server.  Validate that your IP address is correct on the domain controller and  that your SRV records match accordingly in DNS.
0
 
bankadminAuthor Commented:
Im using Veeam 5.0.230 to restore the backups. I do have more than on DC but I have only restored the 1 for the tests. I wont be getting back down to our DR site until next tuesday to follow up on this so any suggestions I will try then.

I did check the event logs and nothing stuck out to me as being the issue.
I did not validate the IP address but I will once I get back down there.
0
 
Chris HInfrastructure ManagerCommented:
Checklist i'd recommend:

Restore DC with Global catalog
--It doesn't have to be a GC if you only have one root domain and no child domains, but you must enable the Global Catalog checkbox on the server you restore in order for clients to authenticate.

Make sure IP is correct.
Make sure DNS SRV records reflect the correct IP address for restored global catalog (GC)
Make sure global catalog checkbox is checked
Seize rolls
Remove abandonned DCs
Adjust DNS server on test client and test join domain.

I do this weekly.
0
 
bankadminAuthor Commented:
it worked
0
All Courses

From novice to tech pro — start learning today.