How to Disable Socket Pooling

You may need to disable socket pooling under the following conditions:

• A low number of sites are being hosted.


• There are special security concerns.


• Another application or server has need of port 80 on an IP address.

Socket pooling causes Internet Information Services (IIS) to listen to all IP addresses, and this can present a possible security risk for secure domains with multiple networks. Also, bandwidth throttling and performance adjustments apply to all Web sites configured for the same port (for example, port 80).

If bandwidth throttling or performance tuning is being done on a per-site basis, socket pooling must be disabled.

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.

For additional information about how to disable socket pooling in IIS 6.0, click the following article number to view the article 813368 On IIS 6.0: Setting Metabase Property DisableSocketPooling Has No Effect
To disable socket pooling, follow these steps:

Open a command prompt and make sure you are in the 
X:\Inetpub\Adminscripts folder (where X is the IIS installation drive). 
To do this, type the following lines at the command prompt:

X:CD\Inetpub\Adminscripts 
After you open the Adminscripts folder, type the following line at 
the command prompt:

cscript adsutil.vbs set w3svc/disablesocketpooling true

The command replies as follows:

disablesocketpooling : (BOOLEAN) True 
Stop and start the IIS Admin service.
Restart the WWW service.

NOTE: Article Summary

back to the top