Why will IIS work with localhost, but not with IP address?

not much help - but i have the same issue in reverse - localhost no longer
works - only the ip works - this was after sp2.

"Joe" <joewasik DeleteThis @msn.com> wrote in message
news:1118217897.496905.188310@g49g2000cwa.googlegroups.com...
 > We run Windows XP pro with IIS 5.1. We have always been able to access
 > our default web site via either localhost or the router's IP address.
 > Now, all of a sudden, I get nothing with the IP address, but the
 > localhost still works. I can ping the IP address. I can telnet the IP
 > address. I just can't see IIS with the IP. I tried turning off the
 > Windows firewall. I tried bypassing the router, hooking the PC
 > directly to the DSL modem. Nothing matters. IIS had worked forever. We
 > didn't install or reconfigure anything. But I do think Windows Update
 > may have run a few times. A Netstat shows this line for port 80:
 > TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
 > Since I've never had to look at netstat before, I'm not sure whether
 > this is right. Can anyone help? Are there any diagnostics that I can
 > run?
 > Thanks.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

That internal IP address is fixed, not a DHCP address. It is
192.168.1.240. The router had to be told which computer to which to
route HTTP traffic. And no, that address not does work. I get an
Action Canceled error when going there. Firefox reports a Connection
Refused".
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

Your situation (localhost does not work) is likely due to a security change
in XPSP2. There is a KB describing it.

--
//David
IIS
<a style='text-decoration: underline;' href="http://blogs.msdn.com/David.Wang" target="_blank">http://blogs.msdn.com/David.Wang</a>
This posting is provided "AS IS" with no warranties, and confers no rights.
//
"Jason" <microsoft.DeleteThis@anywhere.com> wrote in message
news:e3izo8AbFHA.1384@TK2MSFTNGP09.phx.gbl...
not much help - but i have the same issue in reverse - localhost no longer
works - only the ip works - this was after sp2.

"Joe" <joewasik.DeleteThis@msn.com> wrote in message
news:1118217897.496905.188310@g49g2000cwa.googlegroups.com...
 > We run Windows XP pro with IIS 5.1. We have always been able to access
 > our default web site via either localhost or the router's IP address.
 > Now, all of a sudden, I get nothing with the IP address, but the
 > localhost still works. I can ping the IP address. I can telnet the IP
 > address. I just can't see IIS with the IP. I tried turning off the
 > Windows firewall. I tried bypassing the router, hooking the PC
 > directly to the DSL modem. Nothing matters. IIS had worked forever. We
 > didn't install or reconfigure anything. But I do think Windows Update
 > may have run a few times. A Netstat shows this line for port 80:
 > TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
 > Since I've never had to look at netstat before, I'm not sure whether
 > this is right. Can anyone help? Are there any diagnostics that I can
 > run?
 > Thanks.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

is the ipaddress bound to the site? Are you running all unnasigned, or have
you perhaps added a hostname entry?

"Joe" <joewasik DeleteThis @msn.com> wrote in message
news:1118217897.496905.188310@g49g2000cwa.googlegroups.com...
 > We run Windows XP pro with IIS 5.1. We have always been able to access
 > our default web site via either localhost or the router's IP address.
 > Now, all of a sudden, I get nothing with the IP address, but the
 > localhost still works. I can ping the IP address. I can telnet the IP
 > address. I just can't see IIS with the IP. I tried turning off the
 > Windows firewall. I tried bypassing the router, hooking the PC
 > directly to the DSL modem. Nothing matters. IIS had worked forever. We
 > didn't install or reconfigure anything. But I do think Windows Update
 > may have run a few times. A Netstat shows this line for port 80:
 > TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
 > Since I've never had to look at netstat before, I'm not sure whether
 > this is right. Can anyone help? Are there any diagnostics that I can
 > run?
 > Thanks.
 ><!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

With "bound" you're asking me if this IP address is static? Yes, it
is. It even has a real domain name pointing to it, which by the way,
is also not working. An important clue here is that we tried running
without the router and saw the same result. The IIS logs see the
localhost access, but not the IP access. And Windows Updates have
shown up in the Windows folder.

IIS broke once before, a year ago, when installing SP2. I had to
rebuild the machine from scratch to get IIS to work back then. This
time I will not rebuild. I hope that someone can point me to a
solution or a way to diagnose the problem. But in the end, if IIS
won't work. We'll have to install Apache (which is bad since we want to
use ASP.Net).

Thanks though for all of your suggestions.
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

Thanks. But as I pointed out before, we already tried removing the
router, then connecting the PC directoy to the DSL modem. It doesn't
help. We also disabled all firewalls and virusscanners. The point is,
IIS used to work. We didn't change a thing -- at least not on purpose.
All of a sudden, no one can get to the web site anymore except locally
using localhost. A netstat seems to say that IIS is listening, but we
can't seem to reach it. Wish I knew what was going on. We run AdAware
and Spybot. Is it possible that these tools blocked IIS? Seems far
fetched, but I grasping at straws here. Isn't there a good diagnostics
tool out there that can show me port 80 traffic?
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

On 8 Jun 2005 08:05:14 -0700, "Joe" <joewasik DeleteThis @msn.com> wrote:

 >That internal IP address is fixed, not a DHCP address. It is
 >192.168.1.240. The router had to be told which computer to which to
 >route HTTP traffic. And no, that address not does work. I get an
 >Action Canceled error when going there. Firefox reports a Connection
 >Refused".

Many routers won't let you route out to a public IP and back in to
another private IP. Localhost doesn't go outside the server.

Jeff<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

On 2005-06-08, Joe <joewasik.DeleteThis@msn.com> wrote:
 >
 > Thanks though for all of your suggestions.

Forget about IIS, it sucks. That's my suggestion.

Bye ! Have a good day !

--
Pierre Tramo
J2EE Lead Architect.<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

Perhaps. I completely re-installed IIS. Had a bunch of headaches
doing that. And it still doesn't work.

Looks like its goodbye IIS, ASP.Net, and maybe even Visual Studio.Net

What a shame.
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

Is this right ??? Advice will be greatly appreciated.

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:7 0.0.0.0:0 LISTENING
TCP 0.0.0.0:9 0.0.0.0:0 LISTENING
TCP 0.0.0.0:13 0.0.0.0:0 LISTENING
TCP 0.0.0.0:17 0.0.0.0:0 LISTENING
TCP 0.0.0.0:19 0.0.0.0:0 LISTENING
TCP 0.0.0.0:21 0.0.0.0:0 LISTENING
TCP 0.0.0.0:80 0.0.0.0:0 LISTENING
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:443 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:1111 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1032 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1048 0.0.0.0:0 LISTENING
TCP 127.0.0.1:5679 0.0.0.0:0 LISTENING
TCP 192.168.1.240:139 0.0.0.0:0 LISTENING
UDP 0.0.0.0:7 *:*
UDP 0.0.0.0:9 *:*
UDP 0.0.0.0:13 *:*
UDP 0.0.0.0:17 *:*
UDP 0.0.0.0:19 *:*
UDP 0.0.0.0:161 *:*
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:500 *:*
UDP 0.0.0.0:1054 *:*
UDP 0.0.0.0:3456 *:*
UDP 0.0.0.0:4500 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1037 *:*
UDP 127.0.0.1:1043 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.240:123 *:*
UDP 192.168.1.240:137 *:*
UDP 192.168.1.240:138 *:*
UDP 192.168.1.240:520 *:*
UDP 192.168.1.240:1900 *:*
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

On 8 Jun 2005 16:11:11 -0700, "Joe" <joewasik.DeleteThis@msn.com> wrote:

 >Thanks. But as I pointed out before, we already tried removing the
 >router, then connecting the PC directoy to the DSL modem. It doesn't
 >help. We also disabled all firewalls and virusscanners. The point is,
 >IIS used to work. We didn't change a thing -- at least not on purpose.
 > All of a sudden, no one can get to the web site anymore except locally
 >using localhost. A netstat seems to say that IIS is listening, but we
 >can't seem to reach it. Wish I knew what was going on. We run AdAware
 >and Spybot. Is it possible that these tools blocked IIS? Seems far
 >fetched, but I grasping at straws here. Isn't there a good diagnostics
 >tool out there that can show me port 80 traffic?

Did your ISP start blocking port 80? Have you tried using another
port to test? Have you tried a Telnet to port 80?

Using the DSL modem, does your system get assigned a public IP? Did
you use that IP in your tests? Everything you post shows a
192.168.x.x number is why I ask.

Are you testing with just the IP to eliminate name resolution issues?
Is IIS set to use host headers? Are you answering on all IP's or just
a single one?

Jeff<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

On 9 Jun 2005 01:54:43 -0700, "Joe" <joewasik.DeleteThis@msn.com> wrote:

 >Perhaps. I completely re-installed IIS. Had a bunch of headaches
 >doing that. And it still doesn't work.
 >
 >Looks like its goodbye IIS, ASP.Net, and maybe even Visual Studio.Net
 >
 >What a shame.

Especially sincce the problem isn't IIS. If Localhost worked, IIS is
working. Your problem is network communications related, and will
transfer to using any web server software on your system.

Jeff<!-- ~MESSAGE_AFTER~ -->
 >> Stay informed about: Why will IIS work with localhost, but not with IP address? 

Thanks for your interest. I really appreciate your input. The answers
to your questions are: (1) Is my ISP blocking port 80 -- I don't know
for sure (2) Yes, I tried using port 81 with the same bad results. (3)
I have not tried Telnet on port 80. I'm not sure how to listen on port
80 with Telnet. I have tried FTP on port 21. No luck with that either,
so far. (4) We have a static IP address which I have to configure the
PC to use when bypassing the router. (5 & 6) I am trying to reach IIS
both ways, with only an IP address and with IP+header. Neither works.
Attempting to reach the machine via its computer name does not work
either. Only localhost appears to work. (7) We only have one static
IP.

Someone else suggested that this is not an IIS issue. I'm willing to
believe that, but I lack the diagnostics tools to prove that. I
downloaded a TCP monitor from SysInternals. That tool does appear to
say that there is perhaps no incoming TCP. The reliability of this tool
in unknown.

I completely un-installed and re-installed IIS from scratch. No
improvement. And by the way, the re-install fought back. It seems
that XPSP2 has some restrictions. I had this error: ""Setup cannot copy
the file staxmem.dll." and it took this command to fix the problem:
"esentutl /p C:\security\database\secedit.sdb". Something going on
with policies perhaps?

So, We're not giving up. We've put in a lot of hours trying to find
out what's going on.

Thanks again.
 >> Stay informed about: Why will IIS work with localhost, but not with IP address?