On 2/8/06, Mikkel L. Ellertson <mikkel@xxxxxxxxxxxxxxxx> wrote: > J. K. Cliburn wrote: > > On 2/8/06, Jacob (=Jouk) Jansen <joukj@xxxxxxxxxxxxxxxxxxxx> wrote: > > > >>a.apprich@xxxxxxxxxxxxxxxxxxxx wrote on 8-FEB-2006 11:30:21.57 > >> > >> > >>>>>>>I try to get the rsh command working to a FC4 system > >> > >>[snip] > >> > >>>what does /var/log/messages tell you about login via rsh? > >> > >>No Route to host > > > > > > I know you said you have the relevant ports unfiltered in iptables, > > but isn't this the typical message received when you attempt to access > > a blocked port? > > > Nope. You will get connection refused if the port is set to reject, > and a timeout message if it is set to drop. You get the No route to > host when there is a network configuration problem. I disagree, but I won't be able to substantiate my disagreement until I get home this evening. Every time I see the "No route to host" message, my next step is to look for a filter in the way, and I almost always find a port blocked by netfilter.
