Technical article 100046

Group permissions are not recognized on an NFS exported AFPS share.

OpenServer 5.0.0OpenServer 5.0.2

Written · Last revised

Problem

If an NFS exported fileystem is shared as an AFPS share and the "unixgroups" and "unixdirchk" flags have been set on the AFPS server, Microsoft Windows 95 or Windows for Workgroups PC client users are unable to create new files on that share according to their group permission.

As an example only, the AFPS server has both the "unixgroups" and
"unixdirchk" flags set within the "/usr/net/servers/lanman/lanman.ini"          file:

... [ lmxserver ] ... locale=english_us.8859 fileperms=00664 unixgroups=yes unixdirchk=0 ...

The "unixgroups" flag allows files and directories created on the AFPS share to assume the same UNIX group identity as that of the creator's UNIX group rather than default to the "DOS----" group.

The "unixdirchk" flag allows files and directories to be created on the AFPS share depending on its setting:

- If set to "0", clients may create files only if they have UNIX write permission for that directory. They can gain this permission by being a member of the same UNIX group as the owner of the directory, usually the UNIX "group" group.

- If set to "1", the default, clients are allowed to write to directories if owned or created by the Advanced Server, that is, with "DOSxxxx" permissions.

- If set to "2", UNIX permissions are ignored.

In this example, the default file permission of any newly created file will be 664 or "rw-rw-r--" as determined by the "fileperms" flag.

An NFS filesystem, "/u/work", has been exported with root access to an AFPS primary domain controller system called "barney" in the domain "AFPS1" as follows:

(/etc/exports)
/u/work -root=barney.europa.test.COM

The export is NFS mounted onto the "/nfstest" directory as per:

/nfstest on barney:/u/work read/write on Thu Apr 03 16:21.....

The directory has the following permissions:
drwxrwxr-x  2 root   group    512 Apr  3 16:40 nfstest

This directory is then shared as an AFPS share using the command "net share work1=c:/nfstest". An AFPS user "user1", who is also a local UNIX user, has been created on "barney".

As the "unixgroups" and "unixdirchk" flags have been set and the AFPS share directory has "rwx" permissions set for "group", a user belonging to that UNIX group should be able to write to that AFPS share. If, however, "user1" logs into the domain "AFPS1" and attaches to the "work1" share and attempts to create a new file, the following errors appear:

From Windows for Workgroups (WFWG) 3.11 File Manager:

Access is denied

Make sure the disk is not full or write protected.

From an MS-DOS Window:
The network has responded incorrectly
Abort, Retry, Fail ?

The Microsoft Notepad facility fails to "Save as" with:

Cannot access this file.

Please verify security privileges on the network drive.

This problem is not seen with non-NFS based AFPS shares.

Solution

This problem has been reported to SCO Engineering.

Files can be created if the share ownership (/nfstest, in this case)
is changed to the user attempting to create the file, (user1) using
chown(C), or if the directory permissions are changed to 777 using
chmod(C).

The user is able to write to existing files and can write to sub-directories of the AFPS share main directory it has itself created.

See also

SCO Advanced File and Print Server System Guide, Appendix B.

From the Xinuos technical article database, record 100046. Reproduced with permission. The original is at www.sco.com/ta/100046, which is reachable but blocked from search engines. Xinuos marks this article against a retired product line. That refers to the product’s lifecycle, not to whether the advice still works — plenty of it still applies to running systems.

Next step

Need this fixed rather than explained?

Tell us the release, what the system runs and what it is doing. We will reply by email with what we would do next.

  • You deal with the people who do the work
  • No obligation, and no upgrade required before we will help
  • We tell you plainly if something is not worth doing

Send an enquiry

We reply by email. If a server is down, say so in the first line. You can also write to help@scoexpert.com.