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.

IP-HTTPS clients may disconnect from Windows Server 2008 R2-based web servers intermittently after two minutes of idle time


View products that this article applies to.

Symptoms

When a computer connects to a Windows Server 2008 R2-based web server by using the IP over HTTPS (IP-HTTPS) protocol, the connection may be lost after two minutes of idle time.

When this issue occurs, applications that rely on the IP-HTTPS connection do not work correctly. For example, you deploy a Group Policy object (GPO) to remote clients in a domain that has Microsoft Forefront Unified Access Gateway (UAG) DirectAccess. In this scenario, the clients that use the IP-HTTPS protocol might not obtain the GPO because IP-HTTPS connection times out.

↑ Back to the top


Cause

This issue occurs because an IP-HTTPS connection times out after two minutes of idle time.

↑ Back to the top


Resolution

To resolve this issue, apply the following hotfix on the web server. After you install this hotfix, the time-out for IP-HTTPS connections is changed to 30 minutes (1800 seconds).

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: 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 Server 2008 R2
  • Windows Server 2008 R2 Service Pack 1 (SP1)
For more information about how to obtain a 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

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows
To change the EntityBody timer to a value other than 30 minutes, follow these steps:
  1. Click Startstart button , type regedit in the Start Search box, and then press ENTER.
  2. Locate and then click the following registry key:
    HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\IPHLPSVC\Parameters\IPHTTPS\IPHTTPSInterface
  3. Click Edit, point to New, and then click DWORD Value.
  4. Type HttpEntityBodyTimeout, and then press ENTER.
  5. Click Edit, and then click Modify.
  6. Type a value that is from 120-7200.
Note The HttpEntityBodyTimeout entry is for the EntityBody timer and is in units of seconds.

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 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, 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 Server 2008 R2RTMGDR
    6.1.760
    0.
    20xxx
    Windows Server 2008 R2RTMLDR
    6.1.760
    1.
    21xxx
    Windows Server 2008 R2SP1LDR
  • 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" 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 x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Iphlpsvc.dll6.1.7600.20967569,34414-May-201107:34x64
Iphlpsvcmigplugin.dll6.1.7600.1638560,41614-Jul-200901:41x64
Iphlpsvc.dll6.1.7601.21728570,36814-May-201107:11x64
Iphlpsvcmigplugin.dll6.1.7600.1638560,41614-Jul-200901:41x64
Iphlpsvcmigplugin.dll6.1.7600.2096751,20014-May-201106:32x86
Iphlpsvcmigplugin.dll6.1.7601.2172851,20014-May-201107:40x86
For all supported IA-64based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Iphlpsvc.dll6.1.7600.20967980,48014-May-201106:19IA-64
Iphlpsvcmigplugin.dll6.1.7600.16385133,63214-Jul-200901:46IA-64
Iphlpsvc.dll6.1.7601.21728982,01614-May-201106:14IA-64
Iphlpsvcmigplugin.dll6.1.7600.16385133,63214-Jul-200901:46IA-64
Iphlpsvcmigplugin.dll6.1.7600.2096751,20014-May-201106:32x86
Iphlpsvcmigplugin.dll6.1.7601.2172851,20014-May-201107:40x86

↑ 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

For more information about the HTTP_TIMEOUT_LIMIT_INFO structure, visit the following MSDN website:
For more information about how to plan for IP-HTTPS, visit the following TechNet website:

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_21cad67c669cae0d59f9ce6e80ae375d_31bf3856ad364e35_6.1.7600.20967_none_9bbfda002648c083.manifest
File versionNot applicable
File size720
Date (UTC)16-May-2011
Time (UTC)11:33
File nameAmd64_2a286f6fb038e892f0fec6210d6d3cd3_31bf3856ad364e35_6.1.7601.21728_none_27309522ce5d6c1c.manifest
File versionNot applicable
File size1,082
Date (UTC)16-May-2011
Time (UTC)11:33
File nameAmd64_47820fe9fd904ea39ffaf100e7a9bb83_31bf3856ad364e35_6.1.7601.21728_none_759810326718e179.manifest
File versionNot applicable
File size720
Date (UTC)16-May-2011
Time (UTC)11:33
File nameAmd64_a649623f4cb924bd358de4f3abf1484a_31bf3856ad364e35_6.1.7601.21728_none_7249e43fd7abc628.manifest
File versionNot applicable
File size720
Date (UTC)16-May-2011
Time (UTC)11:33
File nameAmd64_afcd0d91365138eba675942cf9c5bdf6_31bf3856ad364e35_6.1.7600.20967_none_293761ba1bd79d32.manifest
File versionNot applicable
File size720
Date (UTC)16-May-2011
Time (UTC)11:33
File nameAmd64_b5262876c6a3f9a6c1b7db6d624f2d0e_31bf3856ad364e35_6.1.7600.20967_none_dea595f8013d9d76.manifest
File versionNot applicable
File size1,082
Date (UTC)16-May-2011
Time (UTC)11:33
File nameAmd64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.20967_none_6e794b2eaf16fea6.manifest
File versionNot applicable
File size131,043
Date (UTC)16-May-2011
Time (UTC)11:40
File nameAmd64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.21728_none_708be82eac1c1425.manifest
File versionNot applicable
File size131,043
Date (UTC)16-May-2011
Time (UTC)11:40
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.20967_none_78cdf580e377c0a1.manifest
File versionNot applicable
File size123,749
Date (UTC)14-May-2011
Time (UTC)06:49
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.21728_none_7ae09280e07cd620.manifest
File versionNot applicable
File size123,749
Date (UTC)14-May-2011
Time (UTC)08:03
Additional files for all supported IA-64based versions of Windows Server 2008 R2
File nameIa64_a649623f4cb924bd358de4f3abf1484a_31bf3856ad364e35_6.1.7601.21728_none_162cecb21f4c5dee.manifest
File versionNot applicable
File size719
Date (UTC)16-May-2011
Time (UTC)11:33
File nameIa64_a9d83fabda26cbe2c2829c6f877c89a7_31bf3856ad364e35_6.1.7601.21728_none_8378a02796e2a578.manifest
File versionNot applicable
File size718
Date (UTC)16-May-2011
Time (UTC)11:33
File nameIa64_afcd0d91365138eba675942cf9c5bdf6_31bf3856ad364e35_6.1.7600.20967_none_cd1a6a2c637834f8.manifest
File versionNot applicable
File size719
Date (UTC)16-May-2011
Time (UTC)11:33
File nameIa64_c722d57588f1ca28f3d72af96bdd2ffd_31bf3856ad364e35_6.1.7600.20967_none_14429d00020bada5.manifest
File versionNot applicable
File size718
Date (UTC)16-May-2011
Time (UTC)11:33
File nameIa64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.20967_none_125c53a0f6b7966c.manifest
File versionNot applicable
File size131,040
Date (UTC)16-May-2011
Time (UTC)11:33
File nameIa64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.21728_none_146ef0a0f3bcabeb.manifest
File versionNot applicable
File size131,040
Date (UTC)16-May-2011
Time (UTC)11:33
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7600.20967_none_78cdf580e377c0a1.manifest
File versionNot applicable
File size123,749
Date (UTC)14-May-2011
Time (UTC)06:49
File nameWow64_microsoft-windows-i..oexistencemigration_31bf3856ad364e35_6.1.7601.21728_none_7ae09280e07cd620.manifest
File versionNot applicable
File size123,749
Date (UTC)14-May-2011
Time (UTC)08:03

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2535133
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 224