Hi Max,
It looks like a network issue instead of the software. Falling back to
PORT sounds like to ACTIVE mode from PASV mode. In PASV, you will be
connecting to a random port told by server with a random port from your
side. Do you have a firewall to block such traffic that the system will
send out port unreachable ICMP?
Maybe you can do a tcpdump to see what it is going on. For PASV, you can
only use "host <client> and host <server> and tcp and not port 22" as
the filter. It's not effective but it will collect what you want to
locate the issue.
Best regards,
------------
Banyan He
Blog: http://www.rootong.com
Email: banyan@xxxxxxxxxxx
On 4/2/2013 7:12 AM, Max Pyziur wrote:
> Greetings,
>
> Beginning today, I started to receive the following when ftp'ing to my
> CentOS 6 machine:
> ncftp /home/pyz2 > dir
> connect failed: No route to host.
> connect failed: No route to host.
> connect failed: No route to host.
> Falling back to PORT instead of PASV mode.
>
> I can make a connection, but I can't get a directory listing or transfer
> data/files.
>
> I'm flummoxed.
>
> What I had been doing is adding more directives to my /etc/hosts.deny
> file, today to include certain categories of ip addresses for the vsftpd
> service.
>
> I unwound that after I saw the problem starting to occur, and have
> restarted vsftpd several times.
>
> That hasn't changed the above issue.
>
> And yes, I've googled.
>
> My firewall setting has port 21 open.
>
> I can remotely telnet to hostname 21
>
> and I get a response indicating that the port is open.
>
> Any advice would be appreciated.
>
> Much thanks.
>
> Max Pyziur
> pyz@xxxxxxxxx
> _______________________________________________
> CentOS mailing list
> CentOS@xxxxxxxxxx
> http://lists.centos.org/mailman/listinfo/centos
>
_______________________________________________
CentOS mailing list
CentOS@xxxxxxxxxx
http://lists.centos.org/mailman/listinfo/centos
