J
joecarter83
I had a problem last week where one of my three DC's wasn't
replicating following a forced demotion and subsequent repromotion of
a DC. Restarting all three DC's sorted things out but I noticed the
following warning in the Directory Service event log:
No nTDSConnection object exists for inbound replication from server
CN="NTDS Settings
DEL:15d02946-40e1-42c0-9e96-769bc179725e",CN="PHANTOM
DEL:8de98b91-f211-4d0d-85ad-49f70fca3a9f",CN=Servers,CN=Default-First-
Site-Name,CN=Sites,CN=Configuration,DC=corpusstudents,DC=local at
address
15d02946-40e1-42c0-9e96-769bc179725e._msdcs.mydomainname.local. The
partition DC=mydomainname,DC=local is no longer replicated from it.
Though I did do a metadata cleanup when I removed the DC that died, I
think that something somewhere is still referring to the deleted DC.
Any ideas?
replicating following a forced demotion and subsequent repromotion of
a DC. Restarting all three DC's sorted things out but I noticed the
following warning in the Directory Service event log:
No nTDSConnection object exists for inbound replication from server
CN="NTDS Settings
DEL:15d02946-40e1-42c0-9e96-769bc179725e",CN="PHANTOM
DEL:8de98b91-f211-4d0d-85ad-49f70fca3a9f",CN=Servers,CN=Default-First-
Site-Name,CN=Sites,CN=Configuration,DC=corpusstudents,DC=local at
address
15d02946-40e1-42c0-9e96-769bc179725e._msdcs.mydomainname.local. The
partition DC=mydomainname,DC=local is no longer replicated from it.
Though I did do a metadata cleanup when I removed the DC that died, I
think that something somewhere is still referring to the deleted DC.
Any ideas?