Share via

Client for NFS best practices

  • Article

Applies To: Windows Server 2003 R2

Use the correct command prompt.

If you are running Client for NFS and using a command prompt, you should use the 32-bit version (Cmd.exe), which is available through the Start menu. Do not use the 16-bit version (Command.com). You must run Nfsadmin.exe from an elevated privilege command prompt to change Client for NFS configuration settings.

Avoid using hard mounts.

Regardless of the mount type, Client for NFS will not indefinitely try to mount an NFS shared resource. Once the shared resource has been successfully mounted, if the mount type is a hard mount and the Network File System (NFS) server becomes unavailable, Client for NFS will retry accessing the shared resource until the NFS server is once again available. As a result, Windows applications that are trying to access the shared resource will appear to stop responding.

Note

The umount command will disconnect a hard mount — even if the server is unavailable.