no route to host on port 80
Hi --
I'm trying to allow outside access to my linux box on port 80. However,
when I try to connect (using a web browser, or telnet) the connection
is not created. When I use telnet and specify port 80 I get a "no route to host" error. I've experimented with my firewall by completely removing all rules from all chains, but the connection can still not be made. I can establish connections on all other ports except 80! Can anyone help me?
Thanks.
Quoted 11 lines · Tim Dionne
Hi --
I'm trying to allow outside access to my linux box on port 80. However,
when I try to connect (using a web browser, or telnet) the connection
is not created. When I use telnet and specify port 80 I get a "no route to host" error. I've experimented with my firewall by completely removing all rules from all chains, but the connection can still not be made. I can establish connections on all other ports except 80! Can anyone help me?Thanks.
A few more details are required here Tim:
1) is the linux box the firewall itself?
2) what is your connection map ...i.e. DSL router to linux box to internal
net with connection through router etc.
3) given the "no route to host" error how/what are you using for DNS?
4) what if any rules are in your firewall script?
Alistair Tonner
nerdnet.ca
Senior Systems Analyst - RSS
Any sufficiently advanced technology will have the appearance of magic.
Lets get magical!
Quoted 10 lines · Tim Dionne
Hi --
I'm trying to allow outside access to my linux box on port 80. However,
when I try to connect (using a web browser, or telnet) the connection
is not created. When I use telnet and specify port 80 I get a "no route to host" error. I've experimented with my firewall by completely removing all rules from all chains, but the connection can still not be made. I can establish connections on all other ports except 80! Can anyone help me?
Quoted 2 lines
Thanks.
Hmmm. If this is a connection from outside that's failing, it sounds like an ISP blocking port 80 inbound to me. I have that situation with VerizonDSL, and have been forced to run Apache on port 83. (either that or pay $30/month extra for 'business' instead of 'residential' service - everything the same except static IP and port 80 unblocked)
If you have the machine on a LAN then ensure that you can successfully access port 80 from the LAN. If it stands alone, then at least try browsing from it to http://localhost:80 and make sure you can access it that way. If all of that is successful, try setting Apache (or whatever web server) up to respond to requests on a different port number, and try accessing it from outside with the explicit port number.
j