headers
Whaley, Jason | 19 Jan 2006 15:12

RE: Timeout While Retrieving Directory Listing

Hello Again Raul,

I disabled passive connections in Filezilla (my test ftp client), and I am receiving the same timeout.  

Ideally I want my users (very technically unsavvy) to connect through IE so I will need to get this working
without having clients adjust any settings.

I used ftp from the command line from my work machine and I could connect and be placed in the chroot'ed
directory for the ftp user.  However, an issuance of dir or ls takes 60 seconds exactly everytime to
complete from the command line ftp, but does work.  The behavior of ls and dir is that the output is shown, but
hangs for 60 seconds, then the report is shown.

For instance:

	ftp> dir
	200 PORT command successful
	150 Connecting to port 3047
	-rw-r--r--    1 99       99             82 Jan 19 08:14 ezreg.dat

	//WAIT FOR 60 SECONDS

	226-Options: -l
	226 1 matches total
	ftp: 67 bytes received in 60.00Seconds 0.00Kbytes/sec.

Using put works fine and as expected.  Using get works but again, takes exactly 60 seconds to complete for
only a <1kb sized file.

I tried ftp from localhost and everything worked well, ls and dir commands worked in milliseconds, as expected.
(Continue reading)

Permalink | Reply |
headers
DervishD | 19 Jan 2006 16:34

Re: Timeout While Retrieving Directory Listing

    Hi Jason :)

 * Whaley, Jason <jtwhaley <at> email.uncc.edu> dixit:
> I disabled passive connections in Filezilla (my test ftp client),
> and I am receiving the same timeout.

    My problem was not with passive connections, but with *extended*
passive connections. Anyway, this problem doesn't seem to be related
with that.

> I used ftp from the command line from my work machine and I could
> connect and be placed in the chroot'ed directory for the ftp user. 
> However, an issuance of dir or ls takes 60 seconds exactly
> everytime to complete from the command line ftp, but does work. 
> The behavior of ls and dir is that the output is shown, but hangs
> for 60 seconds, then the report is shown.

    I had exactly the same problem with the default ftp server (I
don't remember which one) under SuSE five years ago. I don't remember
if I finally solved it.

> Could this be a port issue when connecting from a client?  It seems
> to me it may be something network related since ftp'ing from
> localhost works flawlessly.

    You have to make sure that you're using the correct range of
ports for passive mode (the same that your OS says you can use. Under
Linux, you can find those under /proc/sys/net/ipv4/ip_local_port_range).

    I must confess that I'm completely lost with your problem. If I
(Continue reading)

Permalink | Reply |

Gmane