On Fri, May 21, 2004 at 12:00:30AM -0500, mw-list-yum@xxxxxx wrote: > [Errno 4] IOError: [Errno ftp error] (113, 'No route to host') > > I get the following clue when I use ncftp: > > # ncftp moni.msci.memphis.edu > NcFTP 3.1.6 (Aug 25, 2003) by Mike Gleason (http://www.NcFTP.com/contact/). > Connecting to 141.225.11.87... > Welcome to the FTP service on moni.msci at the University of Memphis. > Logging in... > Login successful. > Logged in to moni.msci.memphis.edu. > ncftp / > cd pub/fedora/linux/core/2/i386/os/headers/ > Directory successfully changed. > ncftp ...core/2/i386/os/headers > ls -l header.info > connect failed: No route to host. > Falling back to PORT instead of PASV mode. > -rw-r--r-- 1 0 0 111939 May 13 11:11 header.info > > The ftp server is running FC2 with vsftpd. > > Any advice appreciated. Hrm. That is interesting. "no route to host" is (surprise surprise) a routing problem, but that puzzles me since PASV should be doing pretty much the same thing for both types of connections. I don't remember the details of how it works, though. You might also try running a packet sniffer like ethereal to see what's happening. Hmm. Does the server identify itself for the second connection? If so, is it identifying itself incorrectly? -Michael -- Michael D. Stenner mstenner@xxxxxxxxxxxxxxx ECE Department, the University of Arizona 520-626-1619 1230 E. Speedway Blvd., Tucson, AZ 85721-0104 ECE 524G
