bbcac
asked on
windows clients not using their local domain controller
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?
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?
Hi,
following the previous answer :
Does each DC be in the same subnet it's client ? (some company put their DC in a separate subnet) ?
btw, i would rather restart the computer after to monitor the change of DC, because, by doing only a gpupdate / gpresult you're generally still linked to the same DC (and if it's not the good one...)
cheers
following the previous answer :
Does each DC be in the same subnet it's client ? (some company put their DC in a separate subnet) ?
btw, i would rather restart the computer after to monitor the change of DC, because, by doing only a gpupdate / gpresult you're generally still linked to the same DC (and if it's not the good one...)
cheers
Hi bbcac,
step1: Execute the command set L in command prompt then you'll get the logon server name
step2: Then query the site name,
nltest /dsgetsite /s:Logon server name to be given here
Then open dssite.msc in run and expand sites in the console navigate to the logon server site name and right click on the site name ->Properties, check in General tab the subnet range associated with the site.
Check whether the client IP ADDRESS falls in the subnet range associated with the site in which the logon server exist.
Also, some times if we assign the same subnet range in to two sites will result in this issue.
Conclusion:
Either the IPADDRESS of client machine is not associated to any of the site or it might have assigned to more than one site. Hence the issue.
Kindly perform the above check and revert, so that we can dig further..,
Expecting your reply..,
step1: Execute the command set L in command prompt then you'll get the logon server name
step2: Then query the site name,
nltest /dsgetsite /s:Logon server name to be given here
Then open dssite.msc in run and expand sites in the console navigate to the logon server site name and right click on the site name ->Properties, check in General tab the subnet range associated with the site.
Check whether the client IP ADDRESS falls in the subnet range associated with the site in which the logon server exist.
Also, some times if we assign the same subnet range in to two sites will result in this issue.
Conclusion:
Either the IPADDRESS of client machine is not associated to any of the site or it might have assigned to more than one site. Hence the issue.
Kindly perform the above check and revert, so that we can dig further..,
Expecting your reply..,
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
This was a mistake on my part... I had the site configed wrong... everything is fine now
Run gpupdate /force to refresh group policies
Run gpresult /r to check the login server