I think your problem is that you probably upgraded the DC at that site last and, before the upgrade, your XP and 2K clients had discovered the new 2K3 DCs at the remote site. Once XP and 2K clients discover and authenticate against a 2K or 2K3 DC, they usually don't go back. This may be what you are seeing now. Have you tried disjoining and rejoining one or two of those clients? This should help them rediscover their local DC. Sincerely,
D�j� Ak�m�l�f�, MCSE+M MCSA+M 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 ________________________________ From: [EMAIL PROTECTED] on behalf of Jacob Walker Sent: Thu 1/20/2005 5:27 AM To: [email protected] Subject: [ActiveDir] Clients Not Authenticating with Site DC We are at the end of our migration from NT to AD 2003 and completing the PC moves. However, we are now receiving many reports that some PC's are authenticating against remote DC's. While many PC's in a location will respect the site configuration and authenticate against the local DC, some PC's are authenticating against DC's outside of the site. These are 2000 and XP machines, so we thought they should understand Active Directory sites. We do not have any network traces from any of these machines at this time, but we were wondering if they might be using WINS rather than DNS to locate a DC. But, why would this be happening? These newer OS clients should look for a DC using DNS, shouldn't they? We checked DNS, and it is correct. Any ideas? List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/ List info : http://www.activedir.org/List.aspx List FAQ : http://www.activedir.org/ListFAQ.aspx List archive: http://www.mail-archive.com/activedir%40mail.activedir.org/
