Consider the following scenario:
- You have a computer that is running Windows 7 or Windows Server 2008 R2.
- You access a Distributed File System (DFS) share by using a nested DFS link from the computer. For example, example, assume that the following are domain-based DFS namespaces:
- DFSRoot1: \\Domain name\DFSRoot1
- DFSRoot2: \\Domain name\DFSRoot2
\\Server name\share name
You access the shared folder through the following DFS path:
- You open the Properties dialog box to check the NTFS permissions for the DFS share.
- This issue does not occur if you access the DFS share through one of the following paths:
\\Server name\share name
- This issue typically occurs when the domain controllers in the domain are in different remote sites and resolve the Fully Qualified Domain Name (FQDN) of the domain from a site. This behavior causes a workstation to contact a domain controller in another site. For example, the query time is longer than expected for the following domain controllers:
- Domain controller DC1: (site 1) 10.10.1.1
- Domain controller DC2: (site 2) 192.168.2.1
- Work station WS: (site 1) 192.168.1.1
- For more information about IETF RFC 3484, click the following article number to view the article in the Microsoft Knowledge Base:969029 The functionality for source IP address selection in Windows Server 2008 and in Windows Vista differs from the corresponding functionality in earlier versions of Windows
This issue occurs because the system returns the FQDN of the domain instead of the host name of a nested DFS path. Additionally, when you check the NTFS permissions, the system queries the Domain Name System (DNS) records, and these may point to any domain controller in the domain.
Hotfix informationA 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 website: 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.
PrerequisitesTo apply this hotfix, you must be running Windows 7 Service Pack 1 (SP1) or Windows Server 2008 R2 SP1.
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:
976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2
Registry informationTo apply this hotfix, you do not have to make any changes to the registry.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace a previously released hotfix.
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:
824684 Description of the standard terminology that is used to describe Microsoft software updates