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.

DirectAccess is used for internal network connections in Windows 7 SP1


View products that this article applies to.

Symptoms

A Windows 7 Service Pack 1 (SP1)-based computer uses DirectAccess to connect to the IPHTTPS address of the DirectAccess Server even though the computer is connected to the internal (domain) network. 

↑ Back to the top


Cause

This problem occurs if the FQDN connection to the DA servers can be resolved in the internal network and if a route exists to the IP address that it resolves to. This problem can also occur if the DA client uses a proxy server that has a route to the DA servers.

Only the IPHTTPS tunnel is connected. The IPSec tunnels are not created inside the IPHTTPS tunnel because the firewall detects a domain profile and because the Connection Security rules do not apply to the domain profile. Although the Windows 7 client did not complete a "full" DA connection, the IPHTTPS tunnel connection still occurs on port 443. Therefore, performance issues may occur on the Direct Access server.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft Support. 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, go to 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 Service Pack 1 (SP1)
See Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2 for more information.

Registry information

To enable this fix, 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 any previously released hotfix.
File information
The English (United States) 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 SP1 file information and 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.

    VersionProductSR_LevelService branch
    6.1.760
    0.
    16xxx
    Windows 7 and Windows Server 2008 R2RTMGDR
    6.1.760
    0.
    20xxx
    Windows 7 and Windows Server 2008 R2RTMLDR
    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, extremely important 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 Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. 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 sizeDateTimeHashes
Iphlpsvc.dll6.1.7601.22670502,78430-Apr-201403:44
Iphlpsvcmigplugin.dll6.1.7601.2212451,20003-Oct-201216:27MD5: B4E967889E5AEDA9D66F12676215EB5D
SHA1: 8F8F7127C580E62E2D0DB2630358491A953383C9
Netcorehc.dll6.1.7601.22124175,10403-Oct-201216:29MD5: 5FF9F07B268E5D5A1C321C3CF5C2CB9B
SHA1: 628E07C4C0569DEC9FD1C64A87190BE3A845931C
For all supported x64-based versions of Windows 7 and Windows Server 2008 R2
File nameFile versionFile sizeDateTimeHashesPlatform
Iphlpsvc.dll6.1.7601.22670572,41630-Apr-201404:10MD5: 3567CAEA927E275A368FFFFD556508C0
SHA1: B49DC87013533502BD159F09B7F7A7D25F9FDD73
x64
Iphlpsvcmigplugin.dll6.1.7601.2215060,41602-Nov-201205:47MD5: 1BC91154A140E63600D0CFE98F6D8540
SHA1: 8CBC8B82CC0E7A28B1A449BA7CBB759C58098A96
x64
Netcorehc.dll6.1.7601.22150246,27202-Nov-201205:49MD5: 2323B40730913438730E53044E2335E8
SHA1: 85ED82BC60D97F61DFF90B9908CDB24878C3B8A6
x64
Iphlpsvcmigplugin.dll6.1.7601.2267051,20030-Apr-201403:44MD5: EEA6151FE48857CFC8200F70D6C4A36D
SHA1: B50B9259D0BC09BA8C516E65B8E64E162648611F
x86
Netcorehc.dll6.1.7601.22150175,10402-Nov-201205:06MD5: 165800F28960D4884A0681DC8B4B7164
SHA1: 707E0E26174EE9B36950A72ECD6514AC4353F780
x86
For all supported IA-64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimeHashesPlatform
Iphlpsvc.dll6.1.7601.22670984,57630-Apr-201403:18MD5: F8A31D5EC7D598965B90CC5F56410131
SHA1: F54E4197A5ADAA18942690511FEFD17D50C32CDE
IA-64
Iphlpsvcmigplugin.dll6.1.7601.22150133,12002-Nov-201204:29MD5: F1E8E8C72CE02852CB777943C5602A33
SHA1: 44408636A1BECE3E0BFC494A8F10C1D9A35D2D16
IA-64
Netcorehc.dll6.1.7601.22150478,72002-Nov-201204:31MD5: DB931638AD4D01FFE35BA24D46EE9F0D
SHA1: 948795804560C5003E3FE3DC788516272B7E5DEA
IA-64
Iphlpsvcmigplugin.dll6.1.7601.2267051,20030-Apr-201403:44MD5: EEA6151FE48857CFC8200F70D6C4A36D
SHA1: B50B9259D0BC09BA8C516E65B8E64E162648611F
x86
Netcorehc.dll6.1.7601.22150175,10402-Nov-201205:06MD5: 165800F28960D4884A0681DC8B4B7164
SHA1: 707E0E26174EE9B36950A72ECD6514AC4353F780
x86

Additional file information

Additional file information for Windows 7

Additional files for all supported x86-based versions of Windows 7
File nameX86_129284d94a209689e3ce2bca660c968b_31bf3856ad364e35_6.1.7601.22670_none_bbfc3a2a3a45776f.manifest
File versionNot Applicable
File size1,068
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameX86_2bcd71ec971cd3e6ff2268836118e73e_31bf3856ad364e35_6.1.7601.22670_none_363e1a4e6ea62409.manifest
File versionNot Applicable
File size708
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameX86_f64377aa72a07e56f965f8f048acd2e2_31bf3856ad364e35_6.1.7601.22670_none_35e42a24cb4f5b60.manifest
File versionNot Applicable
File size716
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameX86_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.22670_none_142f2210f3ee8066.manifest
File versionNot Applicable
File size131,037
Date (UTC)30-Apr-2014
Time (UTC)09:06
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameX86_microsoft-windows-netcorehelperclasses_31bf3856ad364e35_6.1.7601.22670_none_e4744d35f515d4ac.manifest
File versionNot Applicable
File size57,394
Date (UTC)30-Apr-2014
Time (UTC)09:06
SHA-1 hashNot Applicable
MD5 hashNot Applicable
Additional files for all supported x64-based versions of Windows 7 and of Windows Server 2008 R2
File nameAmd64_71fb7dbbe238b56336dffb33414a9d3a_31bf3856ad364e35_6.1.7601.22670_none_a776f475599ee19c.manifest
File versionNot Applicable
File size1,064
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_a73e99616b724422892447aed7be8286_31bf3856ad364e35_6.1.7601.22670_none_3e0fd07869d62acb.manifest
File versionNot Applicable
File size1,082
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_b3926e435a7a4b1d50d87ae174a0d653_31bf3856ad364e35_6.1.7601.22670_none_122c5a7ad27e792b.manifest
File versionNot Applicable
File size720
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_bfbf89dc437092eff913a359ff4dbb08_31bf3856ad364e35_6.1.7601.22670_none_d70afbd231f4af74.manifest
File versionNot Applicable
File size1,426
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.22670_none_704dbd94ac4bf19c.manifest
File versionNot Applicable
File size131,043
Date (UTC)30-Apr-2014
Time (UTC)09:09
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameAmd64_microsoft-windows-netcorehelperclasses_31bf3856ad364e35_6.1.7601.22670_none_4092e8b9ad7345e2.manifest
File versionNot Applicable
File size57,398
Date (UTC)30-Apr-2014
Time (UTC)09:09
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.22670_none_7aa267e6e0acb397.manifest
File versionNot Applicable
File size123,749
Date (UTC)30-Apr-2014
Time (UTC)04:06
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameX86_microsoft-windows-netcorehelperclasses_31bf3856ad364e35_6.1.7601.22670_none_e4744d35f515d4ac.manifest
File versionNot Applicable
File size57,394
Date (UTC)30-Apr-2014
Time (UTC)09:09
SHA-1 hashNot Applicable
MD5 hashNot Applicable
Additional files for all supported IA-64-based versions of Windows Server 2008 R2
File nameIa64_1e01b8f82cf9a35f536de5def0bf423e_31bf3856ad364e35_6.1.7601.22670_none_a05fdcd70398a390.manifest
File versionNot Applicable
File size1,785
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameIa64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.22670_none_1430c606f3ec8962.manifest
File versionNot Applicable
File size131,040
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameIa64_microsoft-windows-netcorehelperclasses_31bf3856ad364e35_6.1.7601.22670_none_e475f12bf513dda8.manifest
File versionNot Applicable
File size57,396
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.22670_none_7aa267e6e0acb397.manifest
File versionNot Applicable
File size123,749
Date (UTC)30-Apr-2014
Time (UTC)04:06
SHA-1 hashNot Applicable
MD5 hashNot Applicable
File nameX86_microsoft-windows-netcorehelperclasses_31bf3856ad364e35_6.1.7601.22670_none_e4744d35f515d4ac.manifest
File versionNot Applicable
File size57,394
Date (UTC)30-Apr-2014
Time (UTC)09:03
SHA-1 hashNot Applicable
MD5 hashNot 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


References

Learn about the terminology that Microsoft uses to describe software updates.

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2951611
Revision : 1
Created on : 1/7/2017
Published on : 6/11/2014
Exists online : False
Views : 144