"Error loading directory..."

[justindossey]

Hi,

I've written a custom FTP server for my site, and I want it to support the coreFTP client as well as it does all the others my customers use.

Right now, I've noticed two things in my testing:

1. CoreFTP does not connect() to the remote server until after issuing a data retrieval command, i.e. most clients issue PASV, connect(), then issue LIST. CoreFTP LE appears to be issuing PASV, LIST, then connect(). Not a huge deal-- I've already worked around that.

2. Although the server successfully sends the directory listing to coreFTP on a LIST command, coreFTP fails to display the listing, providing only the unhelpful "Error loading directory..." message. How can I find out why coreFTP rejects the listing? It's the standard unix-style listing, and it works with just about everyone else's FTP clients. Is there some debug parameter I can activate in the client?

Example of the session:

Resolving obscured.domain.name.com...
Connect socket #6292 to 999.999.999.66, port 21...
220 Welcome to the FTP server! Please log in.
USER myusername
331 Please specify the password.
PASS **********
230- Welcome to the FTP Server!
230- You may upload, download, and delete files using this interface.
230 Logged in successfully. Proceed.
SYST
200 L8
Keep alive off...
CWD /
250 Command okay
PASV
227 Entering Passive Mode (999,999,999,66,166,242)
LIST
Connect socket #6448 to 999.999.999.66, port 42738...
150 Opening ascii connection for file list
226 Directory send OK.


Error loading directory...
disconnected

[justindossey]

It looks like the "L8" reply to SYST was confusing things. I unchecked Legacy Mode (whatever that does) and changed system type to Unix, and the files look good.