IIS 5 & IIS 6
website will not start with new IP
Last post Jan 08, 2010 01:22 PM by qbernard
Dec 27, 2009 09:09 AM|Robert Blackwell|LINK
Hello, I've been having trouble with IIS not being able to start a site and it saying
"The network location cannot be reached. For information about network troubleshooting, see Windows help."
Here's the scoop.
I have about 7 sites configured on this site with only 2 IP's
(in the screenshot below you'll see 8 sites, the 8th site is the new one I'm trying to configure)
first IP is being used across 5 websites (one of these has SSL)
second IP is being used on 1 site (this site has SSL)
I added a new IP to my server and created a brand new website. I tried to bind the new site to the new IP and a new hostheader but when I do the site will not start and if I try to start it I get the error I pasted above.
In the event viewer under System I see this entry
"Cannot register the URL prefix 'http://test.mydomain.com:80:mynewip.152/' for site '86390421'. The IP address for the site is not in the HTTP.sys IP listen list. The site has been deactivated. The data field contains the error number.
httpcfg query iplisten
shows all 3 IP's
netstat -an -p tcp
0.0.0.0 and various ports
my two original ips with port 80 and 443
127.0.0.1 and various ports
I have checked my registry
This shows both the 2 original plus the new ip
I've also taken of a screen grab of metabase explorer showing a working site and this new one
I've been trying to figure this out for about a week no with no solution.
Dec 28, 2009 04:44 AM|qbernard|LINK
Anything else binding on that new ip port 80?
Have you try clean up the registry and readd the ip via httpcfg?
Restart HTTP service?
Dec 28, 2009 05:16 AM|Robert Blackwell|LINK
There are no other websites binding to that ip.
Also, as I mentioned netstat -an -p tcp doesn't even list the IP in question so I dont' see how its possible that anything else is using that port for this ip. I've also used a 3rd party app (active ports) to see which ports are active.
What do you mean by clean up the registry?
Yes I have tried adding/deleting the IP via httpcfg and rebooted/restart iis. No solution.
Dec 29, 2009 07:44 AM|Leo Tang - MSFT|LINK
Please check the following thread to see if it helps:
Thread: HTTP.SYS IP Listen list does not get updated when adding/removing an IP on a server
Dec 29, 2009 10:36 AM|qbernard|LINK
If you are on SP1, then get the hotfix.
If you are SP2, then skip the hotfix coz it is included in sp2.
If it's doesn't appear on netstat after you reboot, I doubt it was registered correct with the OS as well. does it shows on ipconfig ? can you ping the ip locally / remotely? check the network card config first. when this is working then you move on to IIS
Restart service means - net stop / start HTTP
Dec 29, 2009 04:56 PM|Robert Blackwell|LINK
I found that thread already and I had tried the steps with no resolve (even though I'm already on SP 2)
Yes the IP shows up on ipconfig. It's not a problem with the ip not working; I have rdp into the server using the ip so it does work.
Yes I can ping locally and remotely.
Yes, since I had tried the previous hotfix I did net stop/start http but technically a reboot would accomplish the same thing which I have already done several times.
Dec 29, 2009 07:20 PM|Robert Blackwell|LINK
I decided to do windows update since I hadn't in a long time... basically going by the slogain, if it's not broke don't fix it. Well I knew my stuff was broken. Anyway I couldn't download updates and I checked the log and I was having problems with BITS.
After doing some searches online I decided to download the windows update agent and reinstall. After doing so I was successfully able to run windows update.
At the time of this post, I was still DOWNLOADING updates, so nothing had been installed yet.
When I went to IIS manager I noticed the site was running so I checked to see what IP just to see if I had reset it or not but to my amazement it was one of the new IP's and it was working. I checked out the site in my browser via domain and its working.
For testing sake, I have created some other test sites with other free IP's but I get the same problem as before.
httpcfg query iplisten doesn't show the ip, so I go to add it manually but I still cannot start the websites. I then try to specifically add the ip:port but it makes no difference.
So for now, I'm glad that this one site is at least working so I can continue testing. But it doesn't make anysense how it fixed it for the one ip and site (but not the others... unless it is because I hadn't bound the other new IP's to any sites yet)
Dec 30, 2009 02:02 AM|qbernard|LINK
haha! what an experience :) to me it is OS binding gap, coz in your first post you are not seeing it at netstat at all. what you did on WU seems nothing to do with TCP stack as well, but amazingly it starts working for you.
So now if you test the 2nd new IP and bind it to site, same error ? is the 2nd IP appear in netstat ? binding it and test.
Dec 30, 2009 03:43 AM|Robert Blackwell|LINK
At this point I don't really remember if I saw it or not in netstat (or if I even did netstat). This has kind of been a blur of mad repitition. I know I atleast query iplisten and when it wasn't there I added it.
This other ip appears in httpcfg and in netstat. To test further I created two other sites with the remaining new IP's I had and none of the ip's appear in httpcfg or netstat.
Actually let me clarify; all 3 of my IP's show up in netstat under TCP 80/443 (and others such as RDP/FTP or whatever else is going on), the 3 other problematic ones only list under UDP for the ports 53, 123, not TCP
Dec 31, 2009 07:50 AM|qbernard|LINK
ha! thanks for the info. only UDP ? weird right?
so now if you put in the 4th IP can you repro the issue?
Dec 31, 2009 04:23 PM|Robert Blackwell|LINK
If I try binding any of the remaining IP's it's the same issue all over again. They don't show up in httpcfg unless I manually add it, and when I do they dont show up in netstat, and also I can't start the website..
After the 3rd IP magically worked I tried to just add all 3 ips to different test sites, set iplisten and reboot and then the whole server (iis that is) wouldn't start. I forget the exact error but basically it was because one of the iplistens was causing
a problem, this had happened one before when I manually changed the registry ListenOnly and accidentally had an empty line after the last ip.
So basically I had to delete the IP listens and reboot to get everything going again.
Jan 04, 2010 06:09 AM|qbernard|LINK
Jan 05, 2010 08:34 AM|Robert Blackwell|LINK
Yeah, well except I'm still stuck in the same situation. I cannot find a way to solve this. It seems like a total fluke that it was "fixed" for the 3rd IP. I cannot successfully seem to bring up the other IP's
Jan 05, 2010 09:42 AM|qbernard|LINK
I have done quite many boxes on IIS 6 with 10+ IPs, never got into what you experienced.
I'm not sure what is causing this, but I'd check if the OS recognize the new IP correctly first. E.g. netstat, ping, traceroute/etc first. Then only bind it to IIS.
Jan 07, 2010 06:55 PM|Robert Blackwell|LINK
My box has gremlins or something. I decided to give it another crack today and it worked fine.
new site, bind ip/hostheader
httpcfg set iplisten -i myip
net stop http
net start http
open iis, start all sites.
Jan 08, 2010 01:22 PM|qbernard|LINK
LOL.. that's Windows magic.