Using Filezilla 2.2.12c on a Os/2 warp server, Filezilla does not handle correctly use of backslash on a CWD command.
Due to this error it is unusable.
Is there a workaround or a configuration setting for resolve this error ?
Status: Connecting to 10.128.33.1 ...
Status: Connected with 10.128.33.1. Waiting for welcome message...
Response: 220 PC00330000 IBM TCP/IP for OS/2 - FTP Server ver 21:07:16 on Dec 16 1997 ready.
Command: USER ...........
Response: 331 Password required for userid.
Command: PASS ********
Response: 230 User userid logged in.
Command: FEAT
Response: 502 Unknown command.
Command: SYST
Response: 215 OS/2 operating system
Status: Connected
Status: Retrieving directory listing...
Command: PWD
Response: 257 "C:\" is current directory.
Command: PORT 10,128,200,4,11,28
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for C:\.
Response: 226 Transfer complete.
Status: Directory listing successful
Status: Retrieving directory listing...
Command: CWD ibmav
Response: 250 CWD command successful.
Command: PWD
Response: 257 "C:\ibmav" is current directory.
Command: PORT 10,128,200,4,11,29
Response: 200 PORT command successful.
Command: TYPE A
Response: 200 Type set to A.
Command: LIST
Response: 150 Opening ASCII mode data connection for C:\ibmav.
Response: 226 Transfer complete.
Status: Directory listing successful
Command: CWD C:/ibmav/
Response: 550 C:/ibmav/: error 2.
A lot of thanks for your response.
Server OS/2 incorrect handling on slash-backslash
Moderator: Project members
It's not easy to add support for other server types in FileZilla 2.x. Please try out the latest FileZilla 3 nightly from http://filezilla-project.org/nightly.php
It is rewritten from scratch and should handle different server types better. If the auto-detection does not work, you can try to use the Site Manager and specify Dos as server type on the advanced tab.
As sidenode, I always wonder how such servers, especially the IBM ones, could even pass through the most basic testing. It looks as if these servers have never been tested for compatibilty with other ftp clients.
It is rewritten from scratch and should handle different server types better. If the auto-detection does not work, you can try to use the Site Manager and specify Dos as server type on the advanced tab.
As sidenode, I always wonder how such servers, especially the IBM ones, could even pass through the most basic testing. It looks as if these servers have never been tested for compatibilty with other ftp clients.
Well setting host type as DOS, active transfer mode and limiting to 1 the concurrent connection number Filezilla 3 work.botg wrote:It's not easy to add support for other server types in FileZilla 2.x. Please try out the latest FileZilla 3 nightly from http://filezilla-project.org/nightly.php
It is rewritten from scratch and should handle different server types better. If the auto-detection does not work, you can try to use the Site Manager and specify Dos as server type on the advanced tab.
As sidenode, I always wonder how such servers, especially the IBM ones, could even pass through the most basic testing. It looks as if these servers have never been tested for compatibilty with other ftp clients.