NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Esseci
May 31, 2012Aspirant
FTP server MLSD timeout
Hi,
I have an issue with a Duo,
I've activated the FTP service without any problem.
I can connect via a client (Filezilla) but I have a folder with a lot of files (pictures) and when I move in and I the client sends the MLSD command I receive the answer:
150 Opening ASCII mode data connection for MLSD
but then it goes in timeout.
I tried to increment the timeout without any results.
I tried with another client (Smart Ftp), the same.
I installed an ftp server in a pc client in the same network of the Nas and by that server I can list every folder.
Perhaps there some memory limit in my Readynas duo ?
Thanks
I have an issue with a Duo,
I've activated the FTP service without any problem.
I can connect via a client (Filezilla) but I have a folder with a lot of files (pictures) and when I move in and I the client sends the MLSD command I receive the answer:
150 Opening ASCII mode data connection for MLSD
but then it goes in timeout.
I tried to increment the timeout without any results.
I tried with another client (Smart Ftp), the same.
I installed an ftp server in a pc client in the same network of the Nas and by that server I can list every folder.
Perhaps there some memory limit in my Readynas duo ?
Thanks
34 Replies
Replies have been turned off for this discussion
- EsseciAspirantI checked the Jumbo Frame check-box and it was turned off.
It doen't work either with that flag turned on or tuned off.
Another usefull information about the problem:
I forwarded the 443 port of the NAS on the router to logon from outside. When I enter the public address the browser ask me for the Nas password but then it stops responding.
Nearly nothing gets out of the Nas (FTP and Https). - StephenBGuru - Experienced UserIt might be worth setting up an alternative https port on the NAS, and try forwarding that in the router instead. I am thinking that the router itself might allow external management over port 443, so there could be some special handling of that port in the router.
Is your router using PPPoE ADSL? If so, you may need to reduce the MTU size configured in the NAS. - EsseciAspirantI set up the alternative port 4443 and I forwarded: the same.
The NAS page finally arrives to the browser but several minutes later.
The router is that one the Telecom (an italian provider) gives to the clients (it's not configurable).
How much do I have to reduce the MTU size? - StephenBGuru - Experienced User
Maybe start with 1454, and see if there is any improvement.Esseci wrote: I set up the alternative port 4443 and I forwarded: the same.
The NAS page finally arrives to the browser but several minutes later.
The router is that one the Telecom (an italian provider) gives to the clients (it's not configurable).
How much do I have to reduce the MTU size?
If your router responds to ping (over the internet), you can measure the MTU using the procedure here: http://muzso.hu/2009/05/17/how-to-deter ... icmp-pings. - EsseciAspirantIi found the best MTU with your hint, but the result is the same.
Next days I'm going to change the router to a Netgear one.
I'll inform you about it - EsseciAspirantRouter changed to NETGEAR DGNB1100.
The same ! - StephenBGuru - Experienced UserHave you tried using active mode?
- EsseciAspirantIn active mode it stops at first MLSD:
Stato: Risoluzione dell'indirizzo IP xxxxxxxxxxxxxxxxxxxxx in corso
Stato: Connessione a xxxxxxxxxxxxxxxxx:40...
Stato: Connessione stabilita, in attesa del messaggio di benvenuto...
Risposta: 220 ProFTPD 1.3.3c Server (NETGEAR ReadyNAS) [xx.xx.xx.xx]
Comando: USER xxxxxxx
Risposta: 331 Password required for xxxxxxx
Comando: PASS **********
Risposta: 230 User xxxxx logged in
Comando: SYST
Risposta: 215 UNIX Type: L8
Comando: FEAT
Risposta: 211-Features:
Risposta: MDTM
Risposta: MFMT
Risposta: TVFS
Risposta: UTF8
Risposta: AUTH TLS
Risposta: MFF modify;UNIX.group;UNIX.mode;
Risposta: MLST modify*;perm*;size*;type*;unique*;UNIX.group*;UNIX.mode*;UNIX.owner*;
Risposta: LANG en-US*
Risposta: PBSZ
Risposta: PROT
Risposta: SITE MKDIR
Risposta: SITE RMDIR
Risposta: SITE UTIME
Risposta: SITE SYMLINK
Risposta: REST STREAM
Risposta: SIZE
Risposta: 211 End
Comando: OPTS UTF8 ON
Risposta: 200 UTF8 set to on
Stato: Connesso
Stato: Lettura elenco cartelle...
Comando: PWD
Risposta: 257 "/" is the current directory
Comando: TYPE I
Risposta: 200 Type set to I
Comando: PORT 192,168,10,12,19,138
Risposta: 200 PORT command successful
Comando: MLSD
Errore: Tempo scaduto per la connessione
Errore: Non è stato possibile leggere il contenuto della cartella - pugilaresAspirantSo in case of mine I get GnuTLS error 53 right after the _second_ MLSD command within the FTPS session.
I use Windows XP SP3 and Filezilla 3.5.3 client. I tried many tricks already but still without success.
Filezilla utilises passive mode explicit TLS in this case.
Data port range set on ReadyNAS, masquerade set also. DMZ set on the server side NAT to ReadyNAS host IP.
I have also turned OFF Application Layer Gateway service on the client machine. Filezilla and fzsftp added to exceptions in Windows Firewall.
Still GnuTLS error 53 after second MLSD :-( - StephenBGuru - Experienced UserFTPeS (explicit TLS) works with my Duo V1 with the FileZilla client. I keep masquerading off, and forward the connection port (I don't use 21) and the passive port range configured on the Duo. I am not seeing these timeout issues.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!