Can't access HTTP server on own computer?

Question

This is driving me NUTS!
I'm running EasyPHP on my PC.
This URL works: http://localhost
This URL doesn't: http://192.168.2.88
When I do an ipconfig /all, both IPs are the same!
I can do a "ping 192.168.2.88" and "ping localhost"
"telnet localhost 80" is successful, but "telnet 192.168.2.88 80" fails

Somehow I can't refer to my own PC using the IP address. Any ideas? All firewalls have already been turned off on the PC...

localhost is an alias for 127.0.0.1, and I have no problems connecting to either. As mentioned earlier, no firewalls are running.

Why I mentioned that both IPs are the same is because the PC that I'm working on has both 192.168.2.88 and 127.0.0.1 as IP addresses. 127.0.0.1 is a standard loopback address while 192.168.2.88 was assigned by the router. Both IP addresses point to the same PC.

The PC should be able to access its own IP address, otherwise when you try "ping"ing your own IP, it should fail.

Pinging 192.168.2.88 on the PC works fine. Same goes for localhost

Answer 1

The fact the localhost works suggests that your HTTP server is in fact working properly and you are accessing it.

You say in your question that ipconfig shows "both IPs are the same". Does this mean you have two network cards and both are using the same IP? (perhaps, a wired and wireless card). If you do and you have entered the same IP address for both, that will certainly cause a conflict when attempting to address the IP.

To fix that, you can do one of the following:

A. Go to network connections and disable one of the cards, presumably the one you are not using.

or.

B. Go to the network connections and open the properties of one of the cards. In the IP settings either change the IP to something different (like 192.168.2.89) or, if you use a router with a DHCP server, set the card to acquire the address automatically.

Hope that helps.

Answer 2

I think the problem is simple.

You state that the server is on the SAME computer that you are using.

MOST computers can NOT "answer" themselves through their IP address; they HAVE to be accessed through the "localhost" or loopback address since all communications are "INTERNAL" to the computer.

The only exception I know of is mainframes with "workstations", which use the mainframe for ALL application processing, since the workstation has NO application processing ability.

Answer 3

Is your firewall blocking it?
Try http://127.0.0.1