Server not accessible

Forum: Other Help Topics
Topic: Server not accessible
started by: Thulemanden

Posted by Thulemanden on July 03 2006,19:49

The webserver is active on 127.0.0.1; the 'Monkey' tab is pressed and the router is programmed to allow 80/80 TCP traffic to the PC's IP. 192.168.0.185

Still there is no access from outside the router.

My ip is < http://83.92.35.50 >

Is any default firewall in place or what else could be the matter?

I used to have a server working on 192.168.0.188 and even when changing the router settings to the other PC IP it kept hitting 188.

I was refurbishing an old Compaq Armada 7770DMT in order to let DSL run a cheap, quiet web server on it, but so far nothing but a net card expense :-(

Hope someone has some clues how to break open the web server. :-)

Posted by Winter Knight on July 06 2006,15:12

I tried to connect to your server at 8:00am PST (GMT -8), Jul 6. Your server did not return pings, nor did it complete a tcp handshake for port 80. I couldn't even tell if it was on.

I know that wasn't helpful, but I figured I should give it a try.

I recommend googling for a network troubleshooting guide. Maybe you've been networking for years, but I've noticed that it is almost always something really, really simple.

I am almost positive that DSL does not come with any built in firewall.

Can you access your webserver from inside your network? You already said you could from your computer itself. It could be a binding problem. Maybe monkey is bound to the lo interface, or maybe a network card you aren't using?

Are you using a static IP? If DSL is configured to use a dynamic IP, it might hop around, avoiding connections.

Just a couple of suggestions. Network problems are always a pain.

Posted by Thulemanden on July 06 2006,15:23

Thanks Winter;

The stealth character of your attempts lead me to believe it's a firewall question, why else would it conceal a 80 port that worked on the other PC.

Perhaps the router support staff can help

Posted by Thulemanden on July 06 2006,15:58

My router had a another firewall feature I just discovered, opening the port.

This made it work.