NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
RN214 FTP Timeout After Transferring Small Amount of Data
Device:
ReadyNAS 214; 6.9.4 Hotfix 1;
~ 7.8 TB free; no quotas enabled
Clients: Filezilla 3.39.0; Windows 7 FTP CLI
Network:
MicroTik router
Last Change: Upgraded ReadyNAS to 6.9.4
I am trying to FTP upload (to NAS from Internet) or download (from NAS to Internet) a file and the connection establishes and the file transfer starts but stops and times out after a small amount of data is transferred (~100KB). The only error message is a timeout error.
If I enable the ability to resume, the file will eventually transfer by sending a small chunk of data, timeout, and then resume.
This problem only exists when transferring from outside the network. Transfers on the LAN have no issues using the same FTP client (same version of Filezilla).
This had been working before the upgrade to ReadyNAS 6.9.4.
Any help is appreciated!!
**************************************
Log from FTP Client:
Status: Connection established, waiting for welcome message...
Status: Logged in
Status: Starting download of /BTWOneDrive/Presentation.pptx
Command: CWD /BTWOneDrive
Response: 250 CWD command successful
Command: TYPE I
Response: 200 Type set to I
Command: PASV
Response: 227 Entering Passive Mode (1,1,1,1,218,65).
Command: RETR Presentation.pptx
Response: 150 Opening BINARY mode data connection for Presentation.pptx (1114244 bytes)
Error: Connection timed out after 20 seconds of inactivity
Error: File transfer failed after transferring 81,760 bytes in 20 seconds
Status: Disconnected from server
Status: Resolving address of www.zippy.com
Status: Connecting to 1.1.1.1:2021...
Status: Connection established, waiting for welcome message...
Status: Logged in
Status: Starting download of /BTWOneDrive/Presentation.pptx
ETH1 SettingsFTP Settings
8 Replies
Your passive port range is much too large (though it is the default). I recommend 3-4 passive ports per (simultaneous) connection. Also, the ports should be in the private range allocated by IANA (49152-65535).
So perhaps try setting the passive port range to 50001-50004, and then configure your router to only forward those ports to the NAS. You should reserve the IP address for the NAS in your router, so it is always the same. Otherwise the port forwarding can fail.
StephenB, thanks for the input!
I changed the passive ports to a small range of 100 (50100-50200) with no effect. As before, some traffic is making it through (roughly 100Kb) and then stopping.
The main reason I posted this in the Netgear forums is that the upgrade to 6.9.4 was the last change that was made and it was working before that. I was hoping that someone would say, "oh yeah, that is fixed in the mainteance release". :)
I did add a rule in my router to specifically forward the passive ports to the NAS which is probably a good idea in general but it didn't help either.
I'm willing to try any other ideas!
The end of your client log looks wrong to me. 1.1.1.1 is the CloudFlare public DNS service, not the IP address of www.zippy.com. And I don't know why it would be trying to resolve www.zippy.com anyway. Any clarification of what that's about? Did you change those bits to mask your WAN IP address?
Bippin wrote:
The main reason I posted this in the Netgear forums is that the upgrade to 6.9.4 was the last change that was made
It's painless to downgrade to 6.9.3, so maybe do that and retest.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
