Microsoft KB Archive/885930

= FIX: Network File System (NFS) client users that do not have the &quot;List Folder / Read Data&quot; permission can still see the file list from an NFS share =

Article ID: 885930

Article Last Modified on 11/15/2007

-

APPLIES TO


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

-





SYMPTOMS
From some Network File System (NFS) clients, including UNIX and Linux, users that do not have &quot;List Folder / Read Data&quot; permissions can still see the file list from an NFS share.



CAUSE
This problem occurs because of the following conditions:
 * Client-side caching is enabled.
 * Server for NFS returns incorrect information to &quot;ACCESS&quot; requests.



RESOLUTION
A supported hotfix is now available from Microsoft. However, this hotfix is intended to correct only the problem that this article describes. Apply this hotfix only to systems that are experiencing this specific problem.

To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:

http://go.microsoft.com/?linkid=6294451

Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:

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

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.

Microsoft Windows Services for UNIX 2.3
  Date         Time   Version         Size     File name -  08-Oct-2004  00:20  5.3000.2117.17   78,336  Clilocks.dll 08-Oct-2004 00:20  5.3000.2117.17   12,208  Clusnfs.exe 08-Oct-2004 00:20  5.3000.2117.17   22,528  Dsctrs.dll 08-Oct-2004 00:20  5.3000.2117.17   10,704  Nfsonly.exe 08-Oct-2004 00:20  5.3000.2117.17   66,048  Nfssh.dll 08-Oct-2004 00:20  5.3000.2117.17   94,208  Nfsshare.exe 08-Oct-2004 00:20  5.3000.2117.17  143,360  Nfsshex.dll 08-Oct-2004 00:20  5.3000.2117.17  113,664  Nfssprop.dll 08-Oct-2004 00:20  5.3000.2117.17   94,720  Nfssvc.exe 08-Oct-2004 00:20  5.3000.2117.17  324,192  Nfssvr.sys 08-Oct-2004 00:20  5.3000.2117.17   40,832  Portmap.sys 14-Dec-2001 06:31  5.0.2134.1       35,600  Regini.exe 08-Oct-2004 00:20  5.3000.2117.17   72,800  Rpcxdr.sys 10-Apr-2003 07:14                   27,102  Supphelp.chm 08-Oct-2004 00:20  5.3000.2117.17   48,128  Upnfs3.exe

Services for UNIX 3.0
  Date         Time   Version      Size     File name --  08-Oct-2004  01:34  7.0.1701.37   23,040  Dsctrs.dll 08-Oct-2004 01:34  7.0.1701.37   26,624  Nfsonly.exe 08-Oct-2004 01:34  7.0.1701.37   67,584  Nfssh.dll 08-Oct-2004 01:34  7.0.1701.37   90,112  Nfsshare.exe 08-Oct-2004 01:34  7.0.1701.37  144,896  Nfsshex.dll 08-Oct-2004 01:34  7.0.1701.37  114,688  Nfssprop.dll 08-Oct-2004 01:34  7.0.1701.37   98,304  Nfssvc.exe 08-Oct-2004 01:34  7.0.1701.37  325,184  Nfssvr.sys 08-Oct-2004 01:34  7.0.1701.37  323,296  Nfssvrn4.sys 08-Oct-2004 01:34  7.0.1701.37   42,624  Portmap.sys 08-Oct-2004 01:34  7.0.1701.37   73,056  Rpcxdr.sys

Services for UNIX 3.5 (Windows 2000 and Windows XP)
  Date         Time   Version      Size     File name 07-Oct-2004 12:19  8.0.1969.17  326,016  Nfssvr.sys

Services for UNIX 3.5 (Windows Server 2003)
  Date         Time   Version     Size     File name ---  08-Oct-2004  00:23  8.0.2254.5  423,552  Nfssvr.sys



WORKAROUND
To work around this problem, use one of the following methods:
 * Use NFS 2.0.
 * Disable the client-side cache in Linux or in UNIX.



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

