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
- pugilaresAspirantIs your Filezilla client running on the Windows machine?
It seems to me that Windows Firewall or some other Windows security setting on my client machine is preventing Filezilla to see incoming connections to ports within data range. Filezilla and fzsftp is present and marked in Windows Firewall exceptions. - StephenBGuru - Experienced UserYes, I run FileZilla on both Windows 7 professional and XP SP 3.
On the Windows 7 system the Firewall settings are set by our IT folks, I have no control over it. - pugilaresAspirantOk, so I changed the command port on my server from 21 to somewhere within the four-digit range. Since then FTPeS works fine :-)
I rally don't know why it wasn't possible on default port. But as it's acceptable for me to use alternative port, then it's OK.
Thank you guys for your attention :-) - chirpaLuminarySome routers mess with FTP packets to try and get around PORT/PASV issues over NAT. They transparently rewrite the commands. Changing to non-default port 21 usually stops this.
http://www.gamedev.net/topic/524150-net ... p-packets/
Related Content
NETGEAR Academy

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