selection logonserver with wrong subnet config

[Willem Kasdorp]

I have an AD network with a lot of sites. It turns out
that not all sites have properly assigned subnets. There
are a number of clients that fall uitside the subnets
defined in AD.

The question is, which DC will such a client select for
logon and why?

 

[Corey Hynes]

Assuming that all sites contain DC's, the client will select a DC that is in
it's site based on how its IP address maps to the subnets and sites you have
created

 

[Willem Kasdorp]

That's my point exactly. There are a number of clients
that don't have a corresponding subnet in AD. They
_cannot_ match themselves to a site. So, which DC do they
pick?

 

[Cary Shultz]

-----Original Message-----
I have an AD network with a lot of sites. It turns out
that not all sites have properly assigned subnets. There
are a number of clients that fall uitside the subnets
defined in AD.

The question is, which DC will such a client select for
logon and why?
.

Willem,

There is an outstanding MS KB Article that explains how a
system locates the DC / GC for logon. A good chunck of it
revolves around the SRV records ( DNS - you *KNEW* that
DNS had to have something to do with this! ).

Anyway, there is also a really good article which could
help you in your situation. It is very possible to have
clients in one site - with a DC in that site - yet
authenticate to a DC in another site. That is because of
the so-called "generic" record. There is a registry hack
to resolve this.

Please take a look at the following:

http://support.microsoft.com/default.aspx?scid=kb;en-
us;306602

HTH,

Cary