Problem: Socket pooling is enabled and the Web server is binding to 0.0.0.0

When running Microsoft IIS server, version 5.0 on Windows back-end servers, you must configure the Microsoft IIS server to be bind specific. Otherwise, socket pooling is enabled as the default, and the Web server binds to 0.0.0.0 and listens for all traffic, rather than binding to the virtual IP addresses configured as multiple identities for the site. If an application on the local host goes down while socket pooling is enabled, AIX® or Windows ND server advisors detect this; however, if an application on a virtual host goes down while the local host stays up, the advisors do not detect the failure and Microsoft IIS continues to respond to all traffic, including that of the downed application.

To determine whether socket pooling is enabled and the Web server is binding to 0.0.0.0, issue the following command:
 netstat -an
The instructions for how to configure the Microsoft IIS server to be bind-specific (disable socket pooling), are located on the Microsoft Product Support Services Web site. You can also go to one of these URLs for this information:
IIS5: Hardware Load Balance Does Not Detect a Stopped Web Site (Q300509)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q300509
How to Disable Socket Pooling (Q238131)
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q238131


Terms and conditions for information centers | Feedback

Last updated: September 10, 2012 09:00 AM EDT
File name: ttrb_multclus.html