When upgrading from version 2.5.5 to version 2.6, I could not connect to the remote server.
The FTP server log file when being connected to by the new version of Cyberduck :
Sat Jun 10 00:01:35 2006 0 Incoming connection request on interface xxx.xx.xxx.xx
Sat Jun 10 00:01:35 2006 0 Connection request accepted from xxx.xx.xxx.xx
Sat Jun 10 00:01:35 2006 0 USER brent
Sat Jun 10 00:01:35 2006 0 PASS ***********
Sat Jun 10 00:01:35 2006 0 SYST
Sat Jun 10 00:01:36 2006 0 NOOP
Sat Jun 10 00:01:36 2006 0 CWD /
Sat Jun 10 00:01:36 2006 0 PORT 0,0,0,0,210,156
Sat Jun 10 00:01:36 2006 0 LIST -a
Sat Jun 10 00:01:36 2006 0 The requested address is not valid in its context.
Reverting back to version 2.5.5 of Cyberduck and being able to connect :
Sat Jun 10 00:24:49 2006 9 Incoming connection request on interface xxx.xx.xxx.xx
Sat Jun 10 00:24:49 2006 9 Connection request accepted from xxx.xx.xxx.xx
Sat Jun 10 00:24:50 2006 9 USER brent
Sat Jun 10 00:24:52 2006 9 PASS ***********
Sat Jun 10 00:24:52 2006 9 SYST
Sat Jun 10 00:24:53 2006 9 NOOP
Sat Jun 10 00:24:53 2006 9 CWD /ftp/Nycomed EAR files
Sat Jun 10 00:24:53 2006 9 PORT 82,41,244,236,238,165
Sat Jun 10 00:24:53 2006 9 LIST
Sat Jun 10 00:24:53 2006 9 Data connection established
What do I need to do differently in 2.6 to make it work ?
Cheers,
Brent Harlow
The text was updated successfully, but these errors were encountered:
I just encountered this problem with a Mac I'm setting up for my daughter. Our two Macs are both running Cyberduck 2.6 on a small LAN behind a DSL router. Her Mac is experiencing the "PORT 0,0,0,0,nnn,nnn" problem; mine works fine. The only difference I can find is her Mac is running 10.4.6 and mine is still at 10.4.5.
When upgrading from version 2.5.5 to version 2.6, I could not connect to the remote server.
The FTP server log file when being connected to by the new version of Cyberduck :
Reverting back to version 2.5.5 of Cyberduck and being able to connect :
What do I need to do differently in 2.6 to make it work ?
Cheers,
Brent Harlow
The text was updated successfully, but these errors were encountered: