up vote 1 down vote favorite
1
share [g+] share [fb]

A single server shares our main website (hosted by Apache) and Exchange OWA site (hosted by IIS).

There are 2 different public IPs for the sites, and they have 2 different URLs. However, IIS insists on grabbing all static IPs assigned to the server.

I did some research and found this link: http://support.microsoft.com/kb/892847

I am on IIS 6.0. I went ahead and disabled socketpooling, and restarted. Used httpcfg to assign IIS to the 2 internal IPs (x.x.x.11:80, x.x.x.11:443) and now IIS site acts like the ports are in use, even when Apache is turned off as well. I double checked the apache config and I specified .12 IP where necessary.

I went and looked at my ListenOnlyList and it looks correct. It has the 2 entries and correct ports.

For kicks I turned back on socketpooling and everything works. I can use Active Ports program and see 0.0.0.0:80 go in and out of use as I turn IIS on and off.

Turned socketpooling back off and things go sour again.

It just seems like IIS is completely ignoring the ListenOnlyList. Except when I change the ListenOnlyList to 0.0.0.0 IIS hums along smoothly. I double checked IIS and made the sure the IPs match - they do. Its not on All Unassigned, it is in fact on x.x.x.11. Crazy.

Any ideas?

link|improve this question
feedback

2 Answers

up vote 0 down vote accepted

Disabling socket pooling specifically does not work on IIS6. Instead you must change the registry key mentioned, and then do the httpcfg thing.

Assuming you changed the registry key, what is the output of running httpcfg query iplisten ?

link|improve this answer
IP: 192.168.10.11:80 IP: 192.168.10.11:443 Also tried removing both and doing just the IP and not the ports, which also didn't work. Output looked like: IP: 192.168.10.11 Still no luck Each time as I made the changes, I went in the registry and confirmed they changed the ListenOnlyList, and they did, then rebooted... – user8167 Jul 9 '09 at 16:02
What service pack level are you on? I think this only works on SP2 or higher. (Check your version of HTTP.sys vs. what is in the KB article) – MattB Jul 9 '09 at 16:08
Yep, we are Windows Server 2003 Std, service pack 2. Look at the versions. Looks like it is properly updated.. http.sys is bigger and lists 2007 as create date (server OS was installed early 2009) – user8167 Jul 9 '09 at 16:27
Weird - but I want to confirm one thing - when you are talking about turning socket pooling on and off, are you talking about the metabase property, or the DisableEndPointSharing regkey? – MattB Jul 9 '09 at 16:43
I ran this command cscript adsutil.vbs set w3svc/disablesocketpooling true Found it here: support.microsoft.com/kb/238131/EN-US/#rtDisclaimer – user8167 Jul 9 '09 at 16:53
show 4 more comments
feedback
up vote 0 down vote

Did you make sure to select only the IP address for the IIS server in the website properties in IIS? You might have "(All Unassigned)" selected. I'm not sure if this will solve your problem, but it's worth checking.

link|improve this answer
I double checked it. Its not All Unassigned. At this point it is acting like it can't even read the ListenOnlyList IPs, unless I manually set it to 0.0.0.0, where it hums along, but takes the IP Apache needs as well. – user8167 Jul 9 '09 at 16:03
Time to roll a VM! – Russ Warren Jul 9 '09 at 16:15
feedback

Your Answer

 
or
required, but never shown
discard

Not the answer you're looking for? Browse other questions tagged or ask your own question.