|
|
|
Inconsistent Connection Errors when Using NFS Client
Technical Note 1795
Last Reviewed 10-Jun-2004
Applies To
Reflection NFS Client
Microsoft Windows
Summary
Technical Note 1795
Last Reviewed 10-Jun-2004
Applies To
Reflection NFS Client
Microsoft Windows
Summary
NFS and SMB network protocols can be used on the same Windows PC concurrently, except when connecting to a server that has both NFS and SAMBA servers enabled. This technical note outlines the symptoms and error messages, explains the background, and provides a solution to this conflict.
Symptoms
When you have an NFS client and an SMB client installed on a Windows machine and you connect to a server that has both NFS and SAMBA enabled (whether SAMBA is loaded on a UNIX server, or Microsoft Services for UNIX—SFU—is enabled on a Windows NT server), the following problems may occur.
The following error message may be displayed:
"An extended error has occurred.""Network name could not be found""Share name could not be found."Or, the user's machine may freeze with an hourglass displayed.
Background
The connection behavior you experience in this environment can be variable because of the way Microsoft Windows handles protocols. Windows assumes that a host and workstation trying to communicate share only a single network protocol in common. When a user requests information located on a remote host, Windows first checks to see if the proper protocol for this connection has already been determined (cached). If so, the request is passed to the specified protocol. If not, the request is passed to the first protocol listed in the Network Provider Order list and the protocol that accepts the request is then cached with the host name or IP address. This caching makes future access to this host faster. (For more information about the Network Provider Order list, see Technical Note 1813.)
The problem arises when the host and workstation share multiple network protocols in common, such as NFS and SMB. If one of the protocols is cached with the remote host name or IP address, and the other protocol attempts to make a connection to that host, an error message or the hour glass may display. This association between client and resource is cached for about 15 minutes and then purged.
Solution
To avoid the symptoms outlined in this technical note, do not enable both NFS and SMB on the same server.
Version 12.0 or higher
If you are running Reflection NFS Client 12.0 or higher, there are additional workarounds that may help to solve this problem. For more information, please contact Attachmate Technical Support, http://support.attachmate.com/contact/.
