The following provides best practices for using Client for
NFS:
Use the correct command prompt
If you are running Client for NFS and use a command prompt, you
should use the 32-bit version (Cmd.exe) available through the
Start menu. Do not use the 16-bit version
(Command.com).
Avoid using hard mounts
Regardless of the mount type, Client for NFS will stop trying to
mount the network drive if it cannot do so. Once the network drive
has been successfully mounted, however, if the mount type is
hard, Client for NFS will continue to try to access the
mounted drive until it is successful. As a result, if the network
file system (NFS) server is unavailable when a program tries to
access the mounted drive, Windows will appear to hang if the mount
type is hard. Also, the umount command will
disconnect a hard mount even if the server is unavailable. For more
information, see Understanding
mount types.
Do not use PCNFS authentication to authenticate users on
hosts containing sensitive information
The PCNFS protocol uses a very weak form of encryption to protect
passwords, and so it is likely that anyone who can intercept the
encrypted password on the network can recover the plain-text
password. For this reason, you should not use PCNFS authentication
to control access to hosts that contain critical or confidential
data.