W2K domain controller has wrong FQDN


I have a domain (DOMAIN1) with 4 Windows domain controllers. One is Windows 2003/Exchange and the others are Windows 2000 file servers.

I need to demote one of the w2k servers and remove it permanently from AD. The problem I'm having is that it is a member of DOMAIN1 but the actual name of the server is "server.DOMAIN2.com". How this happened, I don't know, but it seems to be causing problems where this server cannot replicate with the others.
I cannot run dcpromo successfully on this DC or rename it in its present state. Should I force demotion on this server and  then run ntdsutil on the other DCs to clean them up?  Is there a way I can play with my DNS settings to get this thing to replicate properly?

Can anyone suggest a solution to this problem?

Thanks very much!
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.

Chris DentPowerShell DeveloperCommented:

Is everything except that server replicating properly? You've tried DCDiag and such?

If so, I'd go with turning it off then cleaning it up afterwards (with NTDSUtil as you suggest). Then I'd strongly recommend you rebuild the system completely.


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
Check against your DNS record first. The name may probablly mistyped. After force removal of that w2k DC. try to delete the DC inside dsa.msc as well. and Check the DC cannot be contacted and permenta offline option. After that, run site and services and try to replicate to all other DC. GOod Luck
cacv12000Author Commented:
Thanks guys. When I force replication, the other 3 DC are replicating okay against the bad one. The bad one however is not replicating against the other three. I'm going to force demotion sometime in the next few days. I'll let you know how it turns out.
Chris DentPowerShell DeveloperCommented:

Good luck, yell if there are any problems.

cacv12000Author Commented:
The server demoted properly so all my worrying was for nothing...

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.