RE: Authenticating to wrong DC

From: David V (DavidV_at_discussions.microsoft.com)
Date: 11/15/04

  • Next message: Steven L Umbach: "Re: Authenticating to wrong DC" 
    Date: Mon, 15 Nov 2004 09:25:03 -0800

    Logon requests will go to the local domain controller if you have defined
    what is local by setting up sites in AD Sites and Services, and defined all
    the subnets that belong to each site; if not, then AD does not know what is
    local and what is not. Once you have done that, logon requests will only be
    sent to the remote site if the local DC is unavailable.

    "RichardB" wrote:

    > Hello
    >
    > I have a seperate Domain Controller 600 miles away which most of our Users
    > are authenticating to. How do you set it to use the GC here? I thought
    > that by default that AD would look at the local Domain controller first.
    >
    >
    > Thanks in advance
    > RichardB

  • Next message: Steven L Umbach: "Re: Authenticating to wrong DC"

    Relevant Pages

    • Re: Login Authentication
      ... setup to pull from the local domain controller then secondarily to the ... I would also want to know that all of my clients are authenticating ... is getting first the local DNS Server information and then the DNS ...
      (microsoft.public.windows.server.active_directory)
    • Re: Login Authentication
      ... setup to pull from the local domain controller then secondarily to the ... I would also want to know that all of my clients are authenticating ... is getting first the local DNS Server information and then the DNS Server ...
      (microsoft.public.windows.server.active_directory)
    • Re: Sites and Services
      ... Clients that are AD aware should use a local domain controller but will not ... > restrict login to the DC at the site. ...
      (microsoft.public.windows.server.active_directory)
    • RE: Outdated Active Directory Objects
      ... REPADMIN, not REPLADMIN. ... > object from the following source domain controller. ... > present on the local domain controller because it may have been deleted ...
      (microsoft.public.windows.server.active_directory)
    • Outdated Active Directory Objects
      ... The local domain controller has attempted to replicate the following ... object from the following source domain controller. ... Replication will not continue with the source domain controller until ...
      (microsoft.public.windows.server.active_directory)