Hi guys, we have an issue concerning domain controllers that dont seem to authenticate clients that are in its site.
Domain Controller: AUTESTDC (This is listed as a server in the Site HO in AD Sites and Services)
CLIENTPC has an IP address that is part of a subnet that this Site should service, and as listed in AD Sites and Services.
So, the following is what is happening on a regular basis.
CLIENTPC boots up, user logs on.
Instead of AUTESTDC being the %logonserver%, when you issue this command, a domain controller OUTSIDE its own SITE is the logonserver.
What we need to establish is the following:
1.Why is the client continually getting authenticated OUTSIDE its own site?
2.How can we determine the problem with the local DC (if there is a problem) to see WHY it wont be the logonserver.
3.How do we get the local DC AUTESTDC to be the local logonserver.
4.In our AD Sites and Services, the setup looks correct, so we are at a loss to understand why clients are not being authenticated locally.
5.Any test tools that we can use to fix this problem?
Any help on this greatly appreciated.