Microsoft KB Archive/330038

= FIX: You cannot use a new client group until you restart Server for NFS =

Article ID: 330038

Article Last Modified on 10/19/2005

-

APPLIES TO


 * Microsoft Windows Services for Unix 2.3

-



This article was previously published under Q330038



SYMPTOMS
When you create a new client group, or when you add client computers that were added to an existing client group in Server for NFS, and then you use the client group to assign host level permissions on NFS shares, the client group does not take effect until you restart Server for NFS.

The problem occurs only with client groups that were created before you restart Server for NFS. Although client groups are listed and you can add client groups to NFS share permissions, the client groups do not take effect until you restart Server for NFS.

Note If the client group already existed, you can add a new host and the client group works as expected.



RESOLUTION
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. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

330032 FIX: Windows applications cannot write to a file after the file is given write access by a UNIX client



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



Steps to reproduce the problem

 * 1) Create a client group that has set your UNIX host as a member.
 * 2) Create a new NFS share and allow anonymous access.
 * 3) Set the share permissions to All-Machines No Access.
 * 4) Add the new client group that contains your UNIX client with Read-Write access.
 * 5) From the UNIX client, try to mount the new share.

You can expect to receive an &quot;access denied&quot; error message.
 * 1) Restart Server for NFS on the server side.
 * 2) From the UNIX client, repeat the command to mount the new share.

You can expect the command to work and to permit you to write files as anonymous.

Keywords: kbbug kbfix KB330038

-

[mailto:TECHNET@MICROSOFT.COM Send feedback to Microsoft]

© Microsoft Corporation. All rights reserved.