GC cannot be promoted

  • Thread starter Thread starter Erik Dannstedt
  • Start date Start date
E

Erik Dannstedt

Hi,
I'm running an AD with one root domain and one subdomain.
I want to replace the single DC in the root domain with a new DC but
the new DC cannot propagate it's role as GC.
The error in the Directory Log is 1559 NTDS Replication. Basically it
is saying that:
"A precondition to becoming a GC is that this server host a read-only
copy of all partitions in the enterprise. This server should hold a
copy of partition DC=sub-domain,DC=com but it does not. This system
will not be promoted to a GC until this condition is met."

The problems similair to this I've encountered is about orphand
domain. This one is not orphand.

NetDiag och DCDiag is fine. Well, DCDiag complains that the new server
cannot propagate it's role as GC and tells me to check for KCC errors.

Any ideas would be greatly appreciated!

/Erik Dannstedt
 
How many DCs in the root domain?
Try a repadmin /showreps on this DC, does it show a replication connection
from a DC in the child domain for the child domain container?
Are any DCs having problems replicating the Schema or Config container from
the child domain?
 
Hi James and thanks for your reply.

There were one DC in the root domain and I've recently installed a
second one (the one that can't become a GC). There is one DC in the
child domain.
A repadmin /showreps shows:
CN=Schema,CN=Configuration,DC=root
Default-First-Site-Name\ROOTSERVER1 via RPC
objectGuid: bdcac958-f424-4c76-a89f-50469783b32b
Last attempt @ 2004-08-19 20:52.37 was successful
Default-First-Site-Name\CHILDSERVER1 via RPC
objectGuid: 90866ce7-5c7b-4b67-bb51-51b82b726cff
Last attempt @ 2004-08-19 20:52.37 was successful

CN=Configuration,DC=root
Default-First-Site-Name\CHILDSERVER1 via RPC
objectGuid: 90866ce7-5c7b-4b67-bb51-51b82b726cff
Last attempt @ 2004-08-19 21:20.08 was successful
Default-First-Site-Name\ROOTSERVER1 via RPC
objectGuid: bdcac958-f424-4c76-a89f-50469783b32b
Last attempt @ 2004-08-19 21:25.08 was successful

DC=root
Default-First-Site-Name\ROOTSERVER1 via RPC
objectGuid: bdcac958-f424-4c76-a89f-50469783b32b
Last attempt @ 2004-08-19 21:25.58 was successful

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ========

CN=Schema,CN=Configuration,DC=root
Default-First-Site-Name\ROOTSERVER1 via RPC
objectGuid: bdcac958-f424-4c76-a89f-50469783b32b
Default-First-Site-Name\CHILDSERVER1 via RPC
objectGuid: 90866ce7-5c7b-4b67-bb51-51b82b726cff

CN=Configuration,DC=root
Default-First-Site-Name\ROOTSERVER1 via RPC
objectGuid: bdcac958-f424-4c76-a89f-50469783b32b
Default-First-Site-Name\CHILDSERVER1 via RPC
objectGuid: 90866ce7-5c7b-4b67-bb51-51b82b726cff

DC=root
Default-First-Site-Name\ROOTSERVER1 via RPC
objectGuid: bdcac958-f424-4c76-a89f-50469783b32b
Default-First-Site-Name\CHILDSERVER1 via RPC
objectGuid: 90866ce7-5c7b-4b67-bb51-51b82b726cff

The two existing DCs does not show any problems replicating or
similair. The childserver is registred as a GC in the Root domain
(DNS) but not in the child domain.
/Erik
 
A little more info:
the root domain is single-labeled. I've followed the MS arrticles
though for making dynamic updates etc. to work tith single-labeled
domains to work. The child domain is not single-labeled.

The child domain DC has no errors BUT 5781 Netlogon "Dynamic
registration or deregistration of one or more DNS records failed" and
so on. The child DC uses the root DC as primary DNS and itself as
secondary. It has no problems communicating with the DNS server (same
subnet).

It certainly feel DNS related to me, if anyone has ideas for me I'd be
very happy to hear them!
Thanks
 
Back
Top