Error message when a VPN client that is running Windows Vista or Windows Server 2008 is remotely managed: "Computer \\ComputerName cannot be managed. The network path was not found"

Consider the following scenario:

• On a Windows Vista-based or Windows Server 2008-based client computer, you disable NetBIOS over TCP/IP (NetBT).
• You establish a virtual private networking (VPN) connection to a VPN server in your corporate network.

In this scenario, a corporate IT professional inside your corporate network cannot remotely manage the client computer from the computers behind the VPN gateway.

For example, when an IT professional whose computer is behind the VPN gateway tries to connect to the client by using the "Connect to another computer" feature in Computer Management, the connection fails. Additionally, the IT professional receives the following error message: Moreover, any network functionality that depends on SMB connectivity fails. For example, you cannot access the SMB shares of the remote VPN client when this problem occurs.

This issue occurs because the Lanmanserver service on the Windows Vista VPN client or on the Windows Server 2008 VPN client does not listen on TCP port 445. Because NetBIOS over TCPIP is disabled, the Lanmanserver service also does not listen on TCP port 139. Therefore, you cannot make any server message block (SMB) connections to a Windows Vista or Server 2008 VPN client remotely. This makes any functionality that depends on SMB connectivity fail, such as share access or named pipe access.

Hotfix information

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 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.

Important Windows Vista and Windows Server 2008 hotfixes are included in the same packages. However, only one of these products may be listed on the �Hotfix Request� page. To request the hotfix package that applies to both Windows Vista and Windows Server 2008, just select the product that is listed on the page.

Prerequisites

To apply this hotfix, you must have Windows Server 2008 or Windows Vista Service Pack 1 (SP1) installed on the computer.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace any other previously released hotfixes.

Registry information

To use this hotfix, you do not have to make any changes to the registry.

File information

The 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.

For all supported x86-based versions of Windows Server 2008 and Windows Vista

For all supported x64-based versions of Windows Server 2008 and Windows Vista

For all supported Itanium-based versions of Windows Server 2008

To work around the issue, enable NetBIOS over TCP/IP on the Windows Vista or Windows Server 2008 VPN clients.

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

For more information about NetBT, visit the following Microsoft Web sites:For more information about Lanmanserver, visit the following Microsoft Web site: For more information, click the following article number to view the article in the Microsoft Knowledge Base:

Additional file information for Windows Vista and Windows Server 2008

Additional files for all supported x86-based versions of Windows Vista and Windows Server 2008

Additional files for all supported x64-based versions of Windows Vista and Windows Server 2008

Additional files for all supported Itanium-based versions of Windows Server 2008