Hi guys (sorry for the long post)
This one has me beat.
We have recently moved offices, and now the head office domain controller MBHDMC01 runs both head office and a retail shop. PReviously shop had a server called MBCDMC01, which was switched off.
It is now about 2 months later, and the MBCDMC01 (ex shop server) has been recommisioned into a different site. I am copping heaps of error messages in the event log as follows:
-----------------
1566 - All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable.
1311 - The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
Directory partition:
CN=Configuration,DC=XXXX,DC=local
There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.
1925 - The attempt to establish a replication link for the following writable directory partition failed.
Directory partition:
CN=Schema,CN=Configuration,DC=XXXX,DC=local
Source domain controller:
CN=NTDS Settings,CN=MBHDMC01,CN=Servers,CN=MaryboroughHO,CN=Sites,CN=Configuration,DC=XXXX,DC=local
Source domain controller address:
26ace516-1801-4ce5-9aa0-c4bdb6111a3c._msdcs.XXXX.local
Intersite transport (if any):
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=XXXX,DC=local
This domain controller will be unable to replicate with the source domain controller until this problem is corrected.
User Action
Verify if the source domain controller is accessible or network connectivity is available.
Additional Data
Error value:
2148074274 The target principal name is incorrect.
------------------
Since there is only a handful of staff at that site, I have attempted to get the server synchronised again by doing a DCPROMO and demoting the server, and re promoting, but this fails before the demotion.
Has anyone any ideas how to fix this? I have trawled through numerous microsoft pages and forums, and am still stuck.
Would it be recommended just to clean the server off the active directory for the domain, and start afresh?
cheers,
Brett
This one has me beat.
We have recently moved offices, and now the head office domain controller MBHDMC01 runs both head office and a retail shop. PReviously shop had a server called MBCDMC01, which was switched off.
It is now about 2 months later, and the MBCDMC01 (ex shop server) has been recommisioned into a different site. I am copping heaps of error messages in the event log as follows:
-----------------
1566 - All domain controllers in the following site that can replicate the directory partition over this transport are currently unavailable.
1311 - The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
Directory partition:
CN=Configuration,DC=XXXX,DC=local
There is insufficient site connectivity information in Active Directory Sites and Services for the KCC to create a spanning tree replication topology. Or, one or more domain controllers with this directory partition are unable to replicate the directory partition information. This is probably due to inaccessible domain controllers.
1925 - The attempt to establish a replication link for the following writable directory partition failed.
Directory partition:
CN=Schema,CN=Configuration,DC=XXXX,DC=local
Source domain controller:
CN=NTDS Settings,CN=MBHDMC01,CN=Servers,CN=MaryboroughHO,CN=Sites,CN=Configuration,DC=XXXX,DC=local
Source domain controller address:
26ace516-1801-4ce5-9aa0-c4bdb6111a3c._msdcs.XXXX.local
Intersite transport (if any):
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=XXXX,DC=local
This domain controller will be unable to replicate with the source domain controller until this problem is corrected.
User Action
Verify if the source domain controller is accessible or network connectivity is available.
Additional Data
Error value:
2148074274 The target principal name is incorrect.
------------------
Since there is only a handful of staff at that site, I have attempted to get the server synchronised again by doing a DCPROMO and demoting the server, and re promoting, but this fails before the demotion.
Has anyone any ideas how to fix this? I have trawled through numerous microsoft pages and forums, and am still stuck.
Would it be recommended just to clean the server off the active directory for the domain, and start afresh?
cheers,
Brett