11.0 Troubleshooting the NFS Gateway for NetWare 6.5

This section presents some common troubleshooting scenarios you might encounter when using the NFS Gateway for NetWare 6.5 and how to resolve them.

Reducing mount time while troubleshooting mount failures
Maximum NFS Gateway volumes that can be mounted at a time
Unable to mount volumes although several volumes have been mounted /dismounted previously and no error message is displayed on the logger screen
Handling server abends
The NFS Gateway hangs on loading without any error message
Dismounting a Gateway volume takes a long time when network connectivity to the UNIX server is lost
When using an NFS Gateway volume, the client times out with the message "The specified network name is no longer available"
Even after renaming the target directory from UNIX, the symbolic link directory continues to display previous contents
Trustee information is lost when using a Gateway volume in a cluster enabled environment or using a newly mounted NSS volume as a shadowVolume
In the gystart.ncf file, the nfsgy entry is added even if nfsgy has not been executed
NFS Gateway is not using the NFSGY.NLM parameters specified in GYSTART.NCF
Uninstall is not removing NFS Gateway from the server
The text and the buttons in the NFS Gateway iManager Plug-in are not aligned properly
Unable to mount volumes with message "Old shadow file format found. Load "NFSGYMIG.NLM [<ShadowVolume:>]" to migrate the shadow files."