Socket Pooling in IIS, useful for improving SSL performance,  can also be a pain if you’re trying to run multiple SSL-enabled web applications on the same server. I continue to run into this with IIS and Apache Web Server/ Tomcat.  To specify which IP Addresses HTTP.SYS (IIS) should explicitly listen on can be manipulated through NETSH.

netsh
http
show iplisten

This should return blank if you have socket pooling enabled. To add a listener on a given IP use the add iplisten command

add iplisten ipaddress=x.x.x.x

where x.x.x.x is the IPv4 address of your choice. IPv6 is also supported. 

There’s an article on MSDN that highlights this and other commands for manipulating http.sys.

http://msdn.microsoft.com/en-us/library/cc307219(VS.85).aspx

Afterwards:

C:\Users\Administrator>netstat -an|find “:443”
  TCP    x.x.x.29:443       0.0.0.0:0              LISTENING
  TCP    x.x.x.30:443       0.0.0.0:0              LISTENING

Better!