Actually, if it were hard coded, it would be in the SiteName entry. The DynamicSiteName entry is for the dynamically discovered site as discovered by netlogon...check these links out: DynamicSiteName http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en-us/regentry/55957.asp SiteName http://www.microsoft.com/resources/documentation/Windows/2000/server/reskit/en-us/Default.asp?url=/resources/documentation/Windows/2000/server/reskit/en-us/regentry/55957.asp Rob
________________________________ From: [EMAIL PROTECTED] on behalf of Jeff Smith Sent: Mon 1/24/2005 1:15 PM To: [email protected] Subject: Re: [ActiveDir] Clients Not Authenticating with Site DC Usually the problem is missing SRV Records or Sites and Services is misconfigured. Check the following registry location and see if that site is hard coded. You can write a script to reset this if needed. HKLM\SYSTEM\CCS\SERVICES\NETLOGON\PARAMETERS\DYNAMICSITENAME Also, check the NETLOGON.LOG on both the Client and the Server. You should be able to see what is going on there. On Thu, 20 Jan 2005 11:20:18 -0800, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > 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/ > 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/
<<winmail.dat>>
