Long reconnection time after a DirectAccess server disconnects a Windows 7-based DirectAccess client

Symptoms

Consider the following scenario:
  • You configure a DirectAccess server together with the support of Windows 7-based clients on a server that is running Windows Server 2012 in a network environment. 
  • You have a Windows 7-based DirectAccess client that is connected to the server by using the IP over HTTPS (IP-HTTPS) protocol.

    Note When you set up the IP-HTTPS protocol, Windows installs an IP-HTTPS adapter on the computer.
  • The DirectAccess client is also connected to a corporate network by using a virtual private network (VPN) connection.
  • You disconnect the VPN connection on the DirectAccess client.
In this scenario, the client requires up to 15 minutes to automatically reconnect to the DirectAccess server after the VPN connection is disconnected. Additionally, the IP-HTTPS adapter state is displayed as disconnected during this time.

Cause

This issue occurs because the IP-HTTPS protocol cannot manage eligible interfaces if you disconnect or connect the VPN interface. Therefore, the Network Change Notification handler is missing. Additionally, this issue occurs because the Internet connectivity timer is not reset when the VPN connection is disconnected.

Resolution

Hotfix information

To resolve this issue, install the hotfix on the Windows 7-based DirectAccess client.

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

Prerequisites

To apply this hotfix, you must be running Windows 7 or Windows 7 Service Pack 1 (SP1).

For more information about how to obtain a Windows 7 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

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

Restart requirement

You must restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.
File information

Status

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

More Information

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
Properties

Article ID: 2796313 - Last Review: Feb 13, 2013 - Revision: 1

Feedback