What trouble are you having?

All user requests are transmitted as Anonymous.

Cause:  Authentication is not configured properly.

Solution:  Ensure that mappings are set up correctly in User Name Mapping and that Gateway for NFS is configured to use the correct User Name Mapping server.

An attempt to communicate with the Gateway for NFS service produced an error.

Cause:  The Gateway for NFS service is not started.

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

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

Cause:  The Gateway for NFS Service is not started.

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

An attempt to mount a shared directory produced network error 53 or 67.

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

Solution:  Use the showmount –e server command to display the names of shared directories on the network file system (NFS) server. Ensure that the Internet Protocol (IP) address of the computer running Gateway for NFS is specified in either NFS server file /etc/hosts, or in the DNS database, as appropriate.

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

Cause:  The port mapper or network file system (NFS) server daemons are not running on the NFS server.

Solution:  Ensure that the daemons are started.

I cannot mount a shared root (/) directory on the network file system (NFS) server.

Cause:  Gateway for NFS cannot mount the root directory using the standard path syntax.

Solution:  Mount the root directory using 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:  Nfsrdr service failed to start, or the Service Manager erroneously reported that the service failed to start. Event Viewer might contain an event log 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 Gateway for NFS service has started. If it has started, ignore this message. If it has not started, start the Gateway for NFS service. For more information, see To start Gateway for NFS.

After the server restarts, an error message indicates that the Server service was not started and Gateway for NFS shares are not reconnected.

Cause:  Gateway for NFS started before the Server service.

Solution:  Check to ensure that both Gateway for NFS and Server services have started, then reconnect the Gateway for NFS shares.

Authenticated users cannot access NFS resources, or access them 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 via 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, too many client computers might be 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.

Attempts to create, delete, or perform other operations on files and directories fail, producing the error Operation timed out.

Cause:  Network congestion is preventing operations from completing in the allotted time.

Solution:  Use Registry Editor to change registry values to give operations more time and opportunities to complete:

Note that these settings can adversely affect Gateway for NFS performance when network conditions are normal. Once the problems causing network congestion are solved, you should reset these values to their default settings.