|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: OT: No route to host
From: email builder (emailbuilder88
yahoo.com)
Date: Fri Sep 01 2006 - 10:36:58 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Spoke too soon in one regard:
> TIA to anyone who can assist with a problem that is quite off topic. I
> have
> a fedora core 5 system dumped in my lap that is built on a virtual machine
> inside of a windows O/S. Yuck. Problem is that there is a certain amount
> of
> connectivity out of the linux O/S, because wget works for almost anything,
> a
> browser loaded up in X windows works fine, DNS queries work just fine, but
> postfix (and as I learned subsequently, just regular telnet) cannot connect
> to most any host, complaining "no route to host". I'm not sure how to
> figure
> this one out, especially since only some types of connections fail. Is
> this
> purely outgoing port filtering on the local network firewall?? I have the
> same results with and without the firewall on the fedora system (but there
> is
> still a physical home router type firewall between this and the rest of the
> world).
>
> # telnet slashdot.org
> Trying 66.35.250.150...
> telnet: connect to address 66.35.250.150: No route to host
> telnet: Unable to connect to remote host: No route to host
>
> Traceroute seems to find slashdot (although some of the other hosts I tried
> didn't get that far):
>
> # traceroute slashdot.org
> traceroute to slashdot.org (66.35.250.150), 30 hops max, 40 byte packets
> 1 192.168.1.1 (192.168.1.1) 0.339 ms 1.067 ms 0.250 ms
> <cut to protect the innocent>
> 10 dcr2-so-2-0-0.SanFranciscosfo.savvis.net (204.70.192.90) 154.895 ms
> 156.522 ms 151.836 ms
> 11 bhr1-pos-0-0.SantaClarasc8.savvis.net (208.172.156.198) 164.649 ms
> 161.233 ms 164.077 ms
> 12 csr1-ve243.santaclarasc8.savvis.net (66.35.194.50) 154.987 ms
> 152.728
> ms 151.281 ms
> 13 66.35.212.174 (66.35.212.174) 172.265 ms 172.805 ms 154.023 ms
> 14 slashdot.org (66.35.250.150)(H!) 172.454 ms (H!) 175.008 ms (H!)
> 173.155 ms
>
> Ahhh, in fact I see that this does work:
>
> # telnet slashdot.org 80
> Trying 66.35.250.150...
> Connected to slashdot.org (66.35.250.150).
> Escape character is '^]'.
>
> So I guess it's just port filtering?? Yeeeah, that's my best guess.
>
> If I'm on the right track, is there anything I can do at all to bypass the
> filter without changing it (not currently under my jurisdiction)? It looks
> like port 465 gets through, etc, but this fedora box with postfix is trying
25 seems to fail and 465 gets through from the HOST (windows) O/S, but in the
Fedora system, BOTH ports fail with the same "no route to host" error. So
that confuses me just a bit. Something to do with the bridged
networking?....
> to send out mails to other SMTP servers that are all listening on 25. My
> guess is that the only place to fix it is at the router here... but I'd
> love
> to hear different...
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]