Re: Corrupt AD cannot contact any domain controllers
From: Chriss3 (noSpamHere_at_chrisse.se)
Date: 03/02/04
- Next message: Chris: "Re: Domains and Trust"
- Previous message: Steve: "Re: Delegation issues"
- In reply to: Nathan Coppersmith: "Corrupt AD cannot contact any domain controllers"
- Messages sorted by: [ date ] [ thread ]
Date: Tue, 2 Mar 2004 02:31:23 +0100
Nathan have you seen the follow articles?
Using the DCPROMO /FORCEREMOVAL Command to Force the Demotion of Active
Directory Domain Controllers:
http://support.microsoft.com/default.aspx?kbid=332199
HOW TO: Remove Data in Active Directory After an Unsuccessful Domain
Controller Demotion:
http://support.microsoft.com/default.aspx?scid=kb;en-us;216498
HOW TO: Remove Orphaned Domains from Active Directory:
http://support.microsoft.com/default.aspx?scid=kb;en-us;230306
-- Regards Christoffer Andersson No email replies please - reply in the newsgroup "Nathan Coppersmith" <ncoppersmith@bhsins.com> skrev i meddelandet news:ehWs%23h%23$DHA.1452@TK2MSFTNGP09.phx.gbl... > Ok, we recently upgraded the hardware on three servers. This was done > incrementally by pulling one out, installing new, and moving back into AD. > The bad part was that we didn't bother to run DCPromo to remove AD from any > of them, so after the last "original" server was reconfiged, everything > kinda went to pieces. > > So today the OS on our Exchange server corrupted and had to be reinstalled. > During the install, because a domain controller for our original domain > cannot be contacted (despite the two left being installed as such) I had to > create a new domain. Now I want to get my other two servers into my new > domain to tidy things up, but they cannot contact a suitable domain > controller so DCPromo isn't working. > > I've gone in and manually removed references to all the old servernames with > NTDSUTIL (or whatever the util is called), both the old servers are > installed as domain controllers, the FSO roles have been seized by one of > the remaining servers, and the global catalog has been designated on the > other. > > Essentially I have one "healthy" AD domain just created today, and two > servers part of a "sick" AD from earlier rebuilds. I've gone through just > about every Technet article that I can find, but none of them fix the > problem of the two domain controllers not realizing that they really are > domain controllers. (And they write events to the event log stating how a > domain controller cannot be found). > > Anyone have any ideas? I'd like to get the two servers out of the "sick" > Tree and into the "healthy" Tree that I created today, preferably without > reinstalling the OS. > > -- > Nathan Coppersmith > Director, Information Services > Berends Hendricks Stuit Insurance
- Next message: Chris: "Re: Domains and Trust"
- Previous message: Steve: "Re: Delegation issues"
- In reply to: Nathan Coppersmith: "Corrupt AD cannot contact any domain controllers"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
