Re: How to recover from DC without GC?


"Per Hagstrom" <per.hagstrom@xxxxxxxxxxxxxx> wrote in message
news:eBQmxYfOHHA.4172@xxxxxxxxxxxxxxxxxxxxxxx
OK, the reason I asked was when I first tried to promote it and make it
GC, it complained it couldn't find the "domain", the DNS didn't work, A.D
didn't work and so on... but now after waiting a while, it had actually
recreated itself somehow... !

Only problem now is when I tried to join a new server to become another
DC, it complained again about domain not found... strange.. maybe that's
part of the metadata cleanup?

You've got DNS problems. DNS is the MAIN cause of both authentication
and replication issues in Windows AD domains, and authentication PLUS
replication is required for DCPromo (authenticate you the admin, and
replicate
the new DC etc.)

The new server must use STRICTLY the DNS server that knows (how to find)
the DNS zone which supports AD.

So must the existing DC and all other domain machines on the NIC->IP
properties.

You zone must be dynamic. The DC must be registered and it should be able
to pass a full DCDiag (support tools from server CDRom). Save text to a
file
and search for FAIL and WARN.

Fix those or post the unedited text from both DC and "new server" output
of: "IPconfig /all >file.txt" as well as DCDiag you did above:


--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)


.

Relevant Pages

  • Re: SBS 2003 and Replication Errors with Remote DC
    ... alpha server as soon as you can to get things going. ... A simple DNS replication test is to create a host record in the SBS server ... Domain Controller Diagnosis ...
    (microsoft.public.windows.server.sbs)
  • Re: SBS 2003 and Replication Errors with Remote DC
    ... I did make the changes that you suggested on the DNS of my alpha server and rebooted. ... I did run the simple DNS test that you suggested by adding a host record to my SBS server. ... A simple DNS replication test is to create a host record in the SBS server and wait till it shows up in the remote server. ...
    (microsoft.public.windows.server.sbs)
  • Re: how do i move primary DC from one machine to another
    ... Test omitted by user request: DNS ... Connecting to directory service on server WIN2003DC. ... Replication Site Latency Check ...
    (microsoft.public.windows.server.general)
  • Re: error 8254 DNS Lookup failure
    ... FYI, I repointed the DNS to one server, deleted the contents of _MSDCS ... > in the same site, Replication has been fine up until yesterday, the ... > Starting test: CrossRefValidation ...
    (microsoft.public.win2000.dns)
  • Re: WINS and DNS issue
    ... > When I said the that DNS server is configured to to replicate to all other ... > properties for our forward lookup zone - We dont actually have another ... replication if you have only one DNS server. ...
    (microsoft.public.win2000.dns)
Loading