How to replace domain controller that died

My domain controller died and it held the FSMO and RID. This also my DHCP server.  Now I am getting bounce of DNS  error on the new DC server and secondary DC. Also, I am getting error when logging in remotely using the hostname (but not on IP address) and accessing a network shared drive.

Below are some of the error encounter.

"The server's clock is not synchronized with the primary domain clock"
"DNS lookup failure caused replication to fail"
"This directory server has not received replication information from a number of directory servers within the configured latency interval."
"Active Directory Domain Services could not resolve the following DNS host name of the source domain controller to an IP address. This error prevents additions, deletions and changes in Active Directory Domain Services from replicating between one or more domain controllers in the forest. Security groups, group policy, users and computers and their passwords will be inconsistent between domain controllers until this error is resolved, potentially affecting logon authentication and access to network resources. "
tomfontanillaAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Ganesh Kumar ASr Infrastructure SpecialistCommented:
There are plenty of things you need to do, if you dont have backup you can still bring back the existing Addl. Domain controller converted as PDC (primary domain controller).

a) I have question are you have had dead and addl. DC in the same site?
b) What is the AD Windows Server version?

Let me explain, the primary domain controller is dead. It hosted DNS, DHCP, NTP roles thats why you are getting error. Now you need to convert the secondary (additional DC) to primary. Follow the below steps.

a) First sieze the role from addl. DC -  
b) Assign or transfer the foles to secondary DC - https://support.microsoft.com/kb/255504%20

c) Configure DHCP again or if you have DHCP backup restore. http://technet.microsoft.com/en-us/library/cc736344(v=ws.10).aspx

d) Set NTP server configuration : http://support.microsoft.com/kb/816042

e) Finally remove the dead server entry by : http://www.experts-exchange.com/Software/Server_Software/Active_Directory/A_677-How-to-Remove-a-Failed-Domain-Controller.html
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
tomfontanillaAuthor Commented:
Hi GaneshKumar Anand,


I tried this "a) First sieze the role from addl. DC -  
b) Assign or transfer the foles to secondary DC - https://support.microsoft.com/kb/255504%20
from another site when i was doing research, but did not work. I was getting an error not able to establish trust with the primary domain controller.
0
tomfontanillaAuthor Commented:
also, below recommendation wont work, because i don't have backup of the DHCP data from the dead domain controller.

c) Configure DHCP again or if you have DHCP backup restore. http://technet.microsoft.com/en-us/library/cc736344(v=ws.10).aspx
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

Ganesh Kumar ASr Infrastructure SpecialistCommented:
Do you have backup of AD which died?

Do you have any other DC's on the same site? Is it possible to bring back the original server hardware?

What is windows version?

Can you post the exact error when you try to sieze or transfer fsmo?
0
tomfontanillaAuthor Commented:
Do you have backup of AD which died? No

Do you have any other DC's on the same site? Is it possible to bring back the original server hardware? Yes, and NO

What is windows version? Windows 2008R2

Can you post the exact error when you try to sieze or transfer fsmo?

"Win32 error returned is 0x20af (The requested FSMO operation failed. The current FSMO role holder could not be contacted.)"
0
Ganesh Kumar ASr Infrastructure SpecialistCommented:
Try this command from second DC : c:\netdom query fsmo

This is an solution for the error you got while siezure of FSMO roles :
http://support.microsoft.com/kb/2001165
0
tomfontanillaAuthor Commented:
Hi GaneshKumar Anand,

I just tried this, expand all tress and i could not find  CN=System.

Please advise.
0
Ganesh Kumar ASr Infrastructure SpecialistCommented:
Please post the snapshot.

adsi.png
when you click start>run>adsiedit.msc you will see a window with default naming context, just click next you will get the adsi console like the attached snapshot.

Please come on chat for speedy resolution skype : ganeshkumar.anand
0
tomfontanillaAuthor Commented:
Works!
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.