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.

The DirectAccess connection is lost on a computer that is running Windows 7 or Windows Server 2008 R2 that has an IPv6 address


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You have a computer that is running Windows 7 or Windows Server 2008 R2.
  • The computer has a native IPv6 address.
  • The computer is also configured as a DirectAccess client to use the IP over HTTPS (IP-HTTPS) protocol to access an intranet network.

    Note When the IP-HTTPS protocol is set up, an IP-HTTPS adapter is installed on the computer.
  • A network policy change occurs that changes the DirectAccess settings on the computer.
In this scenario, the IP-HTTPS adapter is uninstalled. Therefore, you cannot access the intranet network through the IP-HTTPS protocol.


For example, in a home network, you have a computer that is connected to a router that configures and routes IPv6 addresses. You use this computer as a DirectAccess client to connect to a company network. However, the DirectAccess server is not configured to use IPv6 addresses. Therefore, the computer uses the IP-HTTPS protocol to access the company network. Then, the DirectAccess settings on this computer are updated by a Group Policy. In this example, the connection to the company network is lost.

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

Prerequisites

To apply this hotfix, your computer must be running Windows 7 or 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 MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2 and 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.20614498,68811-Jan-201007:04x86
Iphlpsvcmigplugin.dll6.1.7600.1638551,20014-Jul-200901:15x86
For all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Iphlpsvc.dll6.1.7600.20614568,32011-Jan-201007:54x64
Iphlpsvcmigplugin.dll6.1.7600.1638560,41614-Jul-200901:41x64

↑ 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 the DirectAccess feature and the IP-HTTPS protocol, visit the following Microsoft Web sites: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 nameUpdate.mum
File versionNot applicable
File size1,459
Date (UTC)12-Jan-2010
Time (UTC)00:11
PlatformNot applicable
File nameX86_9a64391a08b13848c41480588d16668e_31bf3856ad364e35_6.1.7600.20614_none_1ee79c9e5fdd05fb.manifest
File versionNot applicable
File size716
Date (UTC)12-Jan-2010
Time (UTC)00:11
PlatformNot applicable
File nameX86_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.20614_none_128db8b6f693be41.manifest
File versionNot applicable
File size131,037
Date (UTC)12-Jan-2010
Time (UTC)00:14
PlatformNot applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_4aeb35090ee20dc38350d5fcafeab317_31bf3856ad364e35_6.1.7600.20614_none_2f0dccf8fc93d5cd.manifest
File versionNot applicable
File size720
Date (UTC)12-Jan-2010
Time (UTC)00:11
PlatformNot applicable
File nameAmd64_563f90d89b3289bc8c82337796c0e956_31bf3856ad364e35_6.1.7600.20614_none_6650452120f536cb.manifest
File versionNot applicable
File size720
Date (UTC)12-Jan-2010
Time (UTC)00:11
PlatformNot applicable
File nameAmd64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.20614_none_6eac543aaef12f77.manifest
File versionNot applicable
File size131,043
Date (UTC)12-Jan-2010
Time (UTC)00:11
PlatformNot applicable
File nameUpdate.mum
File versionNot applicable
File size1,689
Date (UTC)12-Jan-2010
Time (UTC)00:11
PlatformNot applicable
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.20614_none_7900fe8ce351f172.manifest
File versionNot applicable
File size123,749
Date (UTC)11-Jan-2010
Time (UTC)07:20
PlatformNot applicable

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 979373
Revision : 4
Created on : 9/18/2018
Published on : 9/18/2018
Exists online : False
Views : 202