Hello, I would like to run IIS and apache on the same physical server. So i have attempted to: 1. Stop IIS listening on all ips - httpcfg delete iplisten -i 0.0.0.0 2. Tell IIS to listen on a specifi ip - httpcfg set iplisten -i <my ip address> 3. Restart services to make the changes take affect net stop http net start http iisreset Unfortunately every time i run httpcfg delete or set, i am given the following error return code "HttpSetServiceConfiguration completed with 1629" It does not seem like my httpcfg command have worked, as httpcfg query iplisten returns the same specific ip (which i dont want iis to listen on) Any help would be greatly appreciated Garth

Are you hosting 2 different web sites with each?

Hi. Yes, I would like to host (for examples sake) - website1.com.au on 1.1.1.1:80 on IIS. - website2.com.au on 2.2.2.2:80 on apache I can run apache or IIS on its own, but no both at the same time. Running httpcfg delete iplisten -i 0.0.0.0 does not clear all the ips in http.sys listen list. (i get a 1629 response code instead of 0) Running httpcfg set iplisten -i 1.1.1.1 does not add that ip to http.sys listen list. (i get a 1629 resposne code instead of 0)

You didn't mention anything about having 2 NICs in the machine but either way, there have been other people who have wanted to do the same thing and the answer was something to do with a virtual server. I've never done it myself but that might point you in the right direction.

Hi. From the documentation i've read, all signs point to IIS effectively putting a lock on port 80 for all ip's. The way around this is to remove all listening ip's from its listen list (httpcfg delete iplisten -i 0.0.0.0) and then add specific ips one at at time (httpcfg set iplisten -i <my ip address>) For some reason though i am getting a 1629 error resposne code rather then a 0 success code which many guides and windows doco has suggest i should receive. :(

I don't doubt that IIS would lock port 80 for itself. That's why I mentioned a 'virtual server'. Set Apache to 8080 and test it that way. http://website2.com:8080

Do You have fixed this issue? i get the same error