Home / server / Questions / 38371
Accepted
user8167
Asked: 2009-07-10 07:31:55 +0800 CST

IIS & Apache Same Server

  • 772

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?

apache-2.2 iis

3 Answers

  1. 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.

    • 0
  2. Best Answer

    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 ?

    • 0

  3. I have written a blog post that details the steps you use in httpcfg to get this to work:

    http://www.diaryofaninja.com/blog/2012/06/21/forget-what-your-mother-told-you-iis-and-apache-can-be-friends

    Basically:

    • manually create some IP address bindings for IIS (therefore not creating a "catch all" scenario)
    • setup Apache to run on the IP address or port that isn't in the above bindings
    • 0