Open System Services NFS Overview

A Troubleshooting for Client Users
Before You Begin
Before you issue requests for OSS NFS services:
1. Ask your system manager to register your user ID and group ID on the OSS NFS subsystem.
2. If you want to access files in an existing OSS NFS file system, ask the system manager for the
pathnames of the directories you are allowed to mount on your local system.
Troubleshooting Client Problems
Table 2 contains information about recovering from errors NFS client users might encounter.
Table 2 Troubleshooting for Client Users
Probable Causes and Possible CorrectionsClient Indicates
No Response 1. No network access path exists between the NFS client and NFS server systems.
Check that the network connections are functional and that the user can use a form of the
ping command between the client and server.
Contact the OSS NFS server administrator for help.
2. The PORTMAP process or the OSS NFS subsystem is not running on the NonStop system.
Check that OSS NFS is started on your server using the rpcinfo program on your PC or
workstation or on the NonStop system from a TACL prompt; enter the following command:
rpcinfo -p [ hostname ]
where hostname is the name of the NonStop system that should be running your OSS NFS
server.
Contact the OSS NFS server administrator for help.
Access Denied 1. The client specified an invalid mount point.
Correct the specified mount point.
2. No OSS NFS server process is running for the specified mount point.
Request that the appropriate OSS NFS server be started.
3. The client host is not permitted to use the specified mount point, because it was not exported
for that host.
Contact the OSS NFS server administrator for help.
4. The user name or password specified by the client system is not valid.
Correct the value entered or contact the OSS NFS server administrator for help.
5. You attempted to access an object on a NonStop server that is protected by optional OSS
ACL entries, and server is running an RVU earlier than J06.09 or H06.20.
Contact the OSS NFS server administrator and OSS fileset administrator for help.
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.
Contact the OSS NFS server administrator and OSS fileset administrator for help.
Before You Begin 19