Article ID: 900622
Article Last Modified on 10/11/2007
APPLIES TO
- Microsoft Windows Server 2003, Web Edition
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition
- Microsoft Windows Server 2003, Standard x64 Edition
- Microsoft Windows Server 2003, Enterprise x64 Edition
- Microsoft Windows Server 2003, Enterprise Edition for Itanium-based Systems
SYMPTOMS
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.
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 How to obtain the latest service pack for Windows Server 2003
Hotfix information
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
Date Time Version Size File name -------------------------------------------------------------- 17-Jun-2005 00:19 5.2.3790.350 137,728 Dfssvc.exe
Windows Server 2003 with SP1, x86-based versions
Date Time Version Size File name -------------------------------------------------------------- 17-Jun-2005 00:55 5.2.3790.2467 164,864 Dfssvc.exe
Windows Server 2003, x64-based versions
Date Time Version Size File name -------------------------------------------------------------- 17-Jun-2005 03:30 5.2.3790.2467 320,512 Dfssvc.exe 17-Jun-2005 03:30 5.2.3790.2467 164,864 Wdfssvc.exe
Windows Server 2003, Itanium-based versions
Date Time Version Size File name -------------------------------------------------------------- 17-Jun-2005 03:30 5.2.3790.350 463,872 Dfssvc.exe IA-64 17-Jun-2005 03:30 5.2.3790.350 137,728 Wdfssvc.exe x86
Windows Server 2003 with SP1, Itanium-based versions
Date Time Version Size File name -------------------------------------------------------------- 17-Jun-2005 03:30 5.2.3790.2467 593,920 Dfssvc.exe IA-64 17-Jun-2005 03:30 5.2.3790.2467 164,864 Wdfssvc.exe x86
STATUS
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.
MORE INFORMATION
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:
- Click Start, click Run, type cmd, and then click OK.
- At the command prompt, type dfsutil /pktinfo.
- If this problem exists, the tool responds with \
NetBIOSName\DFSRootShareinstead 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:
244380 How to configure DFS to use fully qualified domain names in referrals
For more information, 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
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:
Additional query words: Winx64 Windowsx64 64bit 64-bit
Additional query words: Content Maintenance 39748 Windows SE 162275
Keywords: kbbug kbfix kbqfe kbpubtypekc kbwinserv2003presp1fix kbhotfixserver kbwinserv2003sp2fix KB900622
