I have 3 sites A, B, and C.  The subnets are configured correctly on each site.

Site A is headquarters.  Site B and C are branch offices, and IP traffic is not routable between them.  Each of them is only routable to Site A.

All sites are members of DEFAULTIPSITELINK which has a cost of 200.  I have also created two Site Links (A-B and A-C), each with a cost of 100.

KCC is incorrectly telling Site B to replicate from Site C, and isn't telling it to replicate to anywhere (seen when I right-click on the NTDS Settings object and go to Properties>Connections).  What's the problem here?

• Edited by J-LA Thursday, June 18, 2015 5:02 PM

Hi J-LA,

Thanks for your post.

The KCC creates replication connections based on your site topol

ogy, which you must define by creating sites and site links. In your scenario, you could delete manual bridgehead selections in each site. Runrepadmin /kcc on each DC to automatically regenerate a new topology. After running the command, then run repadmin /showrepl to  have a check.

In addition, you could check the error message in the Event log.

Best Regards,

Mary Dong

• Proposed as answer by Mary DongMicrosoft contingent staff, Moderator Thursday, June 25, 2015 2:53 AM
• Marked as answer by Mary DongMicrosoft contingent staff, Moderator Tuesday, June 30, 2015 1:28 AM
• Unmarked as answer by J-LA 13 hours 40 minutes ago
• Unproposed as answer by J-LA 13 hours 40 minutes ago

Thanks!  This does not solve the issue, though.  KCC just regenerates the same incorrect topology.  The File Replication Service log is not much help because it is filled with errors because it's trying to replicate to a DC that it cannot even ping.

Hi J-LA,

Could you please show more error message about replication failure in the log? And Is the problem only between site B and site C? Please also use Dcdiag.exe to verify domain controller health.

Best Regards,

Mary Dong

Hello,

Can you provide the output of following command and possible Error screenshot if you can share here.

Please upload the output of this command to common share location onedrive etc.

Repadmin /Replsum /errorsonly

repadmin /showrepl*

dcdiag /v /c /d /e /s:Contoso.com

repadmin /kcc on each DC

Also

The KCC is will automatically creates the partnerships. The KCC doesn't know if you have a physical mesh or not. If BASL is enabled, which it is by default, it will create partnerships all over the place between DCS in any sites. If the physical network is not meshed, then the KCC will be partnering DCS that can't physically communicate to each other.