• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 579
  • Last Modified:

DC Locator Setting in GP / Local Authentication

I have noticed that my clients are authenticating against domain controllers that are not local to them.  I have checked the site and services, the settings are correct.  I have been doing some research and located the option to setup the DC Locator Server http://searchwinit.techtarget.com/tip/0,289483,sid1_gci1283750,00.html ) .  If this option is configured, will it force the computers to authenticate to the subnets that are on that network vs. ones that are not?  Also, if forced, if those controllers are down will it authenticate to the local computer or search for remotes listed in DNS?
0
securitythreat
Asked:
securitythreat
1 Solution
 
KCTSCommented:
If you want clients to authenticate with particular domain controllers in preference to others then you need to configure Active Directory Sites properly.

You should start by defining your subnets in Active Directory Sites and services, then you need to create sites and associate one or more subnets with each site. Once that is done then clients will attempt to use a DC on their own site for authentication.

Of course is you want to minimise traffic across the subnets you should also place a DNS server in each site (easy to do if you use AD integrated DNS), and point clients to that DNS server as their preferred DNS server. Also the DC/DNS server should be made a global catalg server as well to provide GC lookups locally as well. If you are uding DHCP you could also look at localising that as well.

0
 
securitythreatAuthor Commented:
I have all this in place.  However, this is still an issue.
0

Featured Post

Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now