windows clients not using their local domain controller
Posted on 2013-02-02
I am having a problem with our new domain. We have a hub and spoke design with two hub sites. Half of all sites will replicate to one hub and the other half will goto the other.
DC1 and DC2 have a defined site link
DC1 and SITE1 have a defined site link
Site Link Transitivity has been disabled so I also created a site link bridge linking the two site links so that in the case that the domain controller at SITE1 is unavailable, and the domain controller at DC1 is unavailable, that it will still goto DC2. For some reason, most of the clients at SITE1 are going to DC2 when all of the Domain controllers are up and running.
To ensure that it isn't the site link bridge that I created, I removed the site link bridge between the two site links. The clients still use DC2 as their logon server.
DNS is setup right on the clients and the local site DC at SITE1 with their primary DNS serve being the SITE1 domain controller, and their secondary being DC1. Any idea why they continue to goto DC2?