You may be not able to use a VPN connection again on a computer that is running Windows Server 2008 or Windows Vista if you log off the computer without disconnecting the VPN connection

Consider the following scenario. On a computer that is running Windows Server 2008 or Windows Vista, you use Connection Manager to create a VPN connection to a Routing and Remote Access Service server. The VPN connection is created successfully. Then, you log off the computer without disconnecting the VPN connection. In this scenario, when you log on to the system again and open the Network Connections window of Connection Manager, you may find that the status for the VPN connection shows "Disconnecting�." Therefore, you may be not able to use this VPN connection again without restarting the computer.

Notes

• If you check the VPN connection in the Routing and Remote Access console on the server side, you notice that the connection is disconnected.
• You can still manually create a VPN connection to the Routing and Remote Access server without using Connection Manager.
• To use the VPN connection in Connection Manager again, you must restart the computer.

This problem occurs because of an error in Connection Manager. When the user logs off the computer, the Connection Manager Monitor receives a notification. If there are connections that were created by Connection Manager that are still active, the Connection Manager Monitor starts a disconnect operation on all such connections. If the user logoff process causes the Connection Manager Monitor to exit while the Connection Manager Monitor is still disconnecting these connections, the connections are left in an inconsistent state.

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

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

No prerequisites are required.

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

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.

Windows Vista and Windows Server 2008 file information notes

• The files that apply to a specific product, milestone (RTM, SPn) can be identified by examining the file version numbers as shown in the following table:

  Version	Product	Milestone	Service branch
  6.0.6000.20xxx	Windows	RTM	LDR
  6.0.6001.22xxx	Windows Server 2008 SP1 and Windows Vista SP1	SP1	LDR

• Service Pack 1 is integrated into Windows Server 2008. Therefore, RTM milestone files apply only to Windows Vista. RTM milestone files have a 6.0.0000.xxxxxx version number.
• The MANIFEST (.manifest) files and MUM (.mum) files that are installed for each environment are listed separately. MUM and MANIFEST files and their associated security catalog (.cat) files are critical to maintaining the state of the updated component. The security catalog files are signed with a Microsoft digital signature. The attributes of these files are not listed.

All supported x86-based versions of Windows Server 2008 and of Windows Vista

All supported x64-based versions of Windows Server 2008 and of Windows Vista

All supported IA-64-based versions of Windows Server 2008

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

For more information about Connection Manager, visit the following Microsoft Web sites:

Additional file information for Windows Server 2008 and for Windows Vista

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

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

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