- Sites: Santa Clara (data center), San Francisco (office), Seattle (office), Boston (office)
- Two Domain Controllers at each site.
- All sites are able to talk to San Francisco but not each other.
- No other services are shared/provided to the sites.
- Only AD/LDAP authentication
- IP subnets are assigned in AD Sites and Services
- Default-First-Site is used in San Francisco
When a new DC comes up it creates an Connection to a Site/DC that it cannot actually talk to. For example: A new DC in San Jose, lets call it SJC-DC02 has a Connection to a DC in Seattle, SEA-01 BUT it cannot actually connect to SEA-01. It can only (by design) talk to SFO-DC01 and SFO-DC02. I am having to manually create the connections from SJC-DC02 to SFO-DC01 and SFO-DC02.
How do I get rid of these "automatically generated" Connections once and for all? (They come back if you just simply delete them)
Remind me, should all Connections be bidirectional? Example: SJC-DC02 to SFO-DC01 and SFO-DC02 as well as SFO-DC01 to SJC-DC02 and SFO-DC02 to SJC-DC02