Cyberduck Mountain Duck CLI

#2702 closed defect (invalid)

Directory listing broken with Microsoft FTP server

Reported by: danieldickison Owned by: dkocher
Priority: normal Milestone: 3.1
Component: ftp Version: 3.0.3
Severity: normal Keywords:
Cc: Architecture:
Platform:

Description

This seems different from other MS FTP tickets that I found during search..

Connecting to this server shows a completely incorrect directory listing, but I can work with it fine via the command line 'ftp' program. Compare the Cyberduck log to the command line usage below. Note that the 'inc' directory that Cyberduck finds is nowhere to be found when doing an 'ls' from the command line, but there are a bunch of other files listed instead.

I see this bug in 3.0.3 and the latest nightly.

Cyberduck:

220 Microsoft FTP Service
USER aliendan
331 Password required for aliendan.
PASS ********
230 User aliendan logged in.
NOOP
200 NOOP command successful.
SYST
215 Windows_NT
STAT /
213-status of /:
10-29-08  02:45AM       <DIR>          inc
213 End of status.
NOOP
421 Timeout (120 seconds): closing control connection.
220 Microsoft FTP Service
USER aliendan
331 Password required for aliendan.
PASS ********
230 User aliendan logged in.
STAT /inc
213-status of /inc:
10-29-08  02:45AM                 2007 inc_database.asp
10-29-08  02:39AM                 4777 JSON.asp
213 End of status.

Command Line:

220 Microsoft FTP Service
ftp> user
(username) aliendan
331 Password required for aliendan.
Password: 
230 User aliendan logged in.
Remote system type is Windows_NT.
ftp> ls inc
500 'EPSV': command not understood
227 Entering Passive Mode (76,74,254,221,19,137).
125 Data connection already open; Transfer starting.
550 inc: The system cannot find the file specified. 
ftp> pwd
Remote directory: /
ftp> ls /
500 'EPSV': command not understood
227 Entering Passive Mode (76,74,254,221,19,138).
125 Data connection already open; Transfer starting.
07-25-08  07:11AM       <DIR>          _private
07-25-08  07:11AM                 1754 _vti_inf.html
07-25-08  07:11AM       <DIR>          _vti_log
09-18-08  08:03PM                15940 About.asp
09-18-08  07:41PM                13297 AboutPremium.asp
10-10-08  06:55PM                14660 AboutPremium_Join.asp
07-25-08  02:05PM                 7186 AbusePolicy.htm
[snip]
ftp> syst
215 Windows_NT
ftp> stat /
Connected and logged into [snip].com.
No proxy connection.
Gate ftp: off, server (none), port ftpgate.
Passive mode: on; fallback to active mode: on.
Mode: stream; Type: ascii; Form: non-print; Structure: file.
Verbose: on; Bell: off; Prompting: on; Globbing: on.
Store unique: off; Receive unique: off.
Preserve modification times: on.
Case: off; CR stripping: on.
Ntrans: off.
Nmap: off.
Hash mark printing: off; Mark count: 1024; Progress bar: on.
Get transfer rate throttle: off; maximum: 0; increment 1024.
Put transfer rate throttle: off; maximum: 0; increment 1024.
Socket buffer sizes: send 131070, receive 262140.
Use of PORT cmds: on.
Use of EPSV/EPRT cmds for IPv4: on.
Command line editing: on.
Version: tnftp 20050625

Change History (3)

comment:1 Changed on Oct 30, 2008 at 7:05:33 PM by dkocher

Related to #2445.

comment:2 Changed on Oct 30, 2008 at 7:10:27 PM by dkocher

  • Milestone set to 3.1
  • Status changed from new to assigned

Use defaults write ch.sudo.cyberduck ftp.sendStatListCommand false as a workaround as described in the common problems section of the help.

We will have to find a workaround; probably just disabling STAT for servers replying with Windows to SYST.

comment:3 Changed on Nov 2, 2008 at 10:31:55 PM by anonymous

  • Resolution set to invalid
  • Status changed from assigned to closed

Thanks for pointing me to the help which I should've checked first.

This one turned out to be a false alarm in any case: the server admin had instantiated 2 totally separate FTP servers on separate ports, and I was using the wrong port when accessing via Cyberduck. Turns out STAT works perfectly fine on this MS server.

Sorry for the noise.

Note: See TracTickets for help on using tickets.