On Fri, Oct 2, 2009 at 12:35 PM, Free, Bob <[email protected]> wrote:
> Hence the "if at all possible" in my query :-)
Here's the problem I am getting now, tho ...
The parent DC seized all the roles, and seems OK about it ...
Server "admnrdc004" knows about 5 roles
Schema - CN=NTDS Settings,CN=ADMNRDC004
Domain - CN=NTDS Settings,CN=ADMNRDC004
PDC - CN=NTDS Settings,CN=ADMNRDC004
RID - CN=NTDS Settings,CN=ADMNRDC004
Infrastructure - CN=NTDS Settings,CN=ADMNRDC004
The child is *not* happy, in the least ....
Server "ADMNWDC003" knows about 5 roles
Schema - CN=NTDS Settings,CN=ADMNRDC001
Domain - CN=NTDS Settings,CN=ADMNRDC001
PDC - CN=NTDS Settings,CN=ADMNWDC003
RID - CN=NTDS Settings,CN=ADMNWDC003
Infrastructure - CN=NTDS Settings,CN=ADMNWDC003
So it still seems to want to talk to RDC001 in the parent domain,
which doesn't exist anymore. Seems like RDC004 didn't go and tell
WDC003 that it was seizing all roles.
How to resolve this? I thought to initiate a replicate from RDC004,
but it doesn't know that WDC003 is an inbound neighbor, It does know
that it is an outbound neighbor, tho ...
==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============
WilsonPark\ADMNWDC003 via RPC
objectGuid: 34a3f66b-148d-4336-bc47-9cf94b7edbff
The child shows this, for "repadmin /showreps" (edited)
WilsonPark\ADMNRDC004 via RPC
objectGuid: fce67ece-48f8-4ed5-8165-92887f332c23
Last attempt @ 2009-10-02 12:49.03 failed, result 1908:
Could not find the domain controller for this domain.
Last success @ 2009-09-29 15:42.46.
99 consecutive failure(s).
Now I am really confused .... can you shed any light?
Thanks
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
