* no route to host on port 80
@ 2003-05-05 2:56 Tim Dionne
2003-05-10 18:01 ` Alistair Tonner
2003-05-11 8:06 ` Joel Newkirk
0 siblings, 2 replies; 3+ messages in thread
From: Tim Dionne @ 2003-05-05 2:56 UTC (permalink / raw)
To: netfilter
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.
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: no route to host on port 80
2003-05-05 2:56 no route to host on port 80 Tim Dionne
@ 2003-05-10 18:01 ` Alistair Tonner
2003-05-11 8:06 ` Joel Newkirk
1 sibling, 0 replies; 3+ messages in thread
From: Alistair Tonner @ 2003-05-10 18:01 UTC (permalink / raw)
To: Tim Dionne, netfilter
On May 4, 2003 10:56 pm, Tim Dionne wrote:
> 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!
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: no route to host on port 80
2003-05-05 2:56 no route to host on port 80 Tim Dionne
2003-05-10 18:01 ` Alistair Tonner
@ 2003-05-11 8:06 ` Joel Newkirk
1 sibling, 0 replies; 3+ messages in thread
From: Joel Newkirk @ 2003-05-11 8:06 UTC (permalink / raw)
To: Tim Dionne; +Cc: netfilter
On Sun, 2003-05-04 at 22:56, Tim Dionne wrote:
> 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.
>
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
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2003-05-11 8:06 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-05-05 2:56 no route to host on port 80 Tim Dionne
2003-05-10 18:01 ` Alistair Tonner
2003-05-11 8:06 ` Joel Newkirk
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox