-
Lauri
Guest
2009-02-14 08:38
I just downloaded WinSCP. I’ve tried and tried to get it to connect to the server, but it doesn’t work. I’ve been through the FAQ and all but couldn’t find anything to help. This is the error message that I get:
Timeout detected.
Could not retrieve directory listing
Opening ASCII mode data connection for /bin/ls.
Error listing directory ‘/’.
Can you help me?
Reply with quote
Advertisement
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,466
- Location:
- Prague, Czechia
2009-02-17
Please read documentation. If that does not help, come back.
Reply with quote
-
Lauri
Guest
2009-02-22 18:54
I’m not sure what you wanted me to see in the documentation. I’ve uninstalled and re-installed, checked and double checked my settings, host name, passwords, etc., tried both passive and active, and still cannot get through to the server. Here’s the error message I’m getting now:
Could not retrieve directory listing
Can’t open data connection.
It says that it is connected but each time it tries to retrieve the directory it fails. I know that other people are getting through to this server with WinSCP – what is going wrong for me?
Please HELP!
Reply with quote
-
martin◆
Site Admin -
2009-02-23
Please post a full log file showing failure with passive mode.
Reply with quote
-
Lauri
Guest
2009-02-24 04:21
SYST 215 Windows_NT FEAT 211-FEAT SIZE MDTM 211 END Connected -------------------------------------------------------------------------- Using FTP protocol. Doing startup conversation with host. PWD 257 "/" is current directory. Getting current directory name. Retrieving directory listing... TYPE A 200 Type set to A. PORT 192,168,1,47,15,209 200 PORT command successful. LIST -a 150 Opening ASCII mode data connection for /bin/ls. 425 Can't open data connection. Could not retrieve directory listing Retrieving directory listing... TYPE A 200 Type set to A. PORT 192,168,1,47,15,211 200 PORT command successful. LIST 150 Opening ASCII mode data connection for /bin/ls. 425 Can't open data connection. Could not retrieve directory listing (ECommand) Error listing directory '/'. Could not retrieve directory listing Can't open data connection. Startup conversation with host finished. TYPE A 200 Type set to A. TYPE A 200 Type set to A.
Reply with quote
Advertisement
-
martin◆
Site Admin -
2009-02-25
You haven’t posted full log file, so I cannot tell for sure. But from the IP address I suspect this issue is what you are facing.
Reply with quote
-
Lauri
Guest
2009-02-25 21:06
Please explain to me how to get the full log file. Or explain how I can fix this problem.
Reply with quote
-
martin◆
Site Admin -
2009-02-27
@Lauri: You cannot fix it. But the problem is tracked already, so it will be resolved eventually.
Reply with quote
- Guest
2010-04-08 23:08
@Lauri: Are you using PASSIVE (PASV
) connection? If so, you’ll need to configure your client accordingly and ensure the proper PASV
ports are open on your firewall if you are accessing your FTP server through one. FTP server admin, if other than you, will know the PASSIVE port range.
Reply with quote
Advertisement
-
grouver
Guest
2011-01-04 15:36
Hi, this is a bit old however the problem is STILL not solved. It has been getting on my nerves for a while and if there were decent free Windows FTP clients I would have given up on WinSCP a long time ago. Anyway, my rants aside, here is a work around that you might find useful. If you notice, the error message usually suggests that you try passive mode due to inability to open some port. Now there might be any reasons why a port cannot be opened and WinSCP cannot really change that. Nonetheless the software should be able to automatically switch to a passive connection which it currently most definitely does not do.
You have to tick the passive connection box. The way you do this is tick the Advanced options box. Then under Connection tick the passive one. I also selected IPv4 as the internet protocol (might not work in your case) and under Environment > FTP ticked the Force IP … option. I’d suggest you save all that as a session and reuse the setting next time. If you are editing a saved session make sure that you save.
Hope this helps!
Reply with quote
-
martin◆
Site Admin -
2011-01-05
Since 4.3 the passive mode is the default one.
Reply with quote
-
lmstearn
Guest
2011-02-26 05:06
Had a problem with this for years.
Forgive my «layman’s» jargon.
Previous dialogues with site Admin & Tech personnel tried to locate a «problem» with my modem. That ceased when exactly the same «problem» arose with a different ADSL2 modem.
Was a problem then with my broadband connection, which used a shared, not dedicated, address at the exchange.
However, the problem was *only* with remote servers run on Microsoft Windows and was dated to a server upgrade ~3.5 years ago.
Other remote servers e.g. Unix didn’t care
Once I changed providers, the problem disappeared altogether.
Until now.
It seems to be a connection speed? issue. I have blown my 2 gigabyte allocation and the transfer speed slows to around 7 kbs.
Logging on to the remote Microsoft Windows FTP server I got no timeout message but:
Could not retrieve directory listing -Can’t open data connection
I deselected passive mode and removed permanent caching and, bingo, got in.
Hope this helps,
Laurie
Reply with quote
- Guest
2011-02-26 05:15
Re above, deselecting passive mode,
«Auto» is greyed out, but neither IPv4 nor IPv6 are selected.
What’s the story there?
Cheers
Laurie
Reply with quote
Advertisement
-
Hari
Guest
2011-07-13 11:23
I am getting this error «Can’t open data connection». please find the log file below
. 2011-07-13 12:45:13.218 -------------------------------------------------------------------------- . 2011-07-13 12:45:13.218 WinSCP Version 4.3.3 (Build 1340) (OS 5.1.2600 Service Pack 3) . 2011-07-13 12:45:13.218 Configuration: HKEY_CURRENT_USERSoftwareMartin PrikrylWinSCP 2 . 2011-07-13 12:45:13.218 Login time: Wednesday, July 13, 2011 12:45:13 PM . 2011-07-13 12:45:13.218 -------------------------------------------------------------------------- . 2011-07-13 12:45:13.218 Session name: CambridgeAssessment@ftps.vizual.co.uk (Ad-Hoc session) . 2011-07-13 12:45:13.218 Host name: ftps.vizual.co.uk (Port: 990) . 2011-07-13 12:45:13.218 User name: CambridgeAssessment (Password: Yes, Key file: No) . 2011-07-13 12:45:13.218 Tunnel: No . 2011-07-13 12:45:13.218 Transfer Protocol: FTP . 2011-07-13 12:45:13.218 Ping type: C, Ping interval: 30 sec; Timeout: 15 sec . 2011-07-13 12:45:13.218 Proxy: none . 2011-07-13 12:45:13.218 FTP: FTPS: Implicit SSL/TLS; Passive: Yes [Force IP: No] . 2011-07-13 12:45:13.218 Local directory: default, Remote directory: home, Update: No, Cache: Yes . 2011-07-13 12:45:13.218 Cache directory changes: Yes, Permanent: Yes . 2011-07-13 12:45:13.218 DST mode: 1 . 2011-07-13 12:45:13.218 -------------------------------------------------------------------------- . 2011-07-13 12:45:13.890 Connecting to ftps.vizual.co.uk:990 ... . 2011-07-13 12:45:14.031 Connected with ftps.vizual.co.uk:990, negotiating SSL connection... . 2011-07-13 12:45:14.406 SSL connection established. Waiting for welcome message... < 2011-07-13 12:45:14.406 220 WELCOME TO FTPS.VIZUAL.CO.UK Vizual Business Tools Secure FTP Site ======== > 2011-07-13 12:45:14.406 USER CambridgeAssessment < 2011-07-13 12:45:14.593 331 Password required for cambridgeassessment > 2011-07-13 12:45:14.593 PASS ************************** < 2011-07-13 12:45:14.765 230 Logged on > 2011-07-13 12:45:14.765 SYST < 2011-07-13 12:45:14.937 215 UNIX emulated by FileZilla > 2011-07-13 12:45:14.937 FEAT < 2011-07-13 12:45:15.125 211-Features: < 2011-07-13 12:45:15.125 MDTM < 2011-07-13 12:45:15.125 REST STREAM < 2011-07-13 12:45:15.125 SIZE < 2011-07-13 12:45:15.125 MLST type*;size*;modify*; < 2011-07-13 12:45:15.125 MLSD < 2011-07-13 12:45:15.125 AUTH SSL < 2011-07-13 12:45:15.125 AUTH TLS < 2011-07-13 12:45:15.125 PROT < 2011-07-13 12:45:15.125 PBSZ < 2011-07-13 12:45:15.125 UTF8 < 2011-07-13 12:45:15.125 CLNT < 2011-07-13 12:45:15.125 MFMT < 2011-07-13 12:45:15.140 211 End > 2011-07-13 12:45:15.140 PBSZ 0 < 2011-07-13 12:45:15.312 200 PBSZ=0 > 2011-07-13 12:45:15.312 PROT P < 2011-07-13 12:45:15.484 200 Protection level set to P . 2011-07-13 12:45:15.484 Connected . 2011-07-13 12:45:15.484 -------------------------------------------------------------------------- . 2011-07-13 12:45:15.500 Using FTP protocol. . 2011-07-13 12:45:15.500 Doing startup conversation with host. > 2011-07-13 12:45:15.515 PWD < 2011-07-13 12:45:15.687 257 "/" is current directory. . 2011-07-13 12:45:15.687 Getting current directory name. . 2011-07-13 12:45:15.703 Retrieving directory listing... > 2011-07-13 12:45:15.703 TYPE A < 2011-07-13 12:45:15.875 200 Type set to A > 2011-07-13 12:45:15.890 PASV < 2011-07-13 12:45:16.078 227 Entering Passive Mode (172,16,18,6,195,83) > 2011-07-13 12:45:16.078 LIST -a < 2011-07-13 12:45:26.609 425 Can't open data connection. . 2011-07-13 12:45:26.609 Could not retrieve directory listing . 2011-07-13 12:45:26.625 Retrieving directory listing... > 2011-07-13 12:45:26.625 TYPE A < 2011-07-13 12:45:26.796 200 Type set to A > 2011-07-13 12:45:26.796 PASV < 2011-07-13 12:45:26.984 227 Entering Passive Mode (172,16,18,6,195,84) > 2011-07-13 12:45:26.984 LIST < 2011-07-13 12:45:37.609 425 Can't open data connection. . 2011-07-13 12:45:37.609 Could not retrieve directory listing * 2011-07-13 12:45:37.609 (ECommand) Error listing directory '/'. * 2011-07-13 12:45:37.609 Could not retrieve directory listing * 2011-07-13 12:45:37.609 Can't open data connection.
Reply with quote
-
user
Guest
2011-07-13 11:29
find the new one
> 2011-07-13 12:45:14.765 SYST < 2011-07-13 12:45:14.937 215 UNIX emulated by FileZilla > 2011-07-13 12:45:14.937 FEAT < 2011-07-13 12:45:15.125 211-Features: < 2011-07-13 12:45:15.125 MDTM < 2011-07-13 12:45:15.125 REST STREAM < 2011-07-13 12:45:15.125 SIZE < 2011-07-13 12:45:15.125 MLST type*;size*;modify*; < 2011-07-13 12:45:15.125 MLSD < 2011-07-13 12:45:15.125 AUTH SSL < 2011-07-13 12:45:15.125 AUTH TLS < 2011-07-13 12:45:15.125 PROT < 2011-07-13 12:45:15.125 PBSZ < 2011-07-13 12:45:15.125 UTF8 < 2011-07-13 12:45:15.125 CLNT < 2011-07-13 12:45:15.125 MFMT < 2011-07-13 12:45:15.140 211 End > 2011-07-13 12:45:15.140 PBSZ 0 < 2011-07-13 12:45:15.312 200 PBSZ=0 > 2011-07-13 12:45:15.312 PROT P < 2011-07-13 12:45:15.484 200 Protection level set to P . 2011-07-13 12:45:15.484 Connected . 2011-07-13 12:45:15.484 -------------------------------------------------------------------------- . 2011-07-13 12:45:15.500 Using FTP protocol. . 2011-07-13 12:45:15.500 Doing startup conversation with host. > 2011-07-13 12:45:15.515 PWD < 2011-07-13 12:45:15.687 257 "/" is current directory. . 2011-07-13 12:45:15.687 Getting current directory name. . 2011-07-13 12:45:15.703 Retrieving directory listing... > 2011-07-13 12:45:15.703 TYPE A < 2011-07-13 12:45:15.875 200 Type set to A > 2011-07-13 12:45:15.890 PASV < 2011-07-13 12:45:16.078 227 Entering Passive Mode (172,16,18,6,195,83) > 2011-07-13 12:45:16.078 LIST -a < 2011-07-13 12:45:26.609 425 Can't open data connection. . 2011-07-13 12:45:26.609 Could not retrieve directory listing . 2011-07-13 12:45:26.625 Retrieving directory listing... > 2011-07-13 12:45:26.625 TYPE A < 2011-07-13 12:45:26.796 200 Type set to A > 2011-07-13 12:45:26.796 PASV < 2011-07-13 12:45:26.984 227 Entering Passive Mode (172,16,18,6,195,84) > 2011-07-13 12:45:26.984 LIST < 2011-07-13 12:45:37.609 425 Can't open data connection. . 2011-07-13 12:45:37.609 Could not retrieve directory listing * 2011-07-13 12:45:37.609 (ECommand) Error listing directory '/'. * 2011-07-13 12:45:37.609 Could not retrieve directory listing * 2011-07-13 12:45:37.609 Can't open data connection.
Reply with quote
-
martin◆
Site Admin -
2011-07-14
Can you try to enable Force IP address for passive mode connections?
https://winscp.net/eng/docs/ui_login_ftp
Reply with quote
-
ok
Guest
2013-04-08 18:29
unable to access
Reply with quote
Advertisement
-
martin◆
Site Admin -
2015-04-08
Reply with quote
-
Daniel D
Guest
2016-06-08 08:52
Try disabling passive mode. Probably not all FTP passive ports are not opened.
For example these all ports must be allowed to use passive mode.
Response: 227 Entering Passive Mode (202,234,195,227,219,190).
Reply with quote
-
martin◆
Site Admin -
- Joined:
- 2002-12-10
- Posts:
- 38,466
- Location:
- Prague, Czechia
2016-06-09
For example these all ports must be allowed to use passive mode.
Response: 227 Entering Passive Mode (202,234,195,227,219,190).
This is bit confusing. The numbers in the 227 response are not port numbers! Only the 219
and 190
represent a port number 56254 (219 * 256 + 190). The 202,234,195,227
is an IP address. So there’s only one port number in the message.
Reply with quote
-
Charl
Guest
2017-05-04 14:27
Hi All,
This could be caused if the server is in active mode and not in passive mode
Reply with quote
Advertisement
- Fizzy
- Joined:
- 2019-02-05
- Posts:
- 1
- Location:
- Srilanka
2019-02-05 12:38
Hi,
I am facing this same issue am assuming if it’s because the data channel ports 5000-5005 which i have updated the firewall settings which aren’t open, It connects to the FTP successfully but does not list the folders under the FTP drive created.
Timeout detected. (data connection)
Could not retrieve directory listing
Error listing directory ‘/’.
Appreciate your input in this regard.
Thanks,
Fazil
Reply with quote E-mail
-
martin◆
Site Admin -
2019-02-17
@Fizzy: Sorry, I do not understand. Can you try to describe your problem again?
Also, can you retrieve the listing using any other FTP client?
Reply with quote
- anotherusername
- Joined:
- 2018-07-18
- Posts:
- 1
- Location:
- Earth
2019-10-15 00:34
After messing around for ages and reading all the useless advice – this is what fixed it for me.
I am using Plesk FTP server with WinSCP connecting on port 21 Passive.
So in Sire settings – Go Advanced > Then FTP under Environment.
Change the following commands that used to be set to AUTO
Use MLSD command — On
Force IP for passive — On
Use HOST command — On
Boom then everything worked.
Reply with quote
- fometeo
- Joined:
- 2020-02-29
- Posts:
- 3
- Location:
- Portugal
2020-03-27 17:01
On a recent case the problem was not the lack of FTP server support for MSLD as log seemed to show cause the connection was lost just after MSLD trying to get the dir listed. The Linux vsftpd server was good:
at file /etc/vsftpd/vsftpd.conf
it had both active and passive services OK
connect_from_port_20=YES pasv_enable=YES
The issue did not happen all the times, sometimes the connection was established (!)
This was a CentOS 7 policy (SELinux) issue solved by
setsebool -P ftpd_connect_all_unreserved 1
or just disabling SElinux
By the way old Windows up to version 8 had ftp.exe
supporting only active FTP.
Reply with quote
Advertisement
-
sarawgeek
Guest
2021-08-20 06:43
For me it was a VPN issue, server was blocking the IP so it was not allowing the directory listing, just check if you something similar kind of setup.
I was trying to connect from USA and server was in India, so may that is why it was blocking for security purpose.
Reply with quote
Advertisement
I’m running a FreeDos v1.1 VirtualBox guest on a Windows 7 64-bit host. Today I ran mTCP’s ftpsrv.exe for FTP access and FTP’d into FreeDos using WinSCP. It started me in my last accessed directory, which was /DRIVE_C/RR2
. I browsed to the root directory (/DRIVE_C
) and uploaded a small file. After the file transfer completed, WinSCP hanged on the file transfer before telling me the connection was broken and that it failed to retrieve the directory listing:
Timeout detected. (data connection)
Could not retrieve directory listing
Error listing directory ‘/DRIVE_C’.
Initially I thought there had been a disk error, but the file was successfully uploaded and everything else seemed to be in order.
Trying to reconnect, however, results in the same error. Clearing the remote directory setting from WinSCP solves nothing. I created a new user and logging in that way still received the same error.
What I can do is manually specify the starting directory to almost any subdirectory other than /DRIVE_C
or /DRIVE_C/FDOS
. Directories are randomly «not found,» causing WinSCP to disconnect, and WinSCP will randomly choke and disconnect while transferring files. Sometimes I can copy a file in FreeDOS to a different location then download it via FTP, but sometimes not. Uploading a file will usually render its directory invisible to FTP.
The VM has a 2GB disk and is half empty, so the disk isn’t low on space.
After wasting hours trying to troubleshoot this, I finally said «screw it» and installed a FreeDOS 1.2 VM guest. I downloaded as many games files as I could from my FreeDos 1.1 VM, then started uploading them to my new FreeDOS 1.2 VM. I decided to put the game files under /DRIVE_C/GAMES/
and drag-n-dropped them from my host to the guest via WinSCP. WinSCP timed out and resumed a few times before choking on a directory listing error and then quitting with an «abnormal execution» error. I can no longer access /DRIVE_C/GAMES/
via FTP (but have no problem when working directly on the system).
Here’s my ftpsrv user setup on both FreeDOS VMs:
# userid password sandbox_directory incoming_directory permissions
redacted redacted [none] [any] all
According to this, my login should have full access with no restrictions.
mTCP configuration on FreeDOS 1.1 (mostly default settings)
packetint 0x60
mtu 1472
DOSRules
ftpsrv_password_file c:FDOSftppass.txt
ftpsrv_log_file c:FDOSftpsrv.log
ftpsrv_filebuffer_size 16
ftpsrv_tcpbuffer_size 16
ftpsrv_packets_per_roll 2
mTCP configuration on FreeDOS 1.2 (mostly default settings)
packetint 0x60
mtu 1500
DOSRules
ftpsrv_password_file c:FDOSftppass.txt
ftpsrv_log_file c:FDOSftpsrv.log
# I forgot to uncomment these, but seems to have made no difference
#ftpsrv_filebuffer_size 16
#ftpsrv_tcpbuffer_size 16
#ftpsrv_packets_per_roll 2
I somehow doubt WinSCP is the culprit here, even though interacting with mTCP seems to be making it wonky. I use WinSCP nearly every day to connect to other systems, and I’ve never encountered this kind of behavior.
WinSCP configuration for both connections:
Protocol: FTP
Encryption: No encryption
Port number: 21
UTF-8 encoding for filenames: Auto
[ ] Trim VMS version numbers
[ ] Synchronize browsing
[x] Remember last used directory
(turning this off didn’t help)
[x] Cache visited remote directories
[x] Cache directory changes
[x] Permanent cache
[x] Resolve symbolic links
[ ] Follow symbolic links to directories
[ ] Preserve deleted files to recycle bin
[x] Passive mode
Protocal options: All auto
Server response timeout: 15
Keepalives: Executing dummy protocol commands
Seconds between keepalives: 30
Internet protocol version: Auto
Proxy type: None
I’m inclined to believe the fault lies in an OS permission setting. I can however find no documentation about file permissions in FreeDos. The closest I can find is attributes, which gives me the following information (on FreeDOS 1.1):
[D----] FDOS
[----A] KERNAL.SYS
[----A] AUTOEXEC.BAT
[----A] COMMAND.COM
[----A] FDCONFIG.SYS
[----A] BOOTSECT.BIN
[D----] DUKE3D
[D----] RR2
which clearly have nothing to do with permissions.
Update 2017.04.03: As requested, here are my log files. (WinSCP wasn’t logging, so this is from this morning.)
Log file from WinSCP:
. 2017-04-03 10:22:22.641 --------------------------------------------------------------------------
. 2017-04-03 10:22:22.642 WinSCP Version 5.9.4 (Build 7333) (OS 6.1.7601 Service Pack 1 - Windows 7 Professional)
. 2017-04-03 10:22:22.643 Configuration: C:UsersRedactedAppDataRoamingwinscp.ini
. 2017-04-03 10:22:22.643 Log level: Normal
. 2017-04-03 10:22:22.643 Local account: Redacted
. 2017-04-03 10:22:22.644 Working directory: C:UsersRedacted
. 2017-04-03 10:22:22.644 Process ID: 7508
. 2017-04-03 10:22:22.644 Command-line: "C:Windowswinscp.exe"
. 2017-04-03 10:22:22.644 Time zone: Current: GMT-6, Standard: GMT-7 (Mountain Standard Time), DST: GMT-6 (Mountain Daylight Time), DST Start: 3/12/2017, DST End: 11/5/2017
. 2017-04-03 10:22:22.644 Login time: Monday, April 03, 2017 10:22:22 AM
. 2017-04-03 10:22:22.644 --------------------------------------------------------------------------
. 2017-04-03 10:22:22.644 Session name: FreeDos 1.1 (Modified site)
. 2017-04-03 10:22:22.644 Host name: 192.168.1.123 (Port: 21)
. 2017-04-03 10:22:22.644 User name: redacted (Password: No, Key file: No, Passphrase: No)
. 2017-04-03 10:22:22.644 Transfer Protocol: FTP
. 2017-04-03 10:22:22.644 Ping type: Dummy, Ping interval: 30 sec; Timeout: 5 sec
. 2017-04-03 10:22:22.644 Disable Nagle: No
. 2017-04-03 10:22:22.644 Proxy: None
. 2017-04-03 10:22:22.644 Send buffer: 262144
. 2017-04-03 10:22:22.644 UTF: Auto
. 2017-04-03 10:22:22.644 FTPS: None [Client certificate: No]
. 2017-04-03 10:22:22.645 FTP: Passive: Yes [Force IP: Auto]; MLSD: Auto [List all: Auto]; HOST: Auto
. 2017-04-03 10:22:22.645 Local directory: C:TEMPFdDOS, Remote directory: /DRIVE_C/UP, Update: Yes, Cache: Yes
. 2017-04-03 10:22:22.645 Cache directory changes: Yes, Permanent: Yes
. 2017-04-03 10:22:22.645 Recycle bin: Delete to: No, Overwritten to: No, Bin path:
. 2017-04-03 10:22:22.645 Timezone offset: 0h 0m
. 2017-04-03 10:22:22.645 --------------------------------------------------------------------------
. 2017-04-03 10:22:22.774 Connecting to 192.168.1.123 ...
. 2017-04-03 10:22:22.774 Connected with 192.168.1.123. Waiting for welcome message...
< 2017-04-03 10:22:22.774 220 mTCP FTP Server
> 2017-04-03 10:22:22.774 USER redacted
< 2017-04-03 10:22:22.775 331 User OK, send Password
> 2017-04-03 10:22:26.075 PASS ********
< 2017-04-03 10:22:26.281 230 User logged in
> 2017-04-03 10:22:26.281 SYST
< 2017-04-03 10:22:26.281 215 UNIX Type: L8
> 2017-04-03 10:22:26.281 FEAT
< 2017-04-03 10:22:26.282 211-mTCP FTP server features:
< 2017-04-03 10:22:26.282 MDTM
< 2017-04-03 10:22:26.282 211 End
. 2017-04-03 10:22:26.327 Connected
. 2017-04-03 10:22:26.327 --------------------------------------------------------------------------
. 2017-04-03 10:22:26.327 Using FTP protocol.
. 2017-04-03 10:22:26.329 Doing startup conversation with host.
> 2017-04-03 10:22:26.379 PWD
< 2017-04-03 10:22:26.380 257 "/" is current directory
. 2017-04-03 10:22:26.380 Changing directory to "/DRIVE_C/UP".
> 2017-04-03 10:22:26.380 CWD /DRIVE_C/UP
< 2017-04-03 10:22:26.381 250 CWD command successful
. 2017-04-03 10:22:26.381 Getting current directory name.
> 2017-04-03 10:22:26.381 PWD
< 2017-04-03 10:22:26.381 257 "/DRIVE_C/UP/" is current directory
. 2017-04-03 10:22:26.581 Retrieving directory listing...
> 2017-04-03 10:22:26.581 TYPE A
< 2017-04-03 10:22:26.581 200 Type set to A
> 2017-04-03 10:22:26.582 PASV
< 2017-04-03 10:22:26.582 227 Entering Passive Mode (192,168,1,123,8,42)
> 2017-04-03 10:22:26.582 LIST -a
. 2017-04-03 10:22:26.582 Connecting to 192.168.1.123:2090 ...
< 2017-04-03 10:22:26.583 150 Sending file list
. 2017-04-03 10:22:26.583 Data connection closed
. 2017-04-03 10:22:26.583 <Empty directory listing>
< 2017-04-03 10:22:26.584 226 Transfer complete
. 2017-04-03 10:22:26.584 Directory listing successful
. 2017-04-03 10:22:26.584 LIST with -a switch returned empty directory listing, will try pure LIST
. 2017-04-03 10:22:26.584 Retrieving directory listing...
> 2017-04-03 10:22:26.584 TYPE A
< 2017-04-03 10:22:26.584 200 Type set to A
> 2017-04-03 10:22:26.585 PASV
< 2017-04-03 10:22:26.585 227 Entering Passive Mode (192,168,1,123,8,91)
> 2017-04-03 10:22:26.585 LIST
. 2017-04-03 10:22:26.585 Connecting to 192.168.1.123:2139 ...
< 2017-04-03 10:22:26.586 150 Sending file list
. 2017-04-03 10:22:26.586 Data connection closed
. 2017-04-03 10:22:26.586 <Empty directory listing>
< 2017-04-03 10:22:26.586 226 Transfer complete
. 2017-04-03 10:22:26.586 Directory listing successful
. 2017-04-03 10:22:26.587 ..;D;0;1899-12-30T07:00:00.000Z;0;"" [0];"" [0];---------;0
. 2017-04-03 10:22:26.681 Startup conversation with host finished.
. 2017-04-03 10:22:30.251 Cached directory change via ".." to "/DRIVE_C".
. 2017-04-03 10:22:30.251 Getting current directory name.
. 2017-04-03 10:22:30.254 Retrieving directory listing...
> 2017-04-03 10:22:30.254 CWD /DRIVE_C/
< 2017-04-03 10:22:30.254 250 CWD command successful
> 2017-04-03 10:22:30.254 PWD
< 2017-04-03 10:22:30.254 257 "/DRIVE_C/" is current directory
> 2017-04-03 10:22:30.254 TYPE A
< 2017-04-03 10:22:30.254 200 Type set to A
> 2017-04-03 10:22:30.254 PASV
< 2017-04-03 10:22:30.254 227 Entering Passive Mode (192,168,1,123,11,61)
> 2017-04-03 10:22:30.254 LIST
. 2017-04-03 10:22:30.254 Connecting to 192.168.1.123:2877 ...
< 2017-04-03 10:22:30.256 150 Sending file list
. 2017-04-03 10:22:30.256 Data connection closed
< 2017-04-03 10:22:30.256 226 Transfer complete
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Jul 14 2016 FDOS
. 2017-04-03 10:22:30.256 -rwxrwxrwx 1 ftp ftp 45344 Jun 21 2011 KERNEL.SYS
. 2017-04-03 10:22:30.256 -rwxrwxrwx 1 ftp ftp 1266 Apr 2 06:26 AUTOEXEC.BAT
. 2017-04-03 10:22:30.256 -rwxrwxrwx 1 ftp ftp 66945 Aug 28 2006 COMMAND.COM
. 2017-04-03 10:22:30.256 -rwxrwxrwx 1 ftp ftp 848 Jul 14 2016 FDCONFIG.SYS
. 2017-04-03 10:22:30.256 -rwxrwxrwx 1 ftp ftp 512 Jul 14 2016 BOOTSECT.BIN
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Jul 14 2016 RR
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Jul 14 2016 ATOMIC
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Jul 14 2016 DUKE3D
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Jul 30 2016 RR2
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Aug 9 2016 HUNT
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Apr 2 08:13 TEST
. 2017-04-03 10:22:30.256 -rwxrwxrwx 1 ftp ftp 527 Apr 2 07:09 README.TXT
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Apr 2 18:23 DCINST
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Apr 2 18:26 DUKEDC
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Apr 2 18:36 ERR200
. 2017-04-03 10:22:30.256 drwxrwxrwx 1 ftp ftp 0 Apr 2 18:39 UP
. 2017-04-03 10:22:30.256 -rwxrwxrwx 1 ftp ftp 161 Apr 2 18:44 GAMER.INI
. 2017-04-03 10:22:30.266 Directory listing successful
. 2017-04-03 10:22:30.266 ..;D;0;1899-12-30T07:00:00.000Z;0;"" [0];"" [0];---------;0
. 2017-04-03 10:22:30.266 FDOS;D;0;2016-07-14T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.266 KERNEL.SYS;-;45344;2011-06-21T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.266 AUTOEXEC.BAT;-;1266;2017-04-02T12:26:00.000Z;1;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.266 COMMAND.COM;-;66945;2006-08-28T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.266 FDCONFIG.SYS;-;848;2016-07-14T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.266 BOOTSECT.BIN;-;512;2016-07-14T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 RR;D;0;2016-07-14T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 ATOMIC;D;0;2016-07-14T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 DUKE3D;D;0;2016-07-14T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 RR2;D;0;2016-07-30T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 HUNT;D;0;2016-08-09T06:00:00.000Z;2;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 TEST;D;0;2017-04-02T14:13:00.000Z;1;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 README.TXT;-;527;2017-04-02T13:09:00.000Z;1;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 DCINST;D;0;2017-04-03T00:23:00.000Z;1;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 DUKEDC;D;0;2017-04-03T00:26:00.000Z;1;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 ERR200;D;0;2017-04-03T00:36:00.000Z;1;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 UP;D;0;2017-04-03T00:39:00.000Z;1;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:30.267 GAMER.INI;-;161;2017-04-03T00:44:00.000Z;1;"ftp" [0];"ftp" [0];rwxrwxrwx;1
. 2017-04-03 10:22:34.312 Cached directory change via "FDOS" to "/DRIVE_C/FDOS".
. 2017-04-03 10:22:34.312 Getting current directory name.
. 2017-04-03 10:22:34.316 Retrieving directory listing...
> 2017-04-03 10:22:34.316 CWD /DRIVE_C/FDOS/
< 2017-04-03 10:22:34.317 250 CWD command successful
> 2017-04-03 10:22:34.317 PWD
< 2017-04-03 10:22:34.317 257 "/DRIVE_C/FDOS/" is current directory
> 2017-04-03 10:22:34.317 TYPE A
< 2017-04-03 10:22:34.317 200 Type set to A
> 2017-04-03 10:22:34.317 PASV
< 2017-04-03 10:22:34.317 227 Entering Passive Mode (192,168,1,123,9,182)
> 2017-04-03 10:22:34.317 LIST
. 2017-04-03 10:22:34.317 Connecting to 192.168.1.123:2486 ...
< 2017-04-03 10:22:34.317 150 Sending file list
< 2017-04-03 10:22:34.317 226 Transfer complete
. 2017-04-03 10:22:39.872 Timeout detected. (data connection)
. 2017-04-03 10:22:39.872 Could not retrieve directory listing
. 2017-04-03 10:22:39.872 Connection was lost, asking what to do.
. 2017-04-03 10:22:39.872 Asking user:
. 2017-04-03 10:22:39.872 Lost connection. ("Timeout detected. (data connection)","Could not retrieve directory listing")
* 2017-04-03 10:22:41.881 (ESshFatal) **Lost connection.**
* 2017-04-03 10:22:41.881 Timeout detected. (data connection)
* 2017-04-03 10:22:41.881 Could not retrieve directory listing
* 2017-04-03 10:22:41.881 Error listing directory '/DRIVE_C/FDOS'.
* 2017-04-03 10:22:41.881 Error changing directory to 'FDOS'.
Log file from mTCP on FreeDOS 1.1
2017-04-03 10:17:37.40 mTCP FtpSrv version (Oct 29 2011) starting
2017-04-03 10:17:37.40 Clients: 3, Client file buffer size: 16384, TCP buffer size: 16384
2017-04-03 10:17:37.40 Packets per poll: 2, TCP sockets: 10, Send buffers: 15, Recv buffers: 40
2017-04-03 10:17:37.40 Client session timeout: 182 seconds
2017-04-03 10:17:37.40 Control port: 21, Pasv ports: 2048-3071
2017-04-03 10:17:37.46 Real IP address: 192.168.1.123, Pasv response IP addr: 192.168.1.123
2017-04-03 10:17:49.65 (0) User redacted signed in from 192.168.1.147:51304 at 2017-04-03 10:17:44
2017-04-03 10:18:09.31 (0) Disconnect: 192.168.1.147:51304
2017-04-03 10:22:23.84 (1) User redacted signed in from 192.168.1.147:51316 at 2017-04-03 10:22:20
2017-04-03 10:22:37.62 (1) Disconnect: 192.168.1.147:51316
2017-04-03 10:36:36.83 (2) User redacted signed in from 192.168.1.147:51365 at 2017-04-03 10:36:33
2017-04-03 10:36:51.39 (2) Disconnect: 192.168.1.147:51365
2017-04-03 10:36:55.83 Shutdown requested
2017-04-03 10:36:56.88 Stats: Sessions: 3 Timeouts: 0
2017-04-03 10:36:56.88 LIST: 11 NLST: 0 RETR: 0
2017-04-03 10:36:56.88 STOR: 0 STOU: 0 APPE: 0
2017-04-03 10:36:56.88 === Server shutdown ===
Update: I tried with Core FTP, and here’s its log:
Welcome to Core FTP, release ver 2.2, build 1887 (x64) -- © 2003-2016
WinSock 2.0
Mem -- 33,531,236 KB, Virt -- 8,589,934,464 KB
Started on Monday April 03, 2017 at 11:36:AM
Connect socket #752 to 192.168.1.123, port 21...220 mTCP FTP Server
USER redacted
331 User OK, send Password
PASS **********
230 User logged in
SYST
215 UNIX Type: L8
Keep alive off...PWD
257 "/" is current directory
PASV
227 Entering Passive Mode (192,168,1,123,10,76)
LIST
Connect socket #800 to 192.168.1.123, port 2636...150 Sending file list
226 Transfer complete
Transferred 54 bytes in 60.000 seconds
CWD /DRIVE_C
250 CWD command successful
PASV
227 Entering Passive Mode (192,168,1,123,9,147)
LIST
Connect socket #844 to 192.168.1.123, port 2451...150 Sending file list
226 Transfer complete
Transferred 1,028 bytes in 60.001 seconds
CWD /DRIVE_C/FDOS/
250 CWD command successful
PASV
227 Entering Passive Mode (192,168,1,123,8,41)
LIST
Connect socket #960 to 192.168.1.123, port 2089...150 Sending file list
226 Transfer complete
Transferred 1,279 bytes in 0.001 seconds
CDUP
250 CWD command successful
PWD
257 "/DRIVE_C/" is current directory
PASV
227 Entering Passive Mode (192,168,1,123,8,67)
LIST
Connect socket #972 to 192.168.1.123, port 2115...150 Sending file list
226 Transfer complete
Transferred 1,028 bytes in 60.001 seconds
QUIT
221 Server closing connection
Total uploaded files: 0
Total uploaded data: 0
Total downloaded files: 0
Total downloaded data: 0
As you can see, it took just over 60 seconds to retrieve 54 bytes of directory information. Core FTP seems to be more successful, in that it eventually gets the directory listing. Some times it works quickly like you would expect FTP to, like when it transferred 1,279 bytes in 0.001 seconds, but it still seems to be hit and miss.
I thought maybe I just wasn’t letting WinSCP wait long enough, so I increased the timeout to two minutes. The only different behavior was that WinSCP hanged for two full minutes before displaying the error.
The mTCP log from these latest two attempts shows nothing more than «User signed in» and «Disconnect» with 0 timeouts and no errors, just like the full log further up this page.
I started thinking the router might be the issue, so I turned off and back on, but that made no difference. My computer is wired directly to the router by a 3-foot cord, and all other internet usage seems normal, so I’m not likely experiencing network interference.
Maybe its time I file a bug with the developer of mTCP and see what he comes up with.
Are you getting an error like “FTP cannot retrieve directory listing” when you try to access FTP server remotely?
This error is caused due to the bad settings in the FTP server, misconfiguration of FTP client, when passive mode setting disables and much more.
That’s why we often get requests from our customers to solve the error like “FTP cannot retrieve directory listing” as part of our Server Management Services.
Today, we’ll see how our Support Engineers fixed the issue for our customers.
What is “FTP cannot retrieve directory listing” error?
This error “FTP cannot retrieve directory listing” means that the user could not access the files from FTP server.
Users encounter an error message like this.
Error: Failed to retrieve directory listing
Now, let’s see the reasons for the error and the real solution to fix it.
Top 4 reasons and solutions to fix it
Here, we have the top 4 reasons for this error to occur and how we troubleshoot it.
1. Wrong encryption settings in FTP client
For instance, in FileZilla, when you connect to FTP server, you will see something like this.
Response: 227 Entering Passive Mode (11,22,33,44,167,111)
Command: MLSD
Error: Connection timed out
Error: Failed to retrieve directory listing
This happens when encryption is set to “Use explicit FTP over TLS if available” in FTP client settings.
So, we changed the encryption to “only use plain FTP” by executing the below steps.
1. First, we click on the File menu and choose Site Manager.
2. Then add Host and change Encryption to only use plain FTP.
3. Also, change the Logon Type to Normal and enter Username and Password.
4. Finally, click Connect to continue.
2. Problem with Passive mode
FTP operates in both active and passive mode. By default, FTP clients like FileZilla, CuteFTP uses passive as transfer mode.
But, in some cases, you may get an error like “FTP cannot retrieve directory listing” in passive mode. Then, try to change the default transfer mode by simply doing the steps below.
1. Go to Settings > Edit and click on Connection > FTP and choose Active.
2. Then under Active mode IP > select Ask your operating system for the external IP address.
3. Finally, under Passive mode > choose Fall back to active mode and click ok to save.
3. Missing passive port range in FTP server
In most of the cases “FTP cannot retrieve directory listing” error happens when passive port range is not mentioned FTP server configuration.
In cPanel for FTP servers like PureFTP, we perform the following steps.
1. We log in to the server via SSH.
2. Open the /var/cpanel/conf/pureftpd/local file and we add the entry like:
ForcePassiveIP: X.X.X.X
We add these changes to the file because FTP server exists behind the firewall.
3. Then we change the server’s default passive port range, by running the command.
echo "PassivePortRange: 49152 65534" >> /var/cpanel/conf/pureftpd/local
/usr/local/cpanel/scripts/setupftpserver pure-ftpd --force
4. Next, we configure the server to allow the passive port range to pass through the firewall.
5. Finally, restart the PureFTP service.
/usr/local/cpanel/scripts/setupftpserver pure-ftpd --force
4. Lacking Port range in firewall settings
Often this error happens when a firewall blocks passive FTP ports. So, it results in getting an error like “FTP cannot retrieve directory listing”.
We execute the following steps to add the passive port range to the firewall.
1. For firewall like iptables, we open the /etc/sysconfig/iptables file in a text editor.
2. Then add the entry like:
iptables -I INPUT -p tcp --dport 49152:65534 -j ACCEPT
3. Finally, run the command to save.
service iptables save
This is how we fix the error like “FTP cannot retrieve directory listing”.
[Having trouble in “FTP cannot retrieve directory listing” error? We’ll fix it for you.]
Conclusion
In short, “FTP cannot retrieve directory listing” error can happen due to a misconfiguration in firewall settings, incorrect passive port range, and more. Today, we’ve discussed the top 4 reasons for this error and how our Technical Engineers fixed them.
PREVENT YOUR SERVER FROM CRASHING!
Never again lose customers to poor server speed! Let us help you.
Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.
GET STARTED
var google_conversion_label = «owonCMyG5nEQ0aD71QM»;
-
ezols
- New here
- Posts: 5
- Joined: Thu Nov 04, 2021 7:44 pm
Error listing directory
Hi,
I have not had any problems with QNAP ftp for a quiet a long time and suddenly im unable to access ftp content over winscp or file zilla.
The message I get:
Timeout detected. (data connection)
Could not retrieve directory listing
Error listing directory ‘/xxxxx.com’.
Its stuck to one directory when showing error listing.
Port 21 is enabled and telnet connection is successful.
No changes to QNAP have been made prior this problem.
In QNAP manager i can see that user successfully logs in via winscp, and then connection drops because of time out and error listing directory.
What could be the problem of this?
Thanks in advance.
-
ezols
- New here
- Posts: 5
- Joined: Thu Nov 04, 2021 7:44 pm
Re: Error listing directory
Post
by ezols » Fri Nov 05, 2021 7:21 pm
Hello, anyone who could help me with this issue?
-
Toxic17
- Ask me anything
- Posts: 6373
- Joined: Tue Jan 25, 2011 11:41 pm
- Location: Planet Earth
- Contact:
Re: Error listing directory
Post
by Toxic17 » Fri Nov 05, 2021 9:34 pm
QTS Version, NAS model, what settings on FTP server are you using?, what ftp program are you using?
is this access from inside your LAN or the internet?
without you giving us information what do you want the community to do? guess?
-
Toxic17
- Ask me anything
- Posts: 6373
- Joined: Tue Jan 25, 2011 11:41 pm
- Location: Planet Earth
- Contact:
Re: Error listing directory
Post
by Toxic17 » Fri Nov 05, 2021 9:36 pm
Error listing directory ‘/xxxxx.com’.
this would suggest your ftp client is looking for a folder called ‘/xxxxx.com’
-
ezols
- New here
- Posts: 5
- Joined: Thu Nov 04, 2021 7:44 pm
Re: Error listing directory
Post
by ezols » Fri Nov 05, 2021 10:43 pm
Thanks for pointing out about additional info in need to provide.
Model — TS-231 P
Firmware version — 4.5.4 1800
Attached ftp settings.
ftp1.png
ftp2.png
Applications Im using to access ftp are, WinSCP and FIleZilla
Attached settings using when connecting via WinScp
winscp.png
Im trying to connect from internet.
Port 21 is answering to telnet, but I don’t see anymore NAS message when connecting to port 21 via telnet, like it was before.
Now if im trying to connect to ftp it just shows Timeout detected, connection failed.
«this would suggest your ftp client is looking for a folder called ‘/xxxxx.com»
The folder was there, i double checked. But Im not sure why it was searching for that specific folder while connection to ftp(anyway now I don’t even get that error message)
Is there anything else that I need to provide?
Thanks in advance.
You do not have the required permissions to view the files attached to this post.
-
Toxic17
- Ask me anything
- Posts: 6373
- Joined: Tue Jan 25, 2011 11:41 pm
- Location: Planet Earth
- Contact:
Re: Error listing directory
Post
by Toxic17 » Fri Nov 05, 2021 10:57 pm
if your connecting from the internet I take it you have port 21 port forwarded (in your router) to your STATIC IP address of your NAS?
I see your Root folder is set to «/PBN FTP» so the folder called «/xxxxx.com» has to be inside the «/PBN FTP» folder else it would not find it.
personally I would not be opening up port 21 on the internet myself, I’d use a VPN, then ftp to the local ipaddress of the NAS, but each to there own.
-
ezols
- New here
- Posts: 5
- Joined: Thu Nov 04, 2021 7:44 pm
Re: Error listing directory
Post
by ezols » Fri Nov 05, 2021 11:35 pm
im just providing support on this current NAS issue, im unaware of the router configuration, but I would say that it its port forwarded to NAS static ip.
Yes, all the necessary folders are stored in root «/PBN FTP» including «xxxxx.com», but im without clue why it try’s to access it straight away when connection to ftp root folder «Error listing directory ‘/xxxxx.com’.»
And now the bigger confusion is why 21 port is not working on NAS anymore. From router side its still accessible.
Under system status I see that there are some error packages, but don’t know what does that indicate
error.png
You do not have the required permissions to view the files attached to this post.
-
Toxic17
- Ask me anything
- Posts: 6373
- Joined: Tue Jan 25, 2011 11:41 pm
- Location: Planet Earth
- Contact:
Re: Error listing directory
Post
by Toxic17 » Fri Nov 05, 2021 11:42 pm
in WinSCP which I take it you are using do you have anything set for Remote Directory, which is in the advanced setting of Winscp entry for the NAS:
Screenshot 2021-11-05 154039.png
if the directory is there on the NAS then does the username you are logging in with, have the correct permissions to read and/or write to that xxxxx.com folder?
You do not have the required permissions to view the files attached to this post.
-
ezols
- New here
- Posts: 5
- Joined: Thu Nov 04, 2021 7:44 pm
Re: Error listing directory
Post
by ezols » Fri Nov 05, 2021 11:53 pm
shame.png
shame on me, there is xxxxx.com root directory specified, unchecked «Remember last used directory». :/
unfortunately I’m unable to test it yet as i have no clue why i cant connect to ftp anymore, ill have to wait till Monday when someone can access router when NAS is located.
You do not have the required permissions to view the files attached to this post.
I’m trying to use winSCP to FTP my server using FTPs and then synch with a backup folder. I have had this working fine from a PC on my work intranet (i.e. the same domain) however when I try to set it up off site (which is my whole point) the same script fails. The FTP log is as follows..
. 2010-09-09 15:28:30.952 --------------------------------------------------------------------------
. 2010-09-09 15:28:30.952 WinSCP Version 4.2.8 (Build 818) (OS 5.2.3790 Service Pack 2)
. 2010-09-09 15:28:30.952 Login time: 09 September 2010 15:28:30
. 2010-09-09 15:28:30.952 --------------------------------------------------------------------------
. 2010-09-09 15:28:30.952 Session name: user1@myserver.nhs.uk
. 2010-09-09 15:28:30.952 Host name: myserver.nhs.uk (Port: 21)
. 2010-09-09 15:28:30.952 User name: user1 (Password: Yes, Key file: No)
. 2010-09-09 15:28:30.952 Tunnel: No
. 2010-09-09 15:28:30.952 Transfer Protocol: FTP
. 2010-09-09 15:28:30.952 Ping type: C, Ping interval: 30 sec; Timeout: 15 sec
. 2010-09-09 15:28:30.952 Proxy: none
. 2010-09-09 15:28:30.952 FTP: FTPS: Explicit SSL; Passive: No [Force IP: No]
. 2010-09-09 15:28:30.952 Local directory: default, Remote directory: home, Update: No, Cache: Yes
. 2010-09-09 15:28:30.952 Cache directory changes: Yes, Permanent: Yes
. 2010-09-09 15:28:30.952 DST mode: 1
. 2010-09-09 15:28:30.952 --------------------------------------------------------------------------
. 2010-09-09 15:28:30.968 Connecting to myserver.nhs.uk ...
. 2010-09-09 15:28:30.984 Connected with myserver.nhs.uk, negotiating SSL connection...
< 2010-09-09 15:28:30.999 220 Microsoft FTP Service
> 2010-09-09 15:28:30.999 AUTH SSL
< 2010-09-09 15:28:31.031 234 AUTH command ok. Expecting TLS Negotiation.
. 2010-09-09 15:28:31.187 SSL connection established. Waiting for welcome message...
> 2010-09-09 15:28:31.187 USER user1
< 2010-09-09 15:28:31.218 331 Password required for user1.
> 2010-09-09 15:28:31.218 PASS ********
< 2010-09-09 15:28:31.234 230 User logged in.
> 2010-09-09 15:28:31.234 SYST
< 2010-09-09 15:28:31.265 215 Windows_NT
> 2010-09-09 15:28:31.265 FEAT
< 2010-09-09 15:28:31.281 211-Extended features supported:
< 2010-09-09 15:28:31.281 LANG EN*
< 2010-09-09 15:28:31.281 UTF8
< 2010-09-09 15:28:31.281 AUTH TLS;TLS-C;SSL;TLS-P;
< 2010-09-09 15:28:31.281 PBSZ
< 2010-09-09 15:28:31.281 PROT C;P;
< 2010-09-09 15:28:31.281 CCC
< 2010-09-09 15:28:31.296 HOST
< 2010-09-09 15:28:31.296 SIZE
< 2010-09-09 15:28:31.296 MDTM
< 2010-09-09 15:28:31.296 REST STREAM
< 2010-09-09 15:28:31.296 211 END
> 2010-09-09 15:28:31.296 OPTS UTF8 ON
< 2010-09-09 15:28:31.312 200 OPTS UTF8 command successful - UTF8 encoding now ON.
> 2010-09-09 15:28:31.312 PBSZ 0
< 2010-09-09 15:28:31.343 200 PBSZ command successful.
> 2010-09-09 15:28:31.343 PROT P
< 2010-09-09 15:28:31.359 200 PROT command successful.
. 2010-09-09 15:28:31.359 Connected
. 2010-09-09 15:28:31.359 --------------------------------------------------------------------------
. 2010-09-09 15:28:31.359 Using FTP protocol.
. 2010-09-09 15:28:31.359 Doing startup conversation with host.
> 2010-09-09 15:28:31.359 PWD
< 2010-09-09 15:28:31.390 257 "/" is current directory.
. 2010-09-09 15:28:31.390 Getting current directory name.
. 2010-09-09 15:28:31.390 Retrieving directory listing...
> 2010-09-09 15:28:31.390 TYPE A
< 2010-09-09 15:28:31.406 200 Type set to A.
> 2010-09-09 15:28:31.421 PORT 10,222,54,3,6,38
< 2010-09-09 15:28:31.437 200 PORT command successful.
> 2010-09-09 15:28:31.437 LIST -a
< 2010-09-09 15:28:31.468 150 Opening ASCII mode data connection.
. 2010-09-09 15:28:46.968 Timeout detected.
. 2010-09-09 15:28:46.968 Could not retrieve directory listing
* 2010-09-09 15:28:46.968 (ESshFatal) Lost connection.
* 2010-09-09 15:28:46.968 Timeout detected.
* 2010-09-09 15:28:46.968 Could not retrieve directory listing
* 2010-09-09 15:28:46.968 Opening ASCII mode data connection.
* 2010-09-09 15:28:46.968 Error listing directory '/'.
. 2010-09-09 15:28:51.999 Connecting to myserver.nhs.uk ...
. 2010-09-09 15:28:52.015 Connected with myserver.nhs.uk, negotiating SSL connection...
< 2010-09-09 15:28:52.031 220 Microsoft FTP Service
> 2010-09-09 15:28:52.031 AUTH SSL
< 2010-09-09 15:28:52.062 234 AUTH command ok. Expecting TLS Negotiation.
. 2010-09-09 15:28:52.140 SSL connection established. Waiting for welcome message...
> 2010-09-09 15:28:52.140 USER user1
< 2010-09-09 15:28:52.156 331 Password required for user1.
> 2010-09-09 15:28:52.156 PASS ********
< 2010-09-09 15:28:52.187 230 User logged in.
> 2010-09-09 15:28:52.187 SYST
< 2010-09-09 15:28:52.202 215 Windows_NT
> 2010-09-09 15:28:52.202 FEAT
< 2010-09-09 15:28:52.234 211-Extended features supported:
< 2010-09-09 15:28:52.234 LANG EN*
< 2010-09-09 15:28:52.234 UTF8
< 2010-09-09 15:28:52.234 AUTH TLS;TLS-C;SSL;TLS-P;
< 2010-09-09 15:28:52.234 PBSZ
< 2010-09-09 15:28:52.234 PROT C;P;
< 2010-09-09 15:28:52.234 CCC
< 2010-09-09 15:28:52.234 HOST
< 2010-09-09 15:28:52.234 SIZE
< 2010-09-09 15:28:52.234 MDTM
< 2010-09-09 15:28:52.234 REST STREAM
< 2010-09-09 15:28:52.234 211 END
> 2010-09-09 15:28:52.234 OPTS UTF8 ON
< 2010-09-09 15:28:52.265 200 OPTS UTF8 command successful - UTF8 encoding now ON.
> 2010-09-09 15:28:52.265 PBSZ 0
< 2010-09-09 15:28:52.281 200 PBSZ command successful.
> 2010-09-09 15:28:52.281 PROT P
< 2010-09-09 15:28:52.312 200 PROT command successful.
. 2010-09-09 15:28:52.312 Connected
. 2010-09-09 15:28:52.312 Doing startup conversation with host.
. 2010-09-09 15:28:52.312 Getting current directory name.
. 2010-09-09 15:28:52.312 Retrieving directory listing...
> 2010-09-09 15:28:52.312 PWD
< 2010-09-09 15:28:52.343 257 "/" is current directory.
> 2010-09-09 15:28:52.343 TYPE A
< 2010-09-09 15:28:52.359 200 Type set to A.
> 2010-09-09 15:28:52.359 PORT 10,222,54,3,6,40
< 2010-09-09 15:28:52.390 200 PORT command successful.
> 2010-09-09 15:28:52.390 LIST -a
< 2010-09-09 15:28:52.406 150 Opening ASCII mode data connection.
This fails whether I run from GUI or a previously tested and working scripted version. It looks from the log like theres a problem with a timeout on the directory listing, presumably it works locally as less lag
Any ideas if this is a winSCP setting (and if so where) or on the FTPserver side (Windows Web Server 2008 R2) ?