Trace: CFtpControlSocket::SendNextCommand(2)Įrror: Failed to retrieve directory listing Trace: CFtpControlSocket::ResetOperation(2) Trace: ControlSocket.cpp(557): Failed to parse returned path. Trace: CFtpControlSocket::SendNextCommand(0) Trace: CFtpControlSocket::ResetOperation(0) But I hope the explanation above will give you enough information about the problem. Apologies about this, but I'm working in a company where I don't have permission to reveal any information about the systems we use, not even the paths on the server. I edited the log by replacing information with tags, even the path it returns. So the problem is not with the server, even it does use quite unusual directory structure. The problem is that Filezilla doesn't understand the returned path.Įvery command line client on Windows and Linux I have tested work with this server. The PWD command returns the correct path (without leading '/') from the server so the problem is not with the return value from server. So for example if you would connect to a normal Linux server the path could be "/example-path/", but on this server the correct path is "example-path/". I suspect that the listing fails because the path on the server doesn't have the leading '/' character in it. I'm trying to retrieve a directory listing from a ftp server.
Paths without leading '/' character won't work. Tested version: Filezilla 3.0.0-beta7, Windows XP
0 kommentar(er)
