You are currently offline, waiting for your internet to reconnect

FIX: Windows Applications Cannot Write to a File After the File is Given Write Access by a UNIX Client

This article was previously published under Q330032
This article has been archived. It is offered "as is" and will no longer be updated.
Some Windows applications cannot open a file to write to it after a UNIX application gives it group or world write permissions by means of Server for NFS.
To enforce strict UNIX semantics, Server for NFS enables the write extended attributes permission for only the owner.

The Windows write permission requires write extended attributes to be enabled. A Windows application does not successfully open the file if it requires the general write permission (instead of requiring just the write data permission).
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem.

To resolve this problem, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site: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.

The English version of this fix has the file attributes (or later) 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   --------------------------------------------------------------   12-Dec-2002  13:28  7.0.1701.8   23,040  Dsctrs.dll          12-Dec-2002  13:29  7.0.1701.8   25,088  Nfsonly.exe         12-Dec-2002  13:29  7.0.1701.8   66,560  Nfssh.dll           12-Dec-2002  14:54  7.0.1701.8   88,576  Nfsshare.exe        12-Dec-2002  13:29  7.0.1701.8  143,360  Nfsshex.dll         12-Dec-2002  13:28  7.0.1701.8  114,176  Nfssprop.dll        21-Dec-2002  03:11  7.0.1701.8   96,768  Nfssvc.exe          12-Dec-2002  13:28  7.0.1701.8  323,488  Nfssvr.sys   12-Dec-2002  13:29  7.0.1701.8  321,440  Nfssvrn4.sys   12-Dec-2002  13:28  7.0.1701.8   73,024  Rpcxdr.sys				
Microsoft has confirmed that this is a bug in the Microsoft products that are listed at the beginning of this article.
Alternatively, to work around this issue, follow these steps:
  1. Give write extended attributes to the Everyone group in the root directory of the share.
  2. Make the entry inheritable by all files and folders.
  3. Enable KeepInheritance for the computer.
For additional information about inheritance, click the following article number to view the article in the Microsoft Knowledge Base:
321049 ACE Inheritance in Windows Services for UNIX

Article ID: 330032 - Last Review: 02/27/2014 21:15:26 - Revision: 1.4

Microsoft Windows Services for Unix 2.3, Microsoft Windows Services for UNIX 3.0 Standard Edition

  • kbnosurvey kbarchive kbbug kbfix kbqfe kbhotfixserver KB330032