DFS referral queries do not return the fully qualified domain name of the DFS root in a Windows Server 2003 cluster environment

You configure a stand-alone Distributed File System (DFS) root in a Microsoft Windows Server 2003 cluster environment. When you turn on the DfsDnsConfig registry key to enable fully qualified domain name (FQDN) referrals, the DFS referral queries may respond with the NetBIOS name and not with the FQDN of the DFS root. For example, the queries may respond with \NetBIOSName\DFSrootShare.

Additionally, when you try to access a DFS resource from a trusted domain by using the FQDN of the DFS resource, you may receive the following error message: Note This problem does not occur on stand-alone Microsoft Windows Server 2003-based computers that use a stand-alone DFS root.

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:

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: 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 tool in Control Panel.

Windows Server 2003, x86-based versions

Windows Server 2003 with SP1, x86-based versions

Windows Server 2003, x64-based versions

Windows Server 2003, Itanium-based versions

Windows Server 2003 with SP1, Itanium-based versions

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Windows Server 2003 Service Pack 2.

By default, DFS uses NetBIOS name resolution for all network shares that are configured in the DFS namespace. In this case, DFS clients that only support NetBIOS name resolution can locate and connect to the shares in the DFS namespace. However, DFS clients that do not use NetBIOS name resolution may not be able to resolve the name of a DFS share.

DFS can also operate in a Domain Name System (DNS)-only environment, where all the computers use FQDNs for name resolution. To operate in that environment, you must add the DFSDnsConfig registry key on each server that participates in the DFS namespace. Add the key to the servers before the DFS namespace is built. In that way, clients will see FQDNs when the clients are referred to other servers as part of the DFS referral process.

You can use the Dfsutil.exe command-line tool to verify DFS internal information. To do this, follow these steps:

1. Click Start, click Run, type cmd, and then click OK.
2. At the command prompt, type dfsutil /pktinfo.
3. If this problem exists, the tool responds with \NetBIOSName\DFSRootShare instead of \FQDN\DFSRootShare.

For more information about how to use the Dfsutil.exe tool, type dfsutil /? at the command prompt.

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

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

Technical support for Windows x64 editions

Your hardware manufacturer provides technical support and assistance for Microsoft Windows x64 editions. Your hardware manufacturer provides support because a Windows x64 edition was included with your hardware. Your hardware manufacturer might have customized the Windows x64 edition installation with unique components. Unique components might include specific device drivers or might include optional settings to maximize the performance of the hardware. Microsoft will provide reasonable-effort assistance if you need technical help with your Windows x64 edition. However, you might have to contact your manufacturer directly. Your manufacturer is best qualified to support the software that your manufacturer installed on the hardware.

For product information about Microsoft Windows XP Professional x64 Edition, visit the following Microsoft Web site: For product information about Microsoft Windows Server 2003 x64 editions, visit the following Microsoft Web site: