First double check the sites setup and make sure each DC is in the right subnets and that the XP clients in question are in the same site. If that is ok time to check connectivity and name resolution to the local DC from the 'bad' XP machine. Has to be one or the other.
And the XP machines have been restarted since the sites were created? From: Heaton, Joseph@DFG [mailto:jhea...@dfg.ca.gov] Sent: Monday, August 20, 2012 3:15 PM To: NT System Admin Issues Subject: Strange login issue We're setting up a new domain. When a user here in the central HQ area logs in, the DC that they use for login is random. Should be a DC here locally, but most of the time it is not. They'll end up using a DC from a field office site, which means the request goes over slow links to get there. I'm not the architect, but I know that the person that set up the domain used Sites and site links for replication, etc. Using this had no effect, and neither did removing them. Anyone have advice on how to make clients use the local DC if it's available, before going to another site for login? ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com<mailto:listmana...@lyris.sunbeltsoftware.com> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
