Hi,

I'm running an Apache webserver, I've got a DLink router, and a cable-modem. My webserver is configured properly, I've routed port 80 correctly, my ISP is not blocking port 80.

The problem is that when I try to access the webserver via my IP address, it does not work.

For example, if I open IE and type http://10.10.10.10/ into the address bar (where 10.10.10.10 is the IP of my system), it won't work. Running wget gives the same results as does "telnet 10.10.10.10 80".

If instead of the IP, I use localhost (or 127.*), it works just fine.

Also, if I access it through a proxyanother computer somewhere on the Internetit works fine as well (other people can access it).

It's just when I try to use the IP address from my system that it doesn't work.

All other protocols/servers tested work normally: ftp, telnet, email, etc., it's only the webserver that does not. That's why I suspected Apache as the problem.

If I shut down Apache, then run another webserver (for example HttpSvr - The Portable Web Server by Ron Logan), it DOES work.

Okay, so you're thinking that the web-server's got a problem. Wait.

If after running another webserver, I shut it down and run Apache again, it now works! I can access the Apache webserver via the IP now. If I then reboot and try again, I'm back at square one. If I then run another webserver for a second and go back to Apache, it works again. It's completely reproducible. It's like there's something that's not being initialized by Apache (if I merely stop and start Apache a few times it won't work, another webserver is required to kickstart it). And like I said, everyone else can access the Apache webserver as can I by any means other than the IP just fine from the start (before running another webserver).

Presumably to make things even more confusing and frustrating, if I take the router out of the equation and connect the system directly to the modem, then everything works fine. But it can't be the router either since others CAN access the webserver, as can I (if I use localhost or 127.* or do the above mentioned steps). It's almost as though other webservers are triggering something in the router to start/run, whereas Apache does not.

Summary: I've got a problem under one very specific circumstance. After boot up, I am unable to access the Apache webserver on my system via the system's own IP address and only in this manner, every other manner, and everyone else can. Only if I stop Apache, run another webserver, shut that down, then run Apache again, will using the IP of this machine to access the webserver on it from it work. Alternately, if I connect the system directly to the cable-modem, then everything works from the start, including using the IP.

:confused: :confused: :confused:

Does anyone have any clue what's going on? This thing is really driving me nuts.