cmariner commented

I am running in to the same problem. INFO. Ftp server is Serv-U. Using Cyberduck 2.6. Tried Passive and Active mode. Cisco Pix Firewall in between client and server.

82bb872 commented

I have the same problem. For me it only happens with FTP connections, not SFTP. I don't think it is related to server configuration or firewall settings, though, as FTP works fine to the same server (wu-ftpd 2.6.2) using the command line client or using Transmit (including using PASV). In the past, FTP to this server worked fine with Cyberduck. I don't know exactly when it stopped working (I generally use SFTP), but the problem occurs now with 2.6.1, 2.6, and 2.5.5 on OS 10.4.7. I get log entries like this (server url and IP address edited out):

613928995 [<ch/cyberduck/core/ftp/FTPSession: 0x136ef3e0>] WARN com.enterprisedt.net.ftp.FTPControlSocket - Forced to close socket Socket[addr=serveraddress.com/xxx.xxx.xxx.xxx,port=21,localport=58995]

5ac05d8 commented

Add another person experiencing this issue. There is an OS X 10.2 FTP server I am trying to connect to that completely fails to work. However, connecting to it via the command line works perfectly still. I get the same type of connection message mentioned by BP.

Console message sans IP numbers:

78740 [<ch/cyberduck/core/ftp/FTPSession: 0x1a9894c0>] WARN com.enterprisedt.net.ftp.FTPControlSocket - Forced to close socket Socket[addr=xxx.xxx.xxx.xxx.transedge.com/xxx.xxx.xxx.xxx,port=21,localport=57221]

Successful command line connects are being generated using the default FTP client in 10.4.7. (lukemftp 1.6-beta2)