Ftp unreachable on same subnet
 

Is there a better way to xfer files. Am I doing things the wrong way?
----------------------------------------------------------------

I need to transfer some files between my local lan boxes. The same account names and passwords exist on both boxes.

In order to xfer files from one FC4 box (192.168.0.5) to
another FC4 box (192.168.0.3). I installed VSFTPD on 192.168.0.5.

From 192.168.0.5 I can successfully FTP 'open' 192.168.0.5 and see the files needing transfer.

From 192.168.0.3 I can ping and traceroute to 192.168.0.5.

However when I try FTP 'open' 192.168.0.5, from 192.168.0.3, it says there is no route to the host.

Ethereal shows 192.168.0.3 & 192.168.0.5 talking on the wire. It also shows an ICMP Destination unreachable packet.

Thanks for any help.

ps: Both 192.168.0.3 & 192.168.0.5 can access the internet, without any problems, via an IPCOP gateway at 192.168.0.1.

For your first question, I prefer to use SSH to copy files and as an FTP replacement. It's easy to use and you can use it across unsecured networks. It is slower as ftp because it encrypts traffic. Still, it fits my needs.

For your second question, check to what interface your FTP server is bound. It could be that it is only listening to the loopback interface (lo, also 127.0.0.1), whereas it should be bound to the network interface (typcially eth0, in your case 192.168.0.5).

What is the exact error message you are getting?

Error Messages
 

I would like to use SSH and SCP too. Then I would not have to stop the VSFTPD service when I surf the internet.

----------------------------------------------------------

From 192.168.0.3;

FTP
[mark@whatever ~]$ ftp
ftp> open 192.168.0.5
ftp: connect: No route to host

SSH
[mark@whatever ~]$ ssh 192.168.0.5
ssh: connect to host 192.168.0.5 port 22: No route to host

PING
[mark@whatever ~]$ ping 192.168.0.5
PING 192.168.0.5 (192.168.0.5) 56(84) bytes of data.
64 bytes from 192.168.0.5: icmp_seq=0 ttl=64 time=0.417 ms
64 bytes from 192.168.0.5: icmp_seq=1 ttl=64 time=0.484 ms

TRACEROUTE
[mark@whatever ~]$ traceroute 192.168.0.5
traceroute to 192.168.0.5 (192.168.0.5), 30 hops max, 38 byte packets
1 192.168.0.5 (192.168.0.5) 0.596 ms !<10> 0.708 ms !<10> 0.554 ms !<10>


ETHEREAL
No. Time Source Destination Protocol Info
1 0.000000 192.168.0.3 192.168.0.5 TCP 40790 > ftp ...

2 0.000288 192.168.0.5 192.168.0.3 ICMP Destination unreachable (Host administratively prohibited)

3 4.998883 Intel-Hf_f1:e7:7c 3com_0f:72:1b ARP Who has 192.168.0.5? Tell 192.168.0.3

4 4.999106 3com_0f:72:1b Intel-Hf_f1:e7:7c ARP 192.168.0.5 is at 00:10:5a:0f:72:1b

Can you post the output of command `route` from your .3 and your .5 machines?

Resolved!, Was the firewall.
 

About a half hour ago I realized that I had enabled the Fedora firewall on the 192.168.0.5 box.

I changed its security level configuration to allow FTP and SSH through the firewall. Now everything works.

I successfully FTPed and SSHed between 192.168.0.3 and 192.168.0.5

Thanks for your support!

Sorry to have wasted your time on something so stupid on my part. :-(



Sincerely,
NewbieMark

Well, maybe we wasted your time by not asking the right questions ;-)
Glad it works.