login server

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

In a W2K server and W2K Pro environment with Active
Directory (all SP4), how does a client find a login
server? The reason I'm asking is occassionally we will
find clients in our New York office being logged on by
DC's in our Boston office even though the New York office
has global catalog servers which were up at the time. We
have even noticed Boston clients being logged on by Munich
DC's. This creates a problem since the GP scripts will
run from the logon server, which can take a long time
especially if the client is authenticating across the
ocean.

Anyone have any ideas? Thanks!

 

[Guest]

Archived from groups: microsoft.public.win2000.dns (More info?)

Thanks to Gil Kirkpatrick :
http://www.winnetmag.com/Articles/Print.cfm?ArticleID=37935

Also take a look at:
http://support.microsoft.com/default.aspx?kbid=306602

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
Microsoft MVP - Directory Services
www.readymaids.com - we know IT
www.akomolafe.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
"DanS" <anonymous@discussions.microsoft.com> wrote in message
news:591701c491c8$3d185cb0$a601280a@phx.gbl...
> In a W2K server and W2K Pro environment with Active
> Directory (all SP4), how does a client find a login
> server? The reason I'm asking is occassionally we will
> find clients in our New York office being logged on by
> DC's in our Boston office even though the New York office
> has global catalog servers which were up at the time. We
> have even noticed Boston clients being logged on by Munich
> DC's. This creates a problem since the GP scripts will
> run from the logon server, which can take a long time
> especially if the client is authenticating across the
> ocean.
>
> Anyone have any ideas? Thanks!