apm825
asked on
Binding IIS v6 on win2003 to certain IPs so that Apache can bind to another IP both on port 80? - 500pts
Binding IIS v6 on win2003 to certain IPs so that Apache can bind to another IP both on port 80? - 500pts\
I would like both apache and IIS to run on my windows 2003 server and both on port 80. Can I configure IIS to only bind to certain IP addresses, so it won't conflict when I try to start up Apache on a particluar IP address? If so, how?
I would like both apache and IIS to run on my windows 2003 server and both on port 80. Can I configure IIS to only bind to certain IP addresses, so it won't conflict when I try to start up Apache on a particluar IP address? If so, how?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Actually, that article also clearly says (IIS6): To configure HTTP.sys, you must use Httpcfg.exe.
and points to this article:
http://support.microsoft.com/kb/813368/EN-US/
which is the same procedure as the posted above...
and points to this article:
http://support.microsoft.com/kb/813368/EN-US/
which is the same procedure as the posted above...
ASKER
yeah! thanks. I think we were typing at the same time....going to try here in a sec, but i'm almost sure this is it. thanks!
ASKER
i just did all of that and its still listening to all those ip addresses. I have like 20+ ip addresses on my server. I have 2 or 3 web apps that are assigned to *all unassigned*. Do you think this would keep it listening to those other ports?
ASKER
yep! that seemed to work! :-)
ASKER
ok, now i'm feeling silly. i had changed apache's config file to another port before when I was troubleshooting it. Once I told it to go for port 80, no dice. I'm thinking shut down iis, start up apache, then start iis. Hope that works.
Yes, that order should be correct.
If you want to ensure that this start order is also respected at Windows reboot, you will need to make IIS dependant of Apache
If you want to ensure that this start order is also respected at Windows reboot, you will need to make IIS dependant of Apache
ASKER
ok, that seemed to work...now i need to install a php or some app and see apache in action.
I'm starting to wonder how I'm going to have to configure this for when the server boots up. Now that I'm typing this, I'm thinking i need to disable the pooling in IIS6 the way you did it in v5. I guess I thoguht that was an iis5 thing.
I'm starting to wonder how I'm going to have to configure this for when the server boots up. Now that I'm typing this, I'm thinking i need to disable the pooling in IIS6 the way you did it in v5. I guess I thoguht that was an iis5 thing.
ASKER
>>Yes, that order should be correct.
If you want to ensure that this start order is also respected at Windows reboot, you will need to make IIS dependant of Apache
oh, i never thought of that. Something I think is weird is that apache is not listed in my services console. Is that normal? I would assume I would set up dependencies there.
If you want to ensure that this start order is also respected at Windows reboot, you will need to make IIS dependant of Apache
oh, i never thought of that. Something I think is weird is that apache is not listed in my services console. Is that normal? I would assume I would set up dependencies there.
Howto run apache as service:
http://httpd.apache.org/docs/win_service.html
After that, add dependencies:
http://support.microsoft.com/default.aspx?scid=kb;en-us;193888&Product=win2000
http://httpd.apache.org/docs/win_service.html
After that, add dependencies:
http://support.microsoft.com/default.aspx?scid=kb;en-us;193888&Product=win2000
ASKER
wow, thanks. that was above and beyond. These were excellent answers!
Glad I could help. Expecting a good grade then when you close the question.
ASKER
absolutely! sorry for the delay!
ASKER
disabling socket pooling between IIS5 and IIS6 is done differently: http://support.microsoft.com/kb/q238131/