Open System Services NFS Management and Operations Guide

Table 3 Troubleshooting for Client Users (continued)
Probable Causes and Possible CorrectionsClient Indicates
6. You attempted to access an object on a NonStop server that is protected by optional
OSS ACL entries, the server is running J06.09 or a later J-series RVU or H06.20 or a
later H-series RVU, and one of these conditions is true:
• The NFSPERMMAP attribute of the OSS fileset is set to DISABLED.
• The NFSPERMMAP attribute of the OSS fileset is set to RESTRICTIVE, and there is an
ACL entry on the list that has permissions that are more restrictive than yours for the
operation you are attempting. That is, there is a user, class, or group in the ACL that
is not permitted to access the file. If you are not the owner of the object, even if you
are legitimately allowed access to the object in the OSS ACL for that object, you
cannot access the object using the NFS.
• You attempted a write operation and you do not have write permission for the object
in the OSS ACL. Write permission is always enforced on the server, even if the
permissions returned to the NFS client indicate that you have write permission.
7. You attempted to access a file on a NonStop server that is in a restricted-access fileset,
and you do not have the appropriate privilege to access that file.
8. You attempted to write to an object that has one or more file privileges.
Invalid Password 1. The user name or password specified by the client system is not valid. The client user
must correct the value entered. If the value is correct, see Chapter 5 (page 57), and to
“USER Object” (page 29).
NOTE: Older versions of PCNFSD do not allow passwords that contain punctuation
characters or do not start with a letter. It might be necessary to change a valid password
to have it accepted by PCNFSD.
2. PCNFSD is not running (for PC or Macintosh clients). See “Starting PCNFSD” (page 49).
3. You do not have an alias user ID defined in the list of OSS NFS users, and the OSS NFS
server-object attribute NULL-ALIAS-OK is set to FALSE. See Chapter 5 (page 57).
4. You did not supply a valid password. Verify that the mapped user ID assigned to the
client user’s OSS NFS user ID exists on the system. Then, have the client user try a TACL
logon using the mapped user ID and the specified password. See Chapter 5 (page 57).
Troubleshooting for Client Users 77