Article ID: 921090
Article Last Modified on 11/15/2007
APPLIES TO
- Microsoft Internet Explorer 6.0, when used with:
- Microsoft Windows Server 2003, Standard Edition (32-bit x86)
- Microsoft Windows Server 2003, Enterprise Edition (32-bit x86)
- Microsoft Windows XP Home Edition
- Microsoft Windows XP Professional
Important This article contains information about how to modify the registry. Make sure to back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base:
256986 Description of the Microsoft Windows registry
SYMPTOMS
You use Microsoft Internet Explorer to view a Web page on a computer that is running Microsoft Windows Server 2003 or Microsoft Windows XP. When you do this, Internet Explorer generates an error message that states that the page cannot be displayed.
CAUSE
This problem may occur if the following conditions are true:
- Internet Explorer uses the connect command to post data, to obtain data, or to set up an HTTPS connection.
- The Web server issues a Secure Sockets Layer (SSL) 3.0 closure alert at the same time that the port is closed on the server.
MORE INFORMATION
The closure alert is sent by the server to Internet Explorer as a zero-byte encrypted packet. However, the complete closure message is sent in two different packets. The server sends only the first packet.
Typically, the first closure alert packet includes the ".AP..." (Ack Push) TCP flags to instruct the program that the SSL 3.0 session is closing. A second packet includes the ".A...F" (Ack Fin) TCP flags to instruct the TCP layer to close the port on the client computer.
Because the RESET and FIN TCP flags are not set when the closure alert arrives in the first packet, the Wininet.dll process on the client computer that is running Internet Explorer cannot verify that the packet is not program data. Therefore, the keep-alive port is left open on the client computer until the next Socket Receive call is sent by the client computer. Because Internet Explorer has two keep-alive ports that are open to the server, the retry count is equal to two on the client computer.
The Socket Receive call occurs on the client after it tries to send data on the first keep-alive port. When the Socket Receive call occurs, the SSL 3.0 closure alert is processed. Then, the TCP closure is processed on the client. This step closes the first keep-alive port.
Because the retry count is now one, the client tries to resend data on the second keep-alive port. However, this port has also been closed on the server. When the Socket Receive call occurs on the client, the SSL 3.0 closure alert is processed. Then, the TCP closure is processed. The retry count is now zero. Therefore, the error message is generated that states that the page cannot be displayed.
RESOLUTION
Windows Server 2003 hotfix information
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
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.
| File name | File version | File size | Date | Time | Platform | SP requirement | Service branch |
|---|---|---|---|---|---|---|---|
| Wininet.dll | 6.0.3790.549 | 628,736 | 22-Jun-2006 | 11:19 | x86 | None | RTMQFE |
| Wininet.dll | 6.0.3790.2731 | 665,600 | 22-Jun-2006 | 12:12 | x86 | SP1 | SP1QFE |
How to enable the hotfix
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
After you install this hotfix, you must modify the registry to enable the hotfix. To enable the hotfix, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then right-click the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl
- Point to New, and then click Key.
- Type FEATURE_HANDLE_SSL_CLOSE_NOTIFY_KB921090, and then press ENTER to name the new key.
- Right-click FEATURE_HANDLE_SSL_CLOSE_NOTIFY_KB921090, point to New, and then click DWORD Value.
- Type iexplore.exe, and then press ENTER to name the value.
- Right-click iexplore.exe, and then click Modify.
- In the Value data box, type 00000001, and then click OK.
- Exit Registry Editor.
Windows XP hotfix information
A supported hotfix is now 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. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next service pack that contains this hotfix.
To resolve this problem, submit a request to Microsoft Online Customer Services to obtain the hotfix. To submit an online request to obtain the hotfix, visit the following Microsoft Web site:
Note If additional issues occur or 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. To create a separate service request, visit the following Microsoft Web site:
Prerequisites
To install this hotfix, you must install Windows XP Service Pack 2.
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.
| File name | File version | File size | Date | Time | Platform |
|---|---|---|---|---|---|
| Wininet.dll | 6.0.2900.2936 | 664,576 | 22-Jun-2006 | 10:41 | x86 |
How to enable the hotfix
Warning Serious problems might occur if you modify the registry incorrectly by using Registry Editor or by using another method. These problems might require that you reinstall your operating system. Microsoft cannot guarantee that these problems can be solved. Modify the registry at your own risk.
After you install this hotfix, you must modify the registry to enable the hotfix. To enable the hotfix, follow these steps:
- Click Start, click Run, type regedit, and then click OK.
- Locate and then right-click the following subkey:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Internet Explorer\Main\FeatureControl
- Point to New, and then click Key.
- Type FEATURE_HANDLE_SSL_CLOSE_NOTIFY_KB921090, and then press ENTER to name the new key.
- Right-click FEATURE_HANDLE_SSL_CLOSE_NOTIFY_KB921090, point to New, and then click DWORD Value.
- Type iexplore.exe, and then press ENTER to name the value.
- Right-click iexplore.exe, and then click Modify.
- In the Value data box, type 00000001, and then click OK.
- Exit Registry Editor.
WORKAROUND
To work around this problem, use one of the following methods:
- Disable SSL 3.0 closure alerts at the server.
- Change the keep-alive time-out setting from 30 seconds to 300 seconds.
For more information about how to configure the keep-alive time-out setting, click the following article number to view the article in the Microsoft Knowledge Base:
183110 WinInet limits connections per server
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
For more information, 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 query words: IE SSL 3.0 305217
Keywords: kbwinserv2003presp2fix kbwinxppresp3fix kbie501fix kbbug kbfix kbhotfixserver kbqfe kbpubtypekc KB921090
