How does Windows XP choose the most optimal domain controller?



I have been reading http://support.microsoft.com/default.aspx/kb/314861.

There is a sentence that says "If the client is communicating with a domain controller that is not in the closest (most optimal) site, the domain controller returns the name of the client's site."

I am looking for a technical explanation of that process.
--
John

.



Relevant Pages

  • Re: Client performance problem windows 2003 server...
    ... In addition, if you have the same problem with non-English client, please ... >Subject: Re: Client performance problem windows 2003 server... ... >>>Deploying Active Directory for Branch Office Environments ... >>>results from not having a domain controller in a particular site. ...
    (microsoft.public.windows.server.networking)
  • Re: Client performance problem windows 2003 server...
    ... there and install an english client to be doing the errorsearching on. ... to the Windows 2000 server in site A that is a English ... >>be a DNS replication issue. ... >>results from not having a domain controller in a particular site. ...
    (microsoft.public.windows.server.networking)
  • Re: AD Site Topology
    ... authenticating with a domain controller in a different physical ... to a GC outside of it's physical location resulting in Outlook ... local infrastrcuture i.e. DC's/F&P but not exchange. ... client side is a good point though although I thought MS improved the ...
    (microsoft.public.win2000.active_directory)
  • Re: DNS-AD integration
    ... On the client open a command prompt and type "set". ... I have also set up AD-integrated DNS in both of these servers. ... use the first domain controller ip address. ... It will use DNS Round Robin to resolve it. ...
    (microsoft.public.windows.server.dns)
  • RE: How does Windows XP choose the most optimal domain controller?
    ... Finding a Domain Controller in the Closest Site: ... A client computer stores its own site information in the registry, ... If the second query is successful, ...
    (microsoft.public.windowsxp.general)

Loading