"network location cannot be reached" error with multiple ip's

I have a few sites on an IIS6 server. The web sites which are attached to a certain ip address work fine.
The other web sites which are attached  to other ip addresses give a
"network location cannot be reached... " error when I try to start them.

I did a httpcfg query iplisten and noticed there's a single ip address listed. It's the one which the working sites are using.

So I used the httpcfg to add the rest of the ip addresses and rebooted.
I noticed none of the sites work anymore and I get a "process cannot access the file because it is being used by another process" error

So I figured only a single ip address can be bind. So I removed them with the httpcfg command and rebooted and came back to the initial issue.

So what is the issue exactly? Is it correct that only a single ip address should be in the listen list?
Why am I getting the "network location cannot be reached" message? Is it because the ip address is not in the listen list but if I add it, it causes another issue.
I am missing something.
Who is Participating?
jentel2Connect With a Mentor Author Commented:
After some more troubleshooting, the solution was to use httpcfg to add ip addresses without specifying post numbers.
Andres PeralesCommented:
If you have multiple websites on one webserver, you will need to add multiple IP addresses to the server.
How to assign multiple IP addresses to the same NIC

If you want to assign more than one IP address to a network card follow the steps below. Right-click on My Network Places, choose Properties. Right-click on the Local Area Connection, choose Properties.

Highlight Internet Protocol (TCP/IP), click Properties.

If you use DHCP, you should disable it: click Use the following IP address and enter IP address, Subnet mask and Default gateway. Click Advanced... at the bottom.

Enter additional IP addresses: click the Add... button and enter a new IP address and Subnet mask.

Once you have done that then you can open IIS Manager, and you can then assign a separate IP address to each separate website that you have listed in IIS.
You will need to have a separate IP address for all the websites or for the websites that you want to use the same leave the drop down setting as unassigned and then make sure you use host headers for those websites.
As long as you are using host headers for the websites that are unassigned or a separate IP address for each of the sites you should not have a problem.
Hope that helps.
jentel2Author Commented:
I forgot to mention these addresses are already on the nic.

IIS manager wouldn't show these addresses if the server didn't have them in its tcp/ip configuration.

The host headers are set up correctly. Also the absence of them or wrong values will not cause the error I am having. Host headers are used when a request comes in, not when I try to start the web site.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.