Microsoft KB Archive/944505

= DFS clients may access the DFS root server in the remote site even though the DFS root server in the local site is available in a Windows Server 2003-based domain =

Article ID: 944505

Article Last Modified on 1/4/2008

-

APPLIES TO


 * Microsoft Windows Server 2003, Datacenter Edition (32-bit x86)
 * Microsoft Windows Server 2003, Datacenter Edition for Itanium-Based Systems
 * Microsoft Windows Server 2003, Datacenter x64 Edition
 * Microsoft Windows Server 2003, Enterprise x64 Edition
 * Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
 * Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
 * Microsoft Windows Server 2003, Standard x64 Edition
 * Microsoft Windows Server 2003, Standard Edition (32-bit x86)

-



SYMPTOMS
Consider the following scenario:
 * In a Windows Server 2003-based domain, you configure the Distributed File System (DFS) together with multiple DFS root servers. Some servers are located in the local site, and the other servers are located in a remote site.
 * Users in the local site use DFS to access shares.

In this scenario, the active DFS target may switch to a server in the remote site even if the DFS root server in the local site is available. This problem may cause the users in the domain to experience a slow response when they access a DFS share.



Hotfix information
A supported hotfix is now 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 Windows Server 2003 service pack that contains this hotfix.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

Prerequisites
To apply this hotfix, you must have Windows Server 2003 Service Pack 1 (SP1) or 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 previously released hotfixes.

Registry information
To use this hotfix, you do not have to make any changes to the registry.

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 SP2, x64-based versions


STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



Network trace information
When this problem occurs, a network trace that resembles the following trace is generated: SMB C transact2 Query path info, File =    SMB R transact2 - NT error, System, Error, Code = (58) STATUS_OBJECT_PATH_NOT_FOUND  

