Console and Terminal Services Access to Dfs Share Ignores Site Preference (274411)
The information in this article applies to:
- Microsoft Windows 2000 Server SP1
- Microsoft Windows 2000 Advanced Server SP1
- Microsoft Windows 2000 Professional SP1
This article was previously published under Q274411 SYMPTOMS
When you are connected to the console, or in a Terminal Services session, you may be referred to a distributed file system (Dfs) replicant even though the local Dfs share is a closer resource and a better choice.
CAUSE
The Microsoft Windows NT Dfs enables Dfs-aware clients to access network resources in a single namespace with improved fault tolerance and load balancing.
Windows 2000-based clients that connect to a Windows 2000-based domain Dfs connection receive a site-ordered list of referrals with servers in the same site as the client displayed at the top of the referral list. Site-aware clients favor connections to servers in the same Active Directory site.
Dfs site preference to site-aware clients is ignored if Dfs shares have links that refer to servers that are located in more than one Active Directory site. This situation can occur under the following conditions:
- You are accessing the Dfs root or link from the console of a Dfs server.
- You are accessing the Dfs root or link over a Terminal Services session to a Terminal Services-enabled Dfs server. (This situation is a variation of the preceding condition.)
The access process to a Dfs share from the console of a Dfs server does not use the expected Active Directory site name of the Dfs client. Specifically, Dfs uses the Internet Protocol (IP) address of the client that is making the request to determine the client's site.
When the client has local access to the computer (Loopback mode), the IP address that is passed on to Dfs is not the real address of the computer. Given these situations, Dfs clients receive a randomized list of Dfs referrals that contain all members of the Dfs root or link, regardless of site preference.
The access to offsite referrals may cause dial-on-demand events, or consume excessive bandwidth if large amounts of data are accessed from offsite Dfs shares (such as a Group Policy-initiated installation of programs).
RESOLUTIONA supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Windows 2000 service pack that contains this hotfix. To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: NOTE: In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
The English version of this fix should have the following file attributes or later:
Date Time Version Size File name
-----------------------------------------------------
11/10/2000 05:18a 5.0.2195.2694 90,384 Dfssvc.exe
WORKAROUND
As a workaround, run Terminal Services on a separate member server; run Dfs on the Windows 2000-based domain controller in the same Active Directory site so that the Dfs client provides and receives correct site information.
STATUSMicrosoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.
| Modification Type: | Minor | Last Reviewed: | 10/7/2005 |
|---|
| Keywords: | kbHotfixServer kbQFE kbbug kbDFS kbfix kbQFE kbWin2000PreSP2Fix KB274411 |
|---|
|