PC logs into Domain Controller in wrong site


i have pc logging in our higher headquarters taking insanely long logon times. under assumption pc logged in dc associated site in.   subnets our site are correct in active directory sites , services shouldn't pc pick our 2 dc's first logon?

what can i do ensure pc never logs on incorrect dc?

howdie!
 
on 04.10.2010 23:14, defense backups wrote:
> have pc logging in our higher headquarters taking
> insanely long logon times. under assumption pc
> logged in dc associated site in. the
> subnets our site correct in active directory sites , services
> shouldn't pc pick our 2 dc's first logon?
 
can perform following commands client (you
need install support tools this):
 
nltest /dsgetdc:<domain>
 
and within nslookup:
set q=srv
_ldap._tcp.<site name>._sites.dc._msdcs.<domain name>
 
what domain controllers returned? if it's both _wrong_ dc
different site, there's trouble dns , you'll have check
in dns if there srv records of other sites registered.
 
that can happen when site-local dcs aren't available or there no
site-local dcs , got introduced later. ad has site-autocoverage
mechanism covers dc-less sites dcs other sites.
 
so you'll want check dns -- ,
aging&scavenging these entries cleaned automatically in future.
 
cheers,
florian
 

microsoft mvp - group policy (http://www.frickelsoft.net/blog)


Windows Server  >  Directory Services



Comments

Popular posts from this blog

server manager error: ADAM.events.xml could not be enumerated.

Cannot access Anywhere Access using domain name?

WMI Failure: Unable to update Local Resource Group