The domain controller locator cannot find an appropriate domain controller on a computer that is running Windows XP or Windows Server 2003

On a computer that is running Windows XP or Windows Server 2003, the domain controller locator cannot find an appropriate domain controller.

For example, the computer may select out-of-site domain controllers to service authentication, LDAP, and other domain controller-specific requests even when in-site domain controllers exist. Or, the computer may send authentication, LDAP, and other domain controller-specific requests to several domain controllers instead of evenly balancing the load across the pool of available domain controllers.

The domain controller locator in Windows XP and in Windows Server 2003 caches the name of a single domain controller. This client cache is not updated until the targeted domain controller stops responding to locator requests or until the client is restarted. Therefore, the client continues to send domain controller requests to the cached domain controller.

Note The cached domain controller is selected from the pool of available domain controllers when the DCLocator cache is first populated.

In this scenario, the client cannot update the cached domain controller item even if additional domain controllers or more suitable domain controllers become available.

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
After you install the hotfix, the DNS locator client in Windows XP and in Windows Server 2003 updates its domain controller cache after a default interval. The DNS locator client tries to rediscover a suitable domain controller. The life cycle of a cached entry is controlled by the value of the ForceRediscoveryInterval registry entry.

After you install the hotfix, you have to create and then modify the ForceRediscoveryInterval registry entry. To do this, follow these steps:

1. Click Start, click Run, type Regedit, and then click OK.
2. Locate and then click the following registry subkey:
   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
3. On the Edit menu, point to New, and then click DWORD Value.
4. Type ForceRediscoveryInterval, and then press ENTER.
5. Right-click ForceRediscoveryInterval, and then click Modify.
6. In the Edit DWORD Value dialog box, under Base, click Decimal.
7. In the Value data box, type the expected value, and then click OK.
   Note The ForceRediscoveryInterval registry entry specifies the number of seconds that the DsGetDcName�function waits before it tries to rediscover the domain controller name. The value of the ForceRediscoveryInterval registry entry must be between�3600 and 4294967295. The default value is 43200 seconds (12 hours). If the value of the ForceRediscoveryInterval registry entry is set to 3600, the client�performs rediscovery every 60 minutes. If the value is set to 4294967295, the cache never expires, and the cached domain controller continues to be used.
8. Exit Registry Editor.

Note�The Force Rediscovery Interval Group Policy setting can be used to configure this registry entry in Windows XP, in Windows Server 2003, or in Windows Vista. This�setting is located under Computer Configuration\Policies\Administrative Templates\System\Netlogon\DC Locator DNS Records.

Hotfix information

Windows Server 2003

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this hotfix, you must have Microsoft Windows Server 2003 Service Pack 1 (SP1) or Microsoft Windows Server 2003 Service Pack 2 (SP2) installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.Windows Server 2003 with SP1, x86-based versionsWindows Server 2003 with SP2, x86-based versionsWindows Server 2003, x64-based versionsWindows Server 2003 with SP2, x64-based versionsWindows Server 2003 with SP1, Itanium-based versions Windows Server 2003 with SP1, Itanium-based versions

Windows XP

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To install this hotfix, you must have Microsoft Windows XP Service Pack 1 or Windows XP Service Pack 2 installed on the computer.

Restart requirement

You have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Windows XP with SP2, x86 Edition Windows XP Professional with SP1, x64 Edition Windows XP Professional x64 Edition with SP2, x64 version

To work around this problem, use one of the following methods.

Method 1

Some client computers periodically retrieve the domain controller name by using the DS_FORCE_REDISCOVERY flag to call the DsGetDcName function. Determine which client computers do this. Then, deploy a script to these client computers.

Method 2

Update the cache on each client. To do this, run the following command at a command prompt:

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about the DsGetDcName function and about domain controller stickiness, visit the following Web site: