Force to use Closest DC at login?

[Bob Reasoner]

We have migrated all of our PCs to a child domain of a
larger government forest.

We have created the sites setup with the correct IP
subnets, but the Client PCs seem to be resolving round
robin to whichever DC is next which might be 2 T1 hops
away.

Each of the local sites has a DC member of the site and
are running Caching only DNS servers which point back to
the Active Directory integrated zone on our primary GC for
the child domain. The forwards and the Reverse lookups
are all maintained on that Child GC/DNS server which
forwards as needed back up to the forest level.

All clients point their primary DNS to the local caching
DNS servers, and their secondary to the child GC/DNS. The
site DCs all point their primary DNS to the child GC/DNS
and their secondary to the forest DNS.

We have several activities that occur from login scripts
and they of course run much slower when coming across the
T1. Our child site clients notice the reverse happening
in that some of them go to a remote site DC to login even
though I have two DCs in the child root site.

Any thoughts? We are also noticing that intermittently
clients are not running login scripts at all, although, I
don't know if the two problems are directly related or not.

Thanks in advance!

 

[Bob Reasoner]

Thanks, I will check that out. Would you know what kinds
of issues I should check to troubleshoot the intermittent
login scripts issue? We used ADMT 2.0 to migrate from an
NT4 domain into this child AD domain. Our login scripts
are batch files, and intermittently we notice that they
are not running login scripts. There doesn't seem to be
any specific users or times of day. The user will login
not see a command prompt login script and not have his/her
mapped drives. They will log off and back on and the
script will run fine.

Thanks again!

Bob Reasoner