FIX: IEHost Makes Calls Back to Port 80 When Internet Explorer Is Bound to a Port Other Than Port 80

This article has been archived. It is offered "as is" and will no longer be updated.
When a managed component is hosted in Microsoft Internet Explorer on a site that is bound to a port other than port 80, the Internet Explorer runtime host (IEHost.dll) makes inappropriate calls back to port 80 at the same site. These calls cause client delays and unacceptable traffic on the server that hosts the port 80 traffic.
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next .NET Framework 1.1 service pack that contains this hotfix.

To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services telephone numbers and information about support costs, visit the following Microsoft Web site:Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.

The English version of this hotfix has the file attributes (or later) 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 tool in Control Panel.
   Date         Time   Version       Size    File name   ----------------------------------------------------   23-Aug-2003  00:37  1.1.4322.936  32,768  Iehost.dll
Microsoft has confirmed that this is a problem in the Microsoft products that are listed at the beginning of this article.

Article ID: 827558 - Last Review: 01/17/2015 05:22:04 - Revision: 1.4

Microsoft .NET Framework 1.1

  • kbnosurvey kbarchive kbhotfixserver kbqfe kbqfe kbnetframe100presp3fix kbfix kbbug KB827558