[ale] ftp - no route to host???
Geoffrey
lists at serioustechnology.com
Tue Jul 27 07:33:59 EDT 2010
Richard Bronosky wrote:
>>> ftp $IP_ADDR
>>>
>>> returns:
>>>
>>> ftp: connect: No route to host
>
> If the error was connection refuse, or connection reset, I'd say it
> was either a firewall on the box or by his ISP. But, "No route" means
> his client does not know that it has a network interface capable of
> routing traffic to the given host (which in this case is specified by
> an IP address). Although he is able to reach it via SSH and UDP ping.
> That's jacked up.
>
> Maybe try:
> echo $IP_ADDR # make sure you have the right var/value
> host $IP_ADDR # seeing if you can do a [reverse] lookup on the var/value
> telnet $IP_ADDR 22 # standard ssh port number
> telnet $IP_ADDR 21 # standard ftp port number
>
> If you get "No route to host" from one of those telnets and not the
> other... evil is afoot.
So if I try:
ftp 192.168.112.133 21
I get to the machine. Why would I have to specify the port? Wouldn't
ftp use the default port, uh, by default?
It's been so long since I played with ftp.... :(
--
Until later, Geoffrey
"I predict future happiness for America if they can prevent
the government from wasting the labors of the people under
the pretense of taking care of them."
- Thomas Jefferson
More information about the Ale
mailing list