Troubleshooting Client for NFS
Applies To: Windows 7, Windows Server 2008 R2
What problem are you having?
I need Client for NFS to only use “privileged” ports.
An error occurred while trying to communicate with the Client for NFS service.
System error 1722 has occurred. The remote procedure call (RPC) server is unavailable.
An attempt to mount a shared directory produces network error 67 — the network name was not found.
I received the message RPC: Timed out or RPC: Port mapper failure – RPC: Timed out.
A file I created on an NFS shared resource 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).
I cannot access files on an NFS shared resource.
I cannot access files on a mapped network drive.
I cannot access a multipart export using a Universal Naming Convention (UNC) path.
I cannot mount a shared root directory (/) on a UNIX computer.
I received a delayed write error message.
Attempting to mount with the net use command results in the error message: 1788: The trust relationship between the primary domain and the trusted domain failed.
Even after changing the default permissions for new files, new files on a mount are still created with the previous permissions.
After restarting the computer, the mount parameters of a persistent mount are changed.
Authenticated users cannot access NFS resources, or all NFS shared resources are accessed as Anonymous.
I need Client for NFS to only use “privileged” ports.
Cause
Some Network File System (NFS) servers have a concept of “privileged” ports (meaning ports numbered lower than 1024), and will not accept client connections from ports above that range.
Solution
Log onto computers running Client for NFS, set the following registry key to 1, and then restart Client for NFS:
HKLM\Software\Microsoft\Client for NFS\CurrentVersion\default
DWORD “UseReservedPorts”
An error occurred while trying to communicate with the Client for NFS service.
Cause
The Client for NFS service is not started, cannot contact Active Directory or the User Name Mapping server, or is running with credentials that are mapped incorrectly.
Solution
In the Services for Network File System Microsoft Management (MMC) console, you can ensure that the service is started by right-clicking Client for NFS, and then clicking Start. In the console, ensure that the name of the correct Active Directory domain or User Name Mapping server is specified. Check with the administrator of the Active Directory or the User Name Mapping server to ensure that your Windows user identity is properly mapped to your UNIX user identity.
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 Network File System, right-click Client for NFS, and then click Start.
An attempt to mount a shared directory produces network error 67 — the network name was not found.
Cause
The directory is not shared, or the server is unable to resolve the client name.
Solution
Use showmount –eserver 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 NFS server to ensure that the NFS and Portmap services are started on the server. Also, ensure that the NFS server accepts connections from this computer.
I received the message RPC: Timed out or RPC: Port mapper failure – RPC: Timed out.
Cause
Either the Portmap or NFS services are not running on the server, or Client for NFS performance settings need to be adjusted.
Solution
Ensure that the services are started. If Portmap and NFS services are running on the server, in Services for Network File System, right-click Client for NFS, click Properties, and then increase the maximum number of retries and the interval between retries.
A file I created on an NFS shared resource 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 identity is not properly mapped in Active Directory or User Name Mapping.
Solution
In the Services for Network File System snap-in, ensure that the name of the correct Active Directory domain or User Name Mapping server is specified. Check with your Active Directory or User Name Mapping administrator to ensure that your Windows user identity is properly mapped to your UNIX user identity.
I cannot access files on an NFS shared resource.
Cause
Services for NFS has not designated an Active Directory domain or a User Name Mapping server for use.
Solution
Specify the correct Active Directory domain or User Name Mapping server. For more information, see Specifying how Client for NFS retrieves UNIX-style identity data.
I cannot access files on a mapped network drive.
Cause
Services for NFS has not designated an Active Directory domain or a User Name Mapping server for use.
Solution
Specify the correct Active Directory domain or User Name Mapping server. For more information, see Specifying how Client for NFS retrieves UNIX-style identity data.
I cannot access a multipart export using a Universal Naming Convention (UNC) path.
Cause
Client for NFS can only access a multipart export, such as server:/d1/d2/d3, when the shared resource is mounted to a drive letter.
Solution
Mount the multipart export to a drive letter:
mount server:/d1/d2/d3 *
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 cannot mount it by using the standard path syntax (net use * \\server\ or net use server:/).
Solution
To mount the root directory, type this command:
net use * \\server\!
The share name must be an exclamation mark (!).
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 –eserver command to determine whether the NFS server is running properly.
Attempting to mount with the net use command results in the error message: 1788: The trust relationship between the primary domain and the trusted domain failed.
Cause
You are attempting to access a computer in an untrusted domain, and either Client for NFS has not started on your computer or the shared resource is not available on the NFS server.
Solution
In the Services for Network File System snap-in, right-click Client for NFS, and then click Start. From a command prompt, use showmount –eserver to display the names of shared directories on the server. If this fails with an RPC timeout, contact the administrator of the NFS server to ensure that the NFS and Portmap services are started on the server and that the shared resource 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.
Authenticated users cannot access NFS resources, or all NFS shared resources are accessed as Anonymous.
Cause
Services for NFS is not configured to retrieve UNIX-style identity data from Active Directory or User Name Mapping.
Solution
In the Services for Network File MMC console, right-click Services for NFS, click Properties, and ensure that the proper Active Directory domain name or User Name Mapping server name is set.
If you are using User Name Mapping, ensure that the .maphosts file on the computer that is running User Name Mapping specifies the name or IP address of this computer.