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.

IPsec connection that uses IKEv2 tunnel mode fails on a computer that is running Windows 7 or Windows Server 2008 R2


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have two computers that are running Windows 7 or Windows Server 2008 R2.
  • Each computer is behind a separate Network Address Translation (NAT) firewall.
  • You connect the computers by using an Internet Protocol Security (IPsec) connection that uses Internet Key Exchange version 2 (IKEv2) tunnel mode.
  • You install the update that is described in Microsoft Knowledge Base (KB) article 2248145 on one of the computers.
In this scenario, the IPsec connection fails. More specifically, no data packets are routed through the IPsec connection, and the IPsec connection is negotiated repeatedly.

↑ Back to the top


Resolution

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 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 one of the following operating systems:
  • Windows 7
  • Windows 7 Service Pack 1 (SP1)
  • Windows Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a Windows 7 or Windows Server 2008 R2 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 use the hotfix in this package, 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 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 files that apply to a specific product, milestone (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
    1.17xxx
    Windows 7 and Windows Server 2008 R2SP1GDR
    6.1.760
    1.21xxx
    Windows 7 and Windows Server 2008 R2SP1LDR
  • 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 and for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are critical 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 sizeDateTime
Bfe.dll6.1.7601.21939496,12809-Mar-201213:49
Fwpuclnt.dll6.1.7601.17514216,57620-Nov-201012:19
Ikeext.dll6.1.7601.21939675,32809-Mar-201213:50
Networksecurity-ppdlic.xrm-msNot applicable3,02809-Mar-201214:11
Nshwfp.dll6.1.7601.21939657,92009-Mar-201213:51
Wfp.mofNot applicable82210-Jun-200921:32
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7601.21939706,56009-Mar-201215:35x64
Fwpuclnt.dll6.1.7601.21939324,09609-Mar-201215:36x64
Ikeext.dll6.1.7601.21939854,52809-Mar-201215:36x64
Networksecurity-ppdlic.xrm-msNot applicable3,02809-Mar-201215:52Not applicable
Nshwfp.dll6.1.7601.21939832,00009-Mar-201215:36x64
Wfp.mofNot applicable82210-Jun-200920:51Not applicable
Fwpuclnt.dll6.1.7601.21939216,57609-Mar-201213:50x86
Nshwfp.dll6.1.7601.21939657,92009-Mar-201213:51x86
Wfp.mofNot applicable82212-Nov-201023:57Not applicable
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Bfe.dll6.1.7601.219391,074,17609-Mar-201213:54IA-64
Fwpuclnt.dll6.1.7601.21939566,27209-Mar-201213:55IA-64
Ikeext.dll6.1.7601.219391,486,84809-Mar-201213:55IA-64
Networksecurity-ppdlic.xrm-msNot applicable3,02809-Mar-201214:11Not applicable
Nshwfp.dll6.1.7601.219391,114,11209-Mar-201213:56IA-64
Wfp.mofNot applicable82210-Jun-200920:57Not applicable
Fwpuclnt.dll6.1.7601.21939216,57609-Mar-201213:50x86
Nshwfp.dll6.1.7601.21939657,92009-Mar-201213:51x86
Wfp.mofNot applicable82212-Nov-201023:57Not applicable

↑ 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 and for Windows Server 2008 R2

Additional files for all supported x86-based versions of Windows 7
File nameX86_20a86d6c24debb129b9d8d613177c98a_31bf3856ad364e35_6.1.7601.21939_none_a2ead1087e612eaa.manifest
File versionNot applicable
File size704
Date (UTC)09-Mar-2012
Time (UTC)20:01
File nameX86_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21939_none_cfa4ddeba1f63ee8.manifest
File versionNot applicable
File size158,847
Date (UTC)09-Mar-2012
Time (UTC)20:04
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_2666cccee9d44abbc79608dede64f461_31bf3856ad364e35_6.1.7601.21939_none_a6a3ac1846156ab1.manifest
File versionNot applicable
File size708
Date (UTC)09-Mar-2012
Time (UTC)20:01
File nameAmd64_76381ea7c449c9436085d7436ac4248d_31bf3856ad364e35_6.1.7601.21939_none_7a53aac6e6dc7c6a.manifest
File versionNot applicable
File size1,058
Date (UTC)09-Mar-2012
Time (UTC)20:01
File nameAmd64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21939_none_2bc3796f5a53b01e.manifest
File versionNot applicable
File size154,831
Date (UTC)09-Mar-2012
Time (UTC)16:01
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21939_none_361823c18eb47219.manifest
File versionNot applicable
File size94,348
Date (UTC)09-Mar-2012
Time (UTC)14:10
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_c760f426708a313f66a559039845bf37_31bf3856ad364e35_6.1.7601.21939_none_e4fa1dc3814c9d44.manifest
File versionNot applicable
File size1,056
Date (UTC)09-Mar-2012
Time (UTC)20:01
File nameIa64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21939_none_cfa681e1a1f447e4.manifest
File versionNot applicable
File size154,828
Date (UTC)09-Mar-2012
Time (UTC)15:15
File nameWow64_microsoft-windows-network-security_31bf3856ad364e35_6.1.7601.21939_none_361823c18eb47219.manifest
File versionNot applicable
File size94,348
Date (UTC)09-Mar-2012
Time (UTC)14:10

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2686921
Revision : 3
Created on : 9/20/2018
Published on : 9/21/2018
Exists online : False
Views : 248