|
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: Brian Collins (listbc
newnanutilities.org)
Date: Fri Sep 01 2006 - 10:55:56 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
> > 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?....
I'd recommend first looking at the host firewall, iptables. Do 'iptables -L
-n' and see what ports/hosts are tagged for DROP/REJECT.
Also, try the traceroute again, this time to one or more of the hosts that
Postfix cannot reach.
And since it's on a virtual machine, there may be other limitations here.
I've never set up a VM inside Windows, so my expertise in that is nil.
Whatever app set up the VM may have some "firewalling" in place, and Windows
firewall may also come into play here. I can't help you there.
--Brian
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]