unable to resolve 127.0.0.1

[Linda]

I am not sure if this is the right group, if not can
someone let me know where should I post this?

I have configured the application server on my
local computer. I am able to access it using
the url - http://localhost/mainpage
however, if I try to use http://127.0.0.1
I get "page not be found" contact sys admin
error.

My question is why it is not recognizing this
ip address? How can I make it work?

Thank you,
-Le

 

[hutch]

have you tired you PC IP addrres instead ??

ex: 192.168.0.1

or http://127.0.0.1/mainpage ?

 

[Linda]

This is my PC IP address. Everything else works like
if I enter my computer name or computer name/mainpage both
work. Just like localhost and localhost/mainpage.
I need this address to resolve.

Thank you,
-Le

 

[Ben]

127.0.0.1 is a local loopback address for testing your
network interface card hardware. It can not be used for
any other function.

 

[Ben]

You must assign a different address to your PC. The
address you are using is a test address. The private
address space you can use inside your router is any
address in the 192.168.0.0 network.

 

[Ben]

For simplicity sake, use 255.255.255.0 as the subnet mask
for an IP address like 192.168.0.7.

 

[Jim]

Not true, local server processes use this address all the time, even local
proxy servers, even IE itself!

Jim

 

[XPUSER]

Not true, local server processes use this address all the time, even local
proxy servers, even IE itself!

Jim

=======================================================

http://www.rfc-editor.org/rfc/rfc3330.txt

Quote from the article above:

127.0.0.0/8 - This block is assigned for use as the Internet host
loopback address. A datagram sent by a higher level protocol to an
address anywhere within this block should loop back inside the host.
This is ordinarily implemented using only 127.0.0.1/32 for loopback,
but no addresses within this block should ever appear on any network
anywhere [RFC1700, page 5].

=======================================================

 

[Jim]

All the RFC means is that you never *assign* the loopback address on the
network, it's always implied, so assignment to a NIC would be meaningless
(indeed, invalid).

"A datagram sent by a higher level protocol to an address anywhere within
this block should loop back inside the host."

Exactly! The RFC doesn't say "don't use it", it doesn't say "it's invalid",
it doesn't say "it's an illegitimate IP address", all it says is "don't send
it out on the network, because no network device will have that publicly
assigned, instead, loop back to the current host"! That's it. Beyond that,
it's as perfectly a valid IP address as any other. And it's perfectly valid
for any local process to address 127.0.0.1 as any other network address.

Jim

Not true, local server processes use this address all the time, even local
proxy servers, even IE itself!

Jim

=======================================================

http://www.rfc-editor.org/rfc/rfc3330.txt

Quote from the article above:

127.0.0.0/8 - This block is assigned for use as the Internet host
loopback address. A datagram sent by a higher level protocol to an
address anywhere within this block should loop back inside the host.
This is ordinarily implemented using only 127.0.0.1/32 for loopback,
but no addresses within this block should ever appear on any network
anywhere [RFC1700, page 5].

=======================================================

 

[Guest]

I was having a similar problem. I'm using a tool that is "hard coded" to spawn an IE window that hits 127.0.0.1 with a port pointing at a newly started instance of apache tomcat . That would not work but if I captured the url it was trying to get to and changed 127.0.0.1 to localhost, it worked just fine

I resolved the issue by going into IE, tools, internet options, connections, LAN Settings and disabled "Use automatic connection script".