Re: Multisite Authentication
- From: "Herb Martin" <news@xxxxxxxxxxxxxx>
- Date: Wed, 21 Mar 2007 12:17:49 -0500
"Laura E. Hunter [MVP]" <laurahcomputing.nospam@xxxxxxxxx> wrote in message
news:%23gj6Am9aHHA.4552@xxxxxxxxxxxxxxxxxxxxxxx
Unfortunately what you're seeing is the expected behaviour in 2K3. If a
client cannot authenticate against any DCs in its local site, it will then
choose -any- available DC.
This behaviour may improve somewhat in the next release of Windows Server,
but Longhorn is still in beta so no features are set in stone where that's
concerned.
If you want to exert more granular control over which DCs can "cover"
various sites, you can modify auto site coverage in DNS using Group Policy
or the Windows Registry. You'll find a detailed explanation of this
setting in the 2003 Branch Office Guide, available here:
http://www.microsoft.com/downloads/details.aspx?FamilyId=9353A4F6-A8A8-40BB-9FA7-3A95C9540112&displaylang=en
In addition to Laura's offered link this one can help also:
How Domain Controllers Are Located in Windows
http://support.microsoft.com/kb/247811
--
Herb Martin, MCSE, MVP
http://www.LearnQuick.Com
(phone on web site)
.
- References:
- Multisite Authentication
- From: Zeno
- Re: Multisite Authentication
- From: Laura E. Hunter [MVP]
- Multisite Authentication
- Prev by Date: Re: Adding Win2003R2 DC to existing Domain w/ Win2003 DC
- Next by Date: Password change in GPO
- Previous by thread: Re: Multisite Authentication
- Next by thread: reading UnicodePWD attribute
- Index(es):
Relevant Pages
|