Consider the following scenario:
- A client computer is running the Network File System (NFS) client and the Server Message Block (SMB) client.
- A server is running the SMB server only.
- The client computer and the server are not members of a domain, or they are members of different domains that do not have a trust relationship.
- You log on to the client computer. However, your user name is not known on the server.
- You try to connect to the server from the client computer by using the \\servername path instead of the \\servername\sharename path.
Error 67: The network name cannot be found.
This problem occurs because of a problem in the NFS client redirector component of the Client for NFS service.
Hotfix informationA supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.
If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.
Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.
PrerequisitesYou must have Microsoft Windows Services for UNIX 3.5 installed to apply this hotfix. Additionally, the computer must be running the Client for NFS service.
Restart requirementYou must restart your computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|File name||File version||File size||Date||Time||Platform|
To work around this problem, use one of the following methods:
- Before you use the \\servername path to connect to the server, authenticate the server by running the following command at a command prompt: net use \\servername\ipc$ /user:servername\username
- Remove the NFS client.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
If the NFS client is not installed or the NFS driver is disabled in the registry, you receive an authentication dialog box.For more information about how to disable the NFS driver in the registry, click the following article number to view the article in the Microsoft Knowledge Base:
816071 How to temporarily deactivate the kernel mode filter driver in WindowsFor more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:
824684 Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 917796 - Last Review: Feb 16, 2017 - Revision: 2
Microsoft Windows Services for UNIX 3.5