Microsoft KB Archive/837197

= FIX: The Client for NFS cannot resolve a symbolic link that is based on AUTO_HOME and other related maps in Windows Services for UNIX =

Article ID: 837197

Article Last Modified on 10/10/2006

-

APPLIES TO


 * Microsoft Windows Services for UNIX 3.0 Standard Edition
 * Microsoft Windows Services for UNIX 3.5

-



Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:

256986 Description of the Microsoft Windows registry



SYMPTOMS
In Microsoft Windows Services for UNIX, the Client for NFS cannot resolve a symbolic link that is based on AUTO_HOME and other related maps.



CAUSE
This problem occurs because the Client for NFS cannot resolve the remote target of a symbolic link file.



Windows Services for UNIX 3.0
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that this article describes. Apply it only to systems that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:

http://support.microsoft.com/contactus/?ws=support

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 usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

Prerequisites
No prerequisites are required.

Restart requirement
You must 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.   Date         Time   Version      Size     File name --  19-Feb-2004  18:06  7.0.1701.31  312,448  Nfsrdr.sys 19-Feb-2004 18:06  7.0.1701.31  359,072  Nfsrdrn4.sys 19-Feb-2004 18:06  5.0.2134.1    35,600  Regini.exe

Windows Services for UNIX 3.5
For Windows Services for UNIX 3.5, this new functionality is included in hotfix 884852.

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

884852 FIX: The Windows Services for UNIX Client for Network File System (NFS) stops responding when you use Windows 2000 with Service Pack 4 as the Client for NFS and Linux as the Server for NFS



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



MORE INFORMATION
This hotfix adds new functionality to Client for NFS. This new functionality lets you access the target of a symbolic link when the symbolic link resolves to a remote NFS share by using DFS links.

Consider the following scenario of an UNIX environment with which the Client for NFS must interop:
 * NFSServer1 hosts a NFS share that is named /home.
 * NFSServer2 hosts a NFS share that is named /data.
 * Assume that the auto mounting mechanism resolves /home and /data to the respective NFS servers of each share. UNIX NFS clients access the following:
 * Symbolic link /home/user1/link-file1 to /data/dir-xyz/file1
 * Symbolic link /home/user1/link-dir1 to /data/dir-xyz/dir1

This feature enables the Client for NFS to perform the following specific tasks:
 * Read and write to /home/user1/link-file1.
 * Create or delete files and directories in /home/user1/link-dir1.

These tasks are achieved by resolving /home/user1/dir-xyx to a UNC path through \\NFSServer2\data\dir-xyz.

Note This feature has the following limitations:
 * Attributes of the link-file1 and link-dir1 remote links may not correctly show up.
 * Changing the directory into remotely linked directories (link-dir1) may not work.

For this scenario, you must have the following Microsoft Windows environment:
 * A DFS server that is named DFSServer.
 * A DFS root that is named DFSRoot.
 * A DFS link that is named dir-xyz that points to \\NFSServer2\data\dir-xyz.

You must add the  registry entry to the registry and then add the list of symbolic links. To do this, follow these steps:

Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.  Click Start, click Run, type regedit, and then click OK. Locate and then click the following registry subkey:

 

 On the Edit menu, click New, and then click Multi-String Value. Type MountSymlinkDfsMaps, and then press ENTER. Right-click MountSymlinkDfsMaps, and then click Modify.</li> In the Edit Multi-String dialog box, type a list of DFS link names. For this scenario, you must add the following DFS link:

/data:\\DFSServer\DFSRoot

</li></ol>

When the Client for NFS encounters the /home/user1/link1 link, it resolves the target as /data/dir-xyz/file1. Then, /data/dir-xyz/file1 is parsed based on the contents of the  registry entry as follows:
 * 1) The /data is converted to \\DFSServer\DFSroot.
 * 2) The /data/dir-xyz becomes \\DFSServer\DFSroot\dir-xyz.
 * 3) The \\DFSServer\DFSroot\dir-xyz becomes \\NFSServer2\data\dir-xyz.
 * 4) The \\NFSServer2\data\dir-xyz\file1 is read.