Microsoft KB Archive Search

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.

  1. Home
  2. A hotfix is available that addresses some issues with the DirectAccess feature in Windows 7 Beta

A hotfix is available that addresses some issues with the DirectAccess feature in Windows 7 Beta

View products that this article applies to.

Beta Information

This article discusses a beta release of a Microsoft product. The information in this article is provided as-is and is subject to change without notice.

No formal product support is available from Microsoft for this beta product. For information about how to obtain support for a beta release, see the documentation that is included with the beta product files, or check the Web location where you downloaded the release.

Important This hotfix is intended for installation on systems that are running Windows 7 Beta only, do not try to install on Windows 7 RC or any released versions of Windows 7.

↑ Back to the top

Symptoms

A hotfix is available that addresses the following issues with the DirectAccess feature in Windows 7 Beta.

Issue 1

When you try to connect a DirectAccess client to a Windows 7 Beta-based DirectAccess server, the connection fails and you receive the following error message:
13888(ERROR_IPSEC_IKE_UNEXPECTED_MESSAGE_ID)
Received unexpected message ID.

Issue 2

The IP-HTTPS tunnel adapter does not start to work automatically when Teredo connections are disabled. Therefore, connectivity is lost in domain networks and for computers that incorrectly identify themselves as in a managed network.

Issue 3

Both Teredo connections and IP-HTTPS connections are present at the same time. If you restart the IP Helper service (Iphlpsvc), this issue may disappear. However, restarting the service does not always work.

Issue 4

Teredo connections intermittently stop working.

↑ Back to the top

Cause

Cause of Issue 1

This issue occurs when the message identifiers between the client and the server are not synchronized. This occurs because of network latency or the Authentication Identifier was deleted incorrectly.

Cause of Issue 3

This issue occurs because IP-HTTPS checksums for Neighbor Discovery Packets are incorrect and IP-HTTPS cannot add mapping table entries after duplicate addresses are detected.

Cause of Issue 4

The issue occurs when Teredo ICMPV6 Echo Replies are dropped by multiple active firewall profiles (MAFP) on the Windows 7 Beta-based DirectAccess Server.

↑ 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 this specific problem.

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, submit a request to 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:
http://support.microsoft.com/contactus/?ws=support
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

No prerequisites are required.

Restart requirement

You must 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 7 Beta, x86-based versions
File nameFile versionFile sizeDateTimePlatform
Iphlpsvc.dll6.1.7000.4114431,61630-Jan-200922:46x86
Tunnel.sys6.1.7000.411477,31230-Jan-200922:45x86
Bfe.dll6.1.7000.4114485,88830-Jan-200923:57x86
Fwpkclnt.sys6.1.7000.4114185,84031-Jan-200900:07x86
Fwpuclnt.dll6.1.7000.4114216,57630-Jan-200923:58x86
Ikeext.dll6.1.7000.4114656,38430-Jan-200923:59x86
Networksecurity-ppdlic.xrm-msNot Applicable3,02831-Jan-200900:15Not Applicable
Nshwfp.dll6.1.7000.4114648,19230-Jan-200922:45x86
Wfp.mofNot Applicable82214-Nov-200819:33Not Applicable
Tcpip.sys6.1.7000.41141,212,38431-Jan-200900:09x86
Windows 7 Beta, x64-based versions
File nameFile versionFile sizeDateTimePlatform
Iphlpsvc.dll6.1.7000.4114490,49631-Jan-200904:06x64
Tunnel.sys6.1.7000.411493,69630-Jan-200923:22x64
Bfe.dll6.1.7000.4114692,22431-Jan-200904:05x64
Fwpkclnt.sys6.1.7000.4114283,10431-Jan-200904:13x64
Fwpuclnt.dll6.1.7000.4114321,53631-Jan-200904:06x64
Ikeext.dll6.1.7000.4114830,97631-Jan-200904:06x64
Networksecurity-ppdlic.xrm-msNot Applicable3,02831-Jan-200904:24Not Applicable
Nshwfp.dll6.1.7000.4114821,24831-Jan-200904:09x64
Wfp.mofNot Applicable82214-Nov-200821:00Not Applicable
Tcpip.sys6.1.7000.41141,804,25631-Jan-200904:16x64
Fwpuclnt.dll6.1.7000.4114216,57630-Jan-200923:58x86
Nshwfp.dll6.1.7000.4114648,19230-Jan-200922:45x86
Wfp.mofNot Applicable82214-Nov-200819:33Not Applicable
Windows 7 Beta, Itanium-based versions
File nameFile versionFile sizeDateTimePlatform
Iphlpsvc.dll6.1.7000.4114847,87231-Jan-200901:29IA-64
Tunnel.sys6.1.7000.4114205,82430-Jan-200922:34IA-64
Bfe.dll6.1.7000.41141,054,72031-Jan-200901:27IA-64
Fwpkclnt.sys6.1.7000.4114468,97631-Jan-200901:40IA-64
Fwpuclnt.dll6.1.7000.4114568,32031-Jan-200901:28IA-64
Ikeext.dll6.1.7000.41141,431,04031-Jan-200901:29IA-64
Networksecurity-ppdlic.xrm-msNot Applicable3,02831-Jan-200901:47Not Applicable
Nshwfp.dll6.1.7000.41141,098,24031-Jan-200901:30IA-64
Wfp.mofNot Applicable82214-Nov-200820:55Not Applicable
Tcpip.sys6.1.7000.41143,536,36831-Jan-200901:43IA-64
Fwpuclnt.dll6.1.7000.4114216,57630-Jan-200923:58x86
Nshwfp.dll6.1.7000.4114648,19230-Jan-200922:45x86
Wfp.mofNot Applicable82214-Nov-200819:33Not 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

↑ Back to the top

Keywords: kbqfe, kbhotfixserver, kbfix, kbautohotfix, kbsurveynew, kbexpertiseinter, kb, kbbug

↑ Back to the top

Article Info
Article ID : 967186
Revision : 3
Created on : 9/25/2018
Published on : 9/25/2018
Exists online : False
Views : 190