Select the product you need help with

The DFS root server cannot do the site costing correctly and local DFS client computers are referred to remote DFS share location after you install Windows Server 2003 Service Pack 1 on the domain controller

Article ID: 917417 - View products that this article applies to.

SYMPTOMS

Consider the following scenario. You install Microsoft Windows Server 2003 Service Pack 1 (SP1) on a Windows Server 2003-based domain controller. However, the Windows Server 2003-based Distributed File System (DFS) root server is not running Windows Server 2003 SP1. In this scenario, the DFS root server cannot do the site costing correctly. Then, local DFS client computers are referred to a remote DFS share location.

Note The DFS share location provides a local share for software installation.

Additionally, wide area network (WAN) traffic increases, and the access time for DFS client computers becomes slow. This problem occurs when many client computers exist in the domain.

Back to the top | Give Feedback

CAUSE

This problem occurs because the change to remote procedure call (RPC) security in Windows Server 2003 SP1 prevents the use of NULL connections. This change affects the DFS service on the DFS root server because the DFS service uses the IP address to make the connection to its local domain controller.

Back to the top | Give Feedback

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Windows Server 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

889100

(http://support.microsoft.com/kb/889100/ )

How to obtain the latest service pack for Windows Server 2003

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 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:

http://support.microsoft.com/contactus/?ws=support

(http://support.microsoft.com/contactus/?ws=support)

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

No prerequisites are required.

Restart requirement

You do not 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.