Windows Explorer stops responding, or you receive an "unexpected network error occurred" error message when you use the Client for NFS service to connect to a NFS volume in Windows Services for UNIX 3.5
This article has been archived. It is offered "as is" and will no longer be updated.
Some earlier versions of UNIX run kernels that do not support versions of Network File System (NFS) that are later than version 2.0.
In Microsoft Windows Services for UNIX 3.5, you may use the Client for NFS service to connect to a NFS volume that was exported by an earlier version of UNIX. When you do this, you experience one of the following issues:
On the Performance tab of the Client for NFS service, you set the Mount type property to Soft. When you try to connect or to map a network drive to an earlier version of a NFS 2.0-exported volume, Windows Explorer stops responding.
When you set the Mount type property to Hard, you receive the following error message:
An unexpected network error occurred.
Additionally, the network drive is not mapped or the connection is not established.
These issues occur because even though some earlier versions of the UNIX kernel do not support NFS 3.0, the mountd service (NFS mount daemon) on the server advertises NFS 3.0.
To resolve this issue, use the following initialization option for the mountd service:
After you restart the mountd service by using this initialization option, Windows Services for UNIX 3.5 correctly connects to the NFS 2.0 remote volume.