Setting metabase property DisableSocketPooling has no effect
To install Microsoft Windows support tools
- Insert the Windows Server 2003 CD in the CD-ROM or DVD-ROM drive.
- When the CD opens, click Perform Additional Tasks.
- Click Browse this CD.
- Double-click Support.
- Double-click Tools.
- Double-click SUPTOOLS.MSI.
- Click Next, type your information in the Name and Organization boxes, click Next, and then click Next on the following screen.
- Click Next again to start the installation.
- Click Finish.
To add an IP address to the IP inclusion list
- Click Start, and then click Run.
- Type cmd, and then click OK to open a command prompt.
- Type the following, where xxx.xxx.x.x is the IP address you want to add:httpcfg set iplisten -i xxx.xxx.x.xWhen this succeeds, Httpcfg returns the following:HttpSetServiceConfiguration completed with 0
To view additional status codes, see the Httpcfg help.
- After the IP address is added, use the following command to list it: httpcfg query iplistenHttpcfg returns the following:IP :xxx.xxx.x.x
- From the command prompt, stop the HTTP service and its dependent services. To do this, type the following string at the command prompt:net stop http /y
- From the command prompt, restart the HTTP service and it dependent services. To do this, type the following string at the command prompt:net start w3svcNote When you start w3svc, all services that were stopped when HTTP was stopped will start.
Because DisableSocketPooling is defined as a valid property in the IIS 6.0 metabase schema (MBSchema.xml), you can still set this property by using Adsutil.vbs, but this has no effect. The functionality in IIS 6.0 is part of the new kernel level driver HTTP.sys. To configure HTTP.sys, you must use Httpcfg.exe.
In IIS 5.0, the TCP listener is Winsock. Winsock uses sockets and IIS is bound to the performance and scalability of the Winsock API. Socket pooling was introduced to address problems in Internet Information Server (IIS) 4.0 where resource usage was high with many Web sites using individual IP addresses.
To solve this scalability problem, IIS 5.0 uses socket pooling to allow resources to be shared. Socket pooling permits double or triple the number of sites to be run on a specific server with unique IP addresses. The DisableSocketPooling property is also introduced in IIS 5.0 and is used when another application is installed that requires use of a port that IIS listens on by default (such as port 80).
In IIS 6.0, HTTP.sys is the TCP listener and HTTP.sys does not use the Winsock API. Sockets are not a configurable property. HTTP.sys uses an IP inclusion list. By default, this list is blank and IIS listens on all IP addresses. You can specify the IP addresses IIS will listen on by adding them to the IP inclusion list.
Important The IP inclusion list is read during startup of the HTTP service. If you change the list, you must restart the service.
Note The HTTP service and the HTTP SSL service are different services. The HTTP service does not appear in the services list and must be restarted at a command prompt. To do this, follow these steps:
- Click Start, click Run, and then type cmd to open a command prompt. At the command prompt, type net stop http /y and press ENTER. This stops the HTTP Secure Sockets Layer (SSL) service and the World Wide Web publishing services because they are dependent on the HTTP service.
- To start the HTTP service, type net start w3svc at the command prompt. This starts the HTTP SSL service and the HTTP service.
- Click Start.
- Click All Programs.
- Click Windows Support Tools.
- Click Support Tools Help.
- Click H under Alphabetical List of Tools by File Name.
- Double-click Httpcfg.exe ( HTTP Configuration Utility).
Article ID: 813368 - Last Review: 12/03/2007 21:25:59 - Revision: 5.3
- kbhowto KB813368