Article ID: 236813
Article Last Modified on 2/27/2007
APPLIES TO
- Microsoft Windows NT Server 4.0, Terminal Server Edition
- Microsoft Windows 2000 Server
- Microsoft Windows 2000 Advanced Server
- Microsoft Windows 2000 Professional Edition
- Microsoft Windows NT Server 4.0 Standard Edition
- Microsoft Windows NT 4.0 Service Pack 5
- Microsoft Windows NT Workstation 4.0 Developer Edition
- Microsoft Windows NT Workstation 4.0
- Microsoft Windows NT Server 4.0 Enterprise Edition
- Microsoft Windows NT 4.0 Service Pack 5
This article was previously published under Q236813
SYMPTOMS
You can use Microsoft Distributed File System (DFS) to map drives directly to folders and subfolders in a DFS share. If your home folder is on a DFS share, the %HOMEDRIVE% variable is mapped only to the DFS root and not to the complete path. This behavior is evident when you view the folder in Windows NT Explorer. In addition, the %HOMEPATH% and %HOMESHARE% variables are not resolved correctly.
For example, if DFS_root is the DFS root on the \\Pkdfs share and your home folder is \\Pkdfs\Dfs_root\Home\User1:
%HOMEDRIVE% (for example, drive Z) is mapped to \\Pkdfs\Dfs_root
%HOMESHARE% resolves to \\Pkdfs\Dfs_root
%HOMEPATH% resolves to \Home\User1.
Instead, %HOMEDRIVE%%HOMESHARE% should resolve to \\Pkdfs\Dfs_root\Home\User1, %HOMEPATH% should resolve to \, and %HOMEDRIVE% (Z:) should map to \\Pkdfs\Dfs_root\Home\User1.
RESOLUTION
Windows NT
To resolve this problem, obtain the latest service pack for Windows NT 4.0 or the individual software update. For information on obtaining the latest service pack, please go to:
- 152734 how to obtain the latest windows nt 4.0 service pack
For information on obtaining the individual software update, contact Microsoft Product Support Services. For a complete list of Microsoft Product Support Services phone numbers and information on support costs, please go to the following address on the World Wide Web:
Windows 2000
By default, Windows 2000 maps the %HOMEDRIVE% variable to your home folder, even if it is on a non-DFS share. In this case, the %HOMEDRIVE% variable is mapped to the \\Pkdfs\Dfs_root\Home\User1 share and the %HOMEPATH% variable resolves to \.
Windows 2000 supports deep share implementation. You can use this feature to directly map to folders in a share if you have appropriate permissions. If your home folder is \\server\share\dir\dir2\%username% (where share is a non-DFS share), your %HOMEDRIVE% variable is mapped to \\server\share\dir1\dir2\%USERNAME% and the %HOMEPATH% variable resolves to \ by default.
You can use the Group Policy Object (GPO) of Active Directory to turn off the deep share feature for the home folder (and keep the behavior the same as Windows NT 4.0). To do this, follow these steps:
- Start Microsoft Management Console (MMC).
- Click the Add/Remove snap-in, and then choose Group Policy from the list.NOTE: You can apply this policy to the local computer, a remote computer, or a set of remote computers.
- Go to the User Configuration\Administrative Templates\System\Logon\Logoff folder.
- Double-click Connect home directory to the root of the share.
- Click Enabled, and then click OK.
When you enable this policy, the %HOMEDRIVE% variable is mapped to \\server\share\ and the %HOMEPATH% variable resolves to \dir1\dir2\%USERNAME% when the share is a non-DFS share.
For a Windows 2000 Server in an NT 4.0 Domain, to open this policy, do the following:
- On the toolbar click Start, click Run, and then type gpedit.msc.
This opens the policy showing both the User and Computer Configuration for the Policy, which is not visable when you open the Local Security Policy.
Windows NT Server 4.0, Terminal Server Edition
To resolve this problem, obtain the latest service pack for Windows NT Server 4.0, Terminal Server Edition. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
152734 How to Obtain the Latest Windows NT 4.0 Service Pack
STATUS
Microsoft has confirmed that this is a problem in Windows NT 4.0 and Windows NT Server 4.0, Terminal Server Edition.
This problem was first corrected in Windows NT Server 4.0 Service Pack 6 and Windows NT Server 4.0, Terminal Server Edition Service Pack 6.
Additional query words: 4.00
Keywords: kbbug kbfix kbqfe kbhotfixserver KB236813
