Multiple users log on to a computer that is running Windows Server 2008 R2 or Windows 7. These users use this computer to access a remote server that shares files and printers by using the Server Message Block (SMB) protocol.
You log on to the computer to access the server.
The connection between the computer and the server is timed out after the connection stays in an inactive status for a long time. Or, the connection fails because of a network error.
You try to reestablish the connection from the computer by using the name of the server.
In this scenario, you may be unable to reestablish the connection. Additionally, you receive the following error message:
Error code: 0x80070035 The network path was not found.
When this issue occurs, you can still access the server by using another naming convention of the server.
For example, you can access the server by using the fully qualified domain name (FQDN). Or, you can use the IP address if you cannot access the server by using the short name.
If you collect a network trace when you try to access the server, you find that there is no traffic to the server.
This issue occurs because of an error in the Mrxsmb10.sys driver.
The Mrxsmb10.sys driver specifies a logon ID the first time that a connection is established to a remote server that shares files and printers by using the SMB protocol. The logon ID and the name of the server are saved in a server entry of the SMB Redirector. For example, the logon ID and one of the following server names that you use to establish the connection are saved:
However, the Mrxsmb10.sys driver does not update the logon ID after the user who used the logon ID logs off. Therefore, any attempt to use the name from the first connection fails regardless of the user name.
A 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 the problem described in this article. 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.
To apply this hotfix, you must be running Windows 7 or Windows Server 2008 R2.
To use the hotfix in this package, you do not have to make any changes to the registry.
You may have to restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace a previously released hotfix.
The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows 7 and Windows Server 2008 R2 file information notes
Important Windows 7 hotfixes and Windows Server 2008 R2 hotfixes are included in the same packages. However, hotfixes on the Hotfix Request page are listed under both operating systems. To request the hotfix package that applies to one or both operating systems, select the hotfix that is listed under "Windows 7/Windows Server 2008 R2" on the page. Always refer to the "Applies To" section in articles to determine the actual operating system that each hotfix applies to.
The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and for Windows 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x86-based versions of Windows 7
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
For all supported IA-64-based versions of Windows Server 2008 R2
To work around this issue, restart the computer.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
For 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
Additional file information
Additional file information for Windows 7 and for Windows Server 2008 R2
Additional files for all supported x86-based versions of Windows 7