Troubleshooting

What trouble are you having?

An error occurred while trying to communicate with the Client for NFS service.

Cause:  The Client for NFS service is not started, cannot contact the User Name Mapping server, or the mapped credentials are incorrect.

Solution:  In Services for UNIX Administration, right-click Client for NFS, and then click Start. In Services for UNIX Administration, ensure that the name of the correct User Name Mapping server is specified. Check with the administrator of the User Name Mapping server to ensure that your Windows user account is properly mapped to your UNIX user account. If you are attempting to mount a network file system (NFS) shared directory using PCNFS credentials, be sure to provide the correct user name and password.

System error 1722 has occurred. The remote procedure call (RPC) server is unavailable.

Cause:  The Client for NFS Service is not started.

Solution:  In Services for UNIX Administration, right-click Client for NFS, and then click Start.

An attempt to mount a shared directory produces a network error 67.

Cause:  The directory is not shared, or the server is unable to resolve the client name.

Solution:  Use showmount –e server to display the names of shared directories on the server. If this fails with a remote procedure call (RPC) time-out, contact the administrator of the network file system (NFS) server to ensure that the NFS and portmap services are started on the server. Ensure that the Internet Protocol (IP) address of the client is specified in either the server /etc/hosts file, or in the DNS database, as appropriate.

I received an RPC: Timed out or RPC: Port mapper failure – RPC: Timed out message.

Cause:  Either the port mapper or network file system (NFS) server daemons are not running on the server, or Client for NFS performance settings need to be adjusted.

Solution:  Ensure that the services are started. If the port mapper and NFS server daemons are running on the server, in Services for UNIX Administration, click Client for NFS, click Performance, and then increase the maximum number of retries and the interval between retries.

A file I created on a mounted network file system (NFS) drive is shown as having been created by nobody:nogroup or by –2:–1, or the user identifier (UID) is a very large number (2**32-2).

Cause:  Your Windows user name is not properly mapped in User Name Mapping.

Solution:  Use the mount command to determine the user identifier (UID) and group identifier (GID) that Client for NFS is using. If it is –2:–2, your Windows user account is not properly mapped. In Services for UNIX Administration, check to ensure that the name of the correct User Name Mapping server is specified. Check with the administrator of the User Name Mapping server to ensure that your Windows user account is properly mapped to your UNIX user account.

When I attempt to map a network drive, I am asked for a user name and password, and then the attempt to map the drive fails even though I supply valid credentials.

Cause:  A User Name Mapping server has not been designated for use by Windows Services for UNIX.

Solution:  Specify the server running User Name Mapping for your network. For more information, see To set up authentication using User Name Mapping.

I cannot access files on a mapped network drive.

Cause:  A User Name Mapping server has not been designated for use by Windows Services for UNIX.

Solution:  Specify the server running User Name Mapping for your network. For more information, see To set up authentication using User Name Mapping.

I cannot mount a shared root directory ("/") on a UNIX computer.

Cause:  When a root directory ("/") on a UNIX computer is shared, Client for NFS will not be able to mount it using the regular syntax of net use * \\server\ or net use server:/.

Solution:  To mount the root directory, enter this command:

net use * \\server\!

The share name must be an exclamation mark (!).

I received an error message stating that a service failed to start.

Cause:  The Service Control Manager might display an event in Event Viewer with the following message:

The NfsRdr service failed to start due to the following error:
The system cannot find the file specified.

Solution:  Check to determine whether the Client for NFS service has started. If it has started, you can ignore this message. If it has not started, start the Client for NFS service. For more information, see To start Client for NFS.

MS-DOS or earlier Windows applications cannot access files on NFS, or a message appears indicating that a 16-bit application cannot be run.

Cause:  By default, Client for NFS does not convert UNIX long file names to MS-DOS–style 8.3 format.

Solution:  Using the Microsoft Registry Editor (regedit.exe), ensure that the following value is set to 1 (the default):

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Client for NFS\CurrentVersion\Users\Default\Defaults\8.3Format

This causes Client for NFS to convert all UNIX file names to the 8.3 format required by MS-DOS applications and by applications designed to run with Windows 3.x and earlier. Setting this value to 0 improves Client for NFS performance somewhat because Client for NFS does not convert file names.

I received a delayed write error message.

Cause:  Either the NFS server is not responding or the Client for NFS performance options are not properly adjusted.

Solution:  Use the showmount –e server command to determine whether the NFS server is running properly. If it is, adjust the Client for NFS performance options; see To set performance options for more information.

Attempting to mount with the net use command produces the error: 1788: Trust relationship is broken.

Cause:  You are attempting to access a computer in another, untrusted domain, and either Client for NFS has not started on your computer or the share is not available from the NFS server.

Solution:  In Services for UNIX Administration, right-click Client for NFS, and then click Start. Use showmount –e server to display the names of shared directories on the server. If this fails with an RPC time-out, contact the administrator of the NFS server to ensure that the NFS and portmap services are started on the server and that the shared directory is available.

Even after changing the default permissions for new files, new files on a mount are still created with the previous permissions.

Cause:  This is by design. New default permissions are only applied to new mounts.

Solution:  Unmount and then remount the shared directory.

After restarting the computer, the mount parameters of a persistent mount are changed.

Cause:  You used the net use command to mount the directory.

Solution:  Use the mount utility to mount the directory.

I cannot mount using PCNFS credentials.

Cause:  Peristent PCNFS mounts are not allowed.

Solution:  Turn off persistent connections by using the net use /pers:no command.

Authenticated users cannot access NFS resources, or all NFS shares are accessed as Anonymous.

Cause:  User Name Mapping is not properly configured to work with this computer.

Solution:  Ensure that the .maphosts file on the computer running User Name Mapping specifies the names or Internet Protocol (IP) addresses of computers that can map user accounts by using User Name Mapping. For more information, see Controlling access to User Name Mapping. If users cannot access NFS resources intermittently and configuring the .maphosts file does not solve the problem, it could be that too many client computers are trying to access User Name Mapping simultaneously. See "Error message: Unable to perform the requested operation as the mapping service cannot be contacted" in User Name Mapping Troubleshooting.