SYMPTOMS
You may notice that Microsoft Internet Information Services (IIS) 6.0 incorrectly binds to ports when IP addresses are added to the IP inclusion list. Consider the following scenario:
- The Web server has two IP addresses. These IP addresses are bound to an installed network card in Internet Information Services Manager (IISM) in IIS 6.0. In this example, the two IP addresses are 10.10.10.2 and 10.10.10.3.
- There are two Web sites in IIS 6.0. Web site 1 is bound to 10.10.10.2:80 for HTTP traffic. Web site 1 is also bound to 10.10.10.2:443 for SSL traffic. Web site 2 is bound to 10.10.10.3:80 for HTTP traffic only.
In this scenario, when you use the
netstat command to view the ports on which the computer is listening, you may notice that IIS 6.0 is bound to port 80 and to port 443 on both IP addresses.
This issue occurs when either of the following conditions is true:
- Both IP addresses have been added to the IP inclusion list.
- Both port 80 and port 443 are bound on 0.0.0.0.
You cannot resolve this problem by setting the IIS 6.0
DisableSocketPooling property to True.
RESOLUTION
Hotfix information
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 Microsoft Windows Server 2003 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.
Prerequisites
You must have Microsoft Windows Server 2003 Service Pack 1 (SP1) installed to apply this hotfix.
Restart requirement
You must restart the computer after you apply this hotfix.
Hotfix replacement information
This hotfix does not replace any other hotfixes.
Registry information
You must create a registry key to enable this hotfix. To do this, follow these steps:
- Apply this hotfix.
- Click Start, click Run, type regedit, and then click OK.
- Locate and then click the following registry key:
HKLM\SYSTEM\CurrentControlSet\Services\HTTP\Parameters
- Right-click Parameters, point to New, and then click DWORD Value.
- Type DisableEndpointSharing, and then press ENTER.
- Right-click DisableEndpointSharing, click Modify, type 1 in the Value data box, and then click OK.
- Click Start, click Run, type cmd, and then click OK.
- At the command prompt, type NET STOP HTTP /y, and then press ENTER.
- At the command prompt, type iisreset /restart, and then press ENTER.
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 tool in Control Panel.Windows Server 2003 SP1, Itanium Architecture
|
| Http.sys | 5.2.3790.2419 | 794,624 | 11-Apr-2005 | 21:40 |
Windows Server 2003 SP1, x64
|
| Http.sys | 5.2.3790.2419 | 535,040 | 11-Apr-2005 | 21:40 |
Windows Server 2003 SP1, x86
|
| Http.sys | 5.2.3790.2419 | 289,280 | 09-Apr-2005 | 03:48 |