> here the message off the non working client:
> Befehl: PWD
> Antwort: 257 "/" is the current directory
> Befehl: TYPE I
> Antwort: 200 Type set to I
> Befehl: PASV
> Antwort: 227 Entering Passive Mode (83,64,113,238,239,178).
> Befehl: LIST
> Fehler: Zeitüberschreitung der Verbindung
> Fehler: Verzeichnisinhalt konnte nicht empfangen werden

> here the working one:
> Command: PWD
> Response: 257 "/" is the current directory
> Command: TYPE A
> Response: 200 Type set to A
> Command: PASV
> Response: 227 Entering Passive Mode (83,64,113,238,235,157).
> Command: LIST
> Response: 150 Opening ASCII mode data connection for file list
> Status: SSL connection established
> Response: 226 Transfer complete

The difference between the two clients is that the non-working client
sends "TYPE I" to the FTP server before the PASV/LIST commands ("TYPE I"
tells the server to use transfer data as type 'binary'); the working
client sends "TYPE A" (for transferring data as type 'ascii', which is
what directory listings are always transferred as) before the PASV/LIST

I tried to reproduce this issue locally using 1.3.2rc2, using both FTP and
FTPS, to no avail. It would be worth seeing your proftpd debug logging,
using debug level 10, for the non-working client:



~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

What is a barrier, an obstacle, but an opportunity for proceeding in a
slighty different direction?

-TJ Saunders

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
ProFTPD Users List
Unsubscribe problems?