Primary Domain Controller no longer appears as a Domain Controller, and cannot be contacted.

We are running a Windows Environment, with Server 2003 Enterprise and Standard, with XP and Vista Machines. A week ago, our Primary Domain Controller (also was all the other operation and schema masters, with Global Catalog, and ran DNS and DHCP) stopped DHCP. We assessed the issue and fired DHCP up on another Domain Controller. When looking thru the Event Logs, there was no reason why DHCP failed, furthermore, it would not start up again.

At this point, it was an inconvenience. Like every other IT department we are underfunded and undermanned so we gave it a band-aid and moved on.

This week, we were trying to replace the server that DHCP had failed on, since it was going to be quicker to replace it than fix it. At this point, we believed that it was still functioning on every level beside DHCP, and had no reason to worry. We were wrong. We tried to remove it from the AD environment, and move its services around, correctly. I say "correctly" because later I learned that you are not supposed to have you Infrastructure Master and Global Catalog on the Domain Controller. Oops. But, we were shocked to see that the Domain Controller we will call it DC-01 was not available. The other Domain Controllers were all there. since then,  I have tried all sorts of help documents on forcing server roles around, and now I'm afraid we just have a bit of a mess. I write a out a quick list of what we are dealing with.

Domain Controllers:
DC-01 (formerly it was all the masters, and had Global Catalog) also running DHCP and DNS
DC-02 just Global Catalog and DNS
DC-03 just a Domain Controller, no Global Catalog
Exchange Server - Running with Domain Controller with Global Catalog (runs Exchange 2007)

I have 2 brand new clean Servers getting loaded up with Windows Server 2003 Standard R2 right now to be the main Domain Controllers, so we can get this all cleaned up, and old boxes (DC-02 and DC-03) laid to rest, as far as being Domain Controllers.

I think that is it. Worst case Scenario I will call Microsoft and pay thru the nose to have them slowly hold my hand and walk me thru everything. But, I have better things to do.
arthurpressAsked:
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.

maxis2cuteCommented:
you should transfer the FSMO roles. if replication is a problem, seize the FSMO roles intead. all this is done vua NTDSUTIL

note if seizing the FSMO roles, immediately disconnect the problem machine once done.  cleanup or reformat/reinstall is required afterwards
a clean reinstall after seizing the roles is always the preferred route if you want to avoid future issues. metadump cleaning doesn't have a good record and depending on what corrupted the dc in the first place, it may not restore the server to a pre-dcpromo state.

Do a complete Operating system reinstall, this alwyas works
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
Jay_Jay70Commented:
"""""because later I learned that you are not supposed to have you Infrastructure Master and Global Catalog on the Domain Controller. Oops

ONLY in a child domain environment does that rule apply, your setup is fine :)

Now, if you have a few mins, read through my guide here to get us on the move :)

http://www.damaged-existence.com/internet/ActiveDirectoryProcedures/ReplaceDomainController/tabid/54/Default.aspx
0
maxis2cuteCommented:
Jay Jay, i looked at yor site and it correct me if i am wrong, but it says to use DC promo, i believe this is impossible since it was stated that the DC can not be contacted.  

The FSMO rules will have to be siezed.   please follow these steps

http://articles.techrepublic.com.com/5100-6345_11-5081138.html
0
The Ultimate Tool Kit for Technolgy Solution Provi

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy for valuable how-to assets including sample agreements, checklists, flowcharts, and more!

Jay_Jay70Commented:
says use dcpromo in a happy environment yes - read on to the forceremoval path :) but read it ALL! otherwise it could get messy
0
arthurpressAuthor Commented:
Sorry JayJay, Maxis2Cute solution worked for us. I did read thru your guide, and it looks good. But, I have already learned most of that stuff. Actually I had tried Seizing the FSMO roles before but could only get the PDC and INfrastructure. But this time it was able to get all the roles correctly. I appreciate your guy's lightning fast responses.
0
arthurpressAuthor Commented:
Thank you very much. You saved our domain. And my butt.
0
Jay_Jay70Commented:
careful with the aftermath of sezing....you have a whole load of cleaning to do
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
Active Directory

From novice to tech pro — start learning today.