Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

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


View products that this article applies to.

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.

↑ Back to the top


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.

↑ Back to the top


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
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 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 files that apply to a specific product, SR_Level (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    0.16xxx
    Windows 7 RTMGDR
    6.1.760
    0.21xxx
    Windows 7RTMLDR
    6.1.760
    1.22xxx
    Windows 7 SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, critical issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • 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 7" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintaining the state of the updated component. 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
File nameFile versionFile sizeDateTimePlatform
Iphlpsvc.dll6.1.7600.21421500,73610-Jan-201304:41x86
Iphlpsvcmigplugin.dll6.1.7600.1638551,20014-Jul-200901:15x86
Iphlpsvc.dll6.1.7601.22214502,27210-Jan-201304:47x86
Iphlpsvcmigplugin.dll6.1.7601.2221451,20010-Jan-201304:47x86
Netcorehc.dll6.1.7601.22214175,10410-Jan-201304:49x86
For all supported x64-based versions of Windows 7
File nameFile versionFile sizeDateTimePlatform
Iphlpsvc.dll6.1.7600.21421982,52810-Jan-201304:39IA-64
Iphlpsvcmigplugin.dll6.1.7600.16385133,63214-Jul-200901:46IA-64
Iphlpsvc.dll6.1.7601.22214985,08810-Jan-201304:36IA-64
Iphlpsvcmigplugin.dll6.1.7601.22214133,12010-Jan-201304:36IA-64
Netcorehc.dll6.1.7601.22214478,72010-Jan-201304:37IA-64
Iphlpsvcmigplugin.dll6.1.7600.2142151,20010-Jan-201304:41x86
Iphlpsvcmigplugin.dll6.1.7601.2221451,20010-Jan-201304:47x86
Netcorehc.dll6.1.7601.22214175,10410-Jan-201304:49x86

↑ Back to the top


Status

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

↑ Back to the top


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

Additional file information for Windows 7

Additional files for all supported x86-based versions of Windows 7
File nameX86_ac8d3b7538543469337822e31d37425a_31bf3856ad364e35_6.1.7601.22214_none_074b3393a54333d4.manifest
File versionNot applicable
File size1,068
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameX86_bf0dec236a5f52059254367e9e90047b_31bf3856ad364e35_6.1.7601.22214_none_fbc949b7c95e9527.manifest
File versionNot applicable
File size716
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameX86_df2516e4856f5d56d6eaa20405373946_31bf3856ad364e35_6.1.7600.21421_none_f5d23401171d3b7d.manifest
File versionNot applicable
File size716
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameX86_fff45db1cd76e59dfa8b289eca123ba1_31bf3856ad364e35_6.1.7601.22214_none_6b8fd0b9a28f530d.manifest
File versionNot applicable
File size708
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameX86_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.21421_none_127fcd58f69ead80.manifest
File versionNot applicable
File size131,037
Date (UTC)10-Jan-2013
Time (UTC)10:19
PlatformNot applicable
File nameX86_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.22214_none_1473fb28f3ba4980.manifest
File versionNot applicable
File size126,735
Date (UTC)10-Jan-2013
Time (UTC)05:42
PlatformNot applicable
File nameX86_microsoft-windows-netcorehelperclasses_31bf3856ad364e35_6.1.7601.22214_none_e4b9264df4e19dc6.manifest
File versionNot applicable
File size52,774
Date (UTC)10-Jan-2013
Time (UTC)05:48
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7
File nameAmd64_19aa8528cdf3086b63b955df55e8264e_31bf3856ad364e35_6.1.7600.21421_none_05f7c1ffd070347c.manifest
File versionNot applicable
File size720
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameAmd64_34089622e49e939ff6ac4ffad42c7a90_31bf3856ad364e35_6.1.7601.22214_none_6c7623fce8a01c2e.manifest
File versionNot applicable
File size720
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameAmd64_38e429ca35f8d166f57417ad251baf10_31bf3856ad364e35_6.1.7601.22214_none_5af596c8adf86fb2.manifest
File versionNot applicable
File size1,064
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameAmd64_7a57c8679b477dcfc3ba792c07b4513f_31bf3856ad364e35_6.1.7601.22214_none_21ec00a9b1766673.manifest
File versionNot applicable
File size1,082
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameAmd64_af31a6793854988d84df50971b7eff6c_31bf3856ad364e35_6.1.7601.22214_none_c509e37cea977df7.manifest
File versionNot applicable
File size1,426
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameAmd64_e0826a42d2bea16e74c80cd05a5162aa_31bf3856ad364e35_6.1.7600.21421_none_ea5600b0d93fc196.manifest
File versionNot applicable
File size1,082
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameAmd64_ed6b584ddc720f41e86c8500f3c634f4_31bf3856ad364e35_6.1.7600.21421_none_351b0cc7f68042c8.manifest
File versionNot applicable
File size720
Date (UTC)10-Jan-2013
Time (UTC)10:16
PlatformNot applicable
File nameAmd64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.21421_none_6e9e68dcaefc1eb6.manifest
File versionNot applicable
File size131,043
Date (UTC)10-Jan-2013
Time (UTC)10:22
PlatformNot applicable
File nameAmd64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.22214_none_709296acac17bab6.manifest
File versionNot applicable
File size126,741
Date (UTC)10-Jan-2013
Time (UTC)06:21
PlatformNot applicable
File nameAmd64_microsoft-windows-netcorehelperclasses_31bf3856ad364e35_6.1.7601.22214_none_40d7c1d1ad3f0efc.manifest
File versionNot applicable
File size52,778
Date (UTC)10-Jan-2013
Time (UTC)06:30
PlatformNot applicable
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.21421_none_78f3132ee35ce0b1.manifest
File versionNot applicable
File size123,749
Date (UTC)10-Jan-2013
Time (UTC)05:26
PlatformNot applicable
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.22214_none_7ae740fee0787cb1.manifest
File versionNot applicable
File size123,749
Date (UTC)10-Jan-2013
Time (UTC)05:28
PlatformNot applicable
File nameX86_microsoft-windows-netcorehelperclasses_31bf3856ad364e35_6.1.7601.22214_none_e4b9264df4e19dc6.manifest
File versionNot applicable
File size52,774
Date (UTC)10-Jan-2013
Time (UTC)05:48
PlatformNot applicable

↑ Back to the top


Keywords: kb, kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseadvanced

↑ Back to the top

Article Info
Article ID : 2796313
Revision : 1
Created on : 1/7/2017
Published on : 2/13/2013
Exists online : False
Views : 138