Automatically Generated NTDS connection removal


  • After changing AD S&S to a Hub/Spoke design (site links are not bridged), then making modification to firewall to reflect same architecture, old 'automatically generated' connections remain and seem to be causeing errors to be logged in event viewer.

    Just doing a 'check replication topology' did not fix the problem.

    Setting the firewalls to allow traffic from one of these remote sites to the other remote site seemed to fix the problem.  It corrected itself by deleting the automatically created connection that existed when the site links were bridged.  Event logs also went far.

    It was like RemoteServerA had to ask RemoteServerB if the link could be deleted.

    Why would these 'auto gen' connecitons not also be removed automatically when there is no physical connection enabled on the FW?

    Friday, June 03, 2011 6:14 PM


  • Just delete them.  No big deal.

    Paul Bergson
    MVP - Directory Services
    MCITP: Enterprise Administrator
    MCTS, MCT, MCSE, MCSA, Security+, BS CSci
    2008, Vista, 2003, 2000 (Early Achiever), NT4 Twitter @pbbergs

    Please no e-mails, any questions should be posted in the NewsGroup. This posting is provided "AS IS" with no warranties, and confers no rights.

    • Marked as answer by MichAda Friday, June 03, 2011 7:55 PM
    Friday, June 03, 2011 7:54 PM

All replies