How to Fix IIS IP issues with HTTPCFG
Wednesday, January 30, 2008 at 3:57PM We run a rather diverse set of web based applications at my company, and many times we have to run them from the same box, to cost down on costs. I recently found myself being forced to reclaim a few IPs on one of our web servers from Apache for IIS.
In a normal world when you assign an IP address to a service, it only takes over that IP. In the microsoft world, when you start IIS it takes over port 80/443 for EVERY IP address on the machine. This is one of those times we must all say "Thanks" to Mr. Gates. Don't get me wrong, IIS is easy and usualy does well, but trying to run IIS and Apache on the same machine, well thats like trying to make some AJAX work in both IE and Firefox.
Once you use HTTPCFG to configure the IPs assigned to IIS, and Apache, MSDN tells you to restart IIS and you'll be fine. Thats just NOT TRUE!! If you restart IIS with the service console, it will not accept the changes you just made with HTTPCFG.
In order to immediately configure the changes you made you simply stop and restart the HTTP services via the command line like so:
step 1: net stop http /y
step 2: net start w3svc
Don't ask me why, but this works and the MMC method doesn't.
Reader Comments (2)
Indeed, an annoying situation. I didn't know about the Service Console part of it.
Seemed to me that if I had the IIS config window open while using httpcfg, my changes wouldn't been seen until I had rebooted.
So weird. I blogged about it on my http://www.dawning.ca/2009/iis-and-apache/" rel="nofollow">site too.
Ugh, yeah, I had to fight with this issue yesterday.
Thanks for posting on it.
Here's http://www.dawning.ca/2009/iis-and-apache/" rel="nofollow">my own post on making this all work out.