Share via

Active Directory local site link topology causing client machines to fetch group policies from cross-continent domain controllers

Patel Vihaan 0 Reputation points
2026-06-11T03:31:54.47+00:00

Hi network infra team,

our office workstations located in London are experiencing heavy delays pulling policy modifications. Looking at the local gpresult logs, the client nodes are actively routing to a Domain Controller located in our Tokyo data center across a high-latency satellite WAN link instead of the local London node.

Thanks

PV

Windows for business | Windows 365 Enterprise
0 comments

1 answer

Sort by: Most helpful
Most helpful Newest Oldest
  1. Marcin Policht 92,045 Reputation points MVP Volunteer Moderator
    2026-06-11T03:41:24.27+00:00

    First, verify the client’s detected site using nltest /dsgetsite and confirm the workstation IP subnet exists under the correct London site in Active Directory Sites and Services. Ensure the London subnet objects are properly defined and associated with the intended site. Missing or overlapping subnet definitions commonly cause clients to authenticate against distant DCs.

    Next, validate DC Locator behavior using nltest /dsgetdc:<domain> on affected systems. Flush cached locator information with nltest /dsgetdc:<domain> /force, or by restarting the Netlogon service.

    Check the DNS configuration tied to the AD site coverage and ensure that the London AD site does not include DNS records of Tokyo domain controllers.

    Keep in mind that majority of AD problems tie to misconfigured DNS.

    If the above response helps answer your question, remember to "Accept Answer" so that others in the community facing similar issues can easily find the solution. Your contribution is highly appreciated.

    hth

    Marcin

    Was this answer helpful?

    0 comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.