KPI1
asked on
Active Directory Services Won't start. DNS has no domain informaton
We recently installed Active Directory services on a member server (small client that has only 1 server). Everything went fine (dcpromo and all that good stuff). This is Windows 2008 R2 Standard.
For several weeks everything was fine, then Active Directory Services stopped. If you try to restart, it fails, yet nothing is logged in the Event log. Very puzzling. DNS has no entry for the domain. If I try to run Dcpromo again, it does list the domain.local that was present, but can't start it again (since there is no DC to query). tried to regtlibv12 actieds.tlb to no avail.
Any suggestions?
For several weeks everything was fine, then Active Directory Services stopped. If you try to restart, it fails, yet nothing is logged in the Event log. Very puzzling. DNS has no entry for the domain. If I try to run Dcpromo again, it does list the domain.local that was present, but can't start it again (since there is no DC to query). tried to regtlibv12 actieds.tlb to no avail.
Any suggestions?
ASKER
Yes, it's like it never existed. We hadn't yet taken a backup. We were just about to implement our backup device but this occurred first. I really want to avoid creating a new AD, everyone getting new profiles, etc.
Did someone do a restore or system resotre to an eariler date on this machine?
If this is your old DC in the domain then you will need to restrore it from backup.
Will.
If this is your old DC in the domain then you will need to restrore it from backup.
Will.
is it pointing to itself for dns?
have you looked at event logs? i would go back to see when these problems began and try to figure out if someone changed something at that time
have you looked at event logs? i would go back to see when these problems began and try to figure out if someone changed something at that time
OOoooooh my, I've been down this road before when testing DR with Backup Exec Veritas on bare metal restores using VMware with a replicating AD domain. I think I know where you should start. Honestly the first place you should look is the disk itself. Make sure it hasn't run out of space. Then look into the NTDS database and verify permissions and fragmentation, and finally check the NTDS Replication configuration and rebuild the replication configurations on both sides using replmon. Try those first., especially replmon to help you track down things.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Nothing else worked.
Have you taken a backup of the Active Directory server using a System State backup?
Will.