The RODCs are not included in a response to a DFS referral request from a computer that is running Windows Server 2003 SP2

In a domain that has both some Windows Server 2003-based domain controllers and some Windows Server 2008-based read-only domain controllers (RODC), the response to a Distributed File System (DFS) referral request might not include RODCs. Therefore, the performance of DFS-related operations is poor.


For example, the performance may be slow when you try to log on to a computer, when you try to run a Group Policy object (GPO) application, when you try to access a shared file, or when you try to access a shared printer.


If you run the dfsutil /pktinfo command on a domain controller that is running Windows Server 2003, the command does not include any information about any RODCs that are running Windows Server 2008.

This issue occurs because the DFS service that is in Windows Server 2003 uses an incorrect parameter when the service queries for some DFS referral information.

When the incorrect parameter is used, the returned DFS referral does not contain RODC information. Therefore, some unsuitable domain controllers are returned to handle the DFS-related operations when a Windows Server 2003-based domain controller handles a DFS referral querying request. Additionally, the unsuitable domain controllers cause the performance issue that is mentioned in the "Symptoms" section.

Hotfix information

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 the problem described in this article. 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 apply this hotfix, you must be running Windows Server 2003 Service Pack 2 (SP2).

For more information about how to obtain a Windows Server 2003 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

Restart requirement

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

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The English (United States) version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.

Windows Server 2003 file information notes

• In addition to the files that are listed in these tables, this hotfix also installs an associated security catalog file (KBnumber.cat) that is signed with a Microsoft digital signature.

For all supported x86-based versions of Windows Server 2003

For all supported x64-based versions of Windows Server 2003

For all supported IA-64-based versions of Windows Server 2003

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

For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information