NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FTP File transfer fail
Hi All, I had this issue before I did a factory default as well, I assumed a factory default would fix the issue I'm having but it seems to continue failing. I have my media share setup for ftp ...
I've sometimes seen the transfer fail at the very end and autoresume to complete (sometimes filezilla actually said 0 bytes to go). Since resume is enabled, I never particularly worried about it.
Are you saying the dyndns is itself doing the masquerade, or that you have the ReadyNAS set up to to the masquerade? The only way dyndns could do it would be if they were acting as an FTP proxy (and then your FTP control connection would always be routed through their server). So if that is what you mean, then I would try taking it out of dyndns as a test.
Filezilla works fine w/o a masquerade, as do some other clients. The way that detection works is that if filezilla sees a private address (192.168.x.x in your case) it substitutes the source address it sees in the incoming IP packets. So depending on the client, you might need the NAS to do the masquerade (if you take it out of dyndns). That can create issues for LAN transfers, depending on your router. However, I suggest ignoring that initially and figuring out what it takes to get FTP over the WAN first.
BTW, you might also check your passive port range. From your log it looks rather large on the NAS. All the passive ports need to be forwarded in your router. I am wondering if some of your failures are because occasionally you are being assigned a passive port that isn't forwarded (or which collides with some other service you have configured on the router).
Generally its best to limit the number of passive ports. You do need at least 1 per simultaneous connection, 2x-4x the number of expected simultaneous connections is a pretty good value. Note some clients will open multiple connections when doing file transfers, they generally have setting which can cap the number they use.
Are you saying the dyndns is itself doing the masquerade, or that you have the ReadyNAS set up to to the masquerade? The only way dyndns could do it would be if they were acting as an FTP proxy (and then your FTP control connection would always be routed through their server). So if that is what you mean, then I would try taking it out of dyndns as a test.
Filezilla works fine w/o a masquerade, as do some other clients. The way that detection works is that if filezilla sees a private address (192.168.x.x in your case) it substitutes the source address it sees in the incoming IP packets. So depending on the client, you might need the NAS to do the masquerade (if you take it out of dyndns). That can create issues for LAN transfers, depending on your router. However, I suggest ignoring that initially and figuring out what it takes to get FTP over the WAN first.
BTW, you might also check your passive port range. From your log it looks rather large on the NAS. All the passive ports need to be forwarded in your router. I am wondering if some of your failures are because occasionally you are being assigned a passive port that isn't forwarded (or which collides with some other service you have configured on the router).
Generally its best to limit the number of passive ports. You do need at least 1 per simultaneous connection, 2x-4x the number of expected simultaneous connections is a pretty good value. Note some clients will open multiple connections when doing file transfers, they generally have setting which can cap the number they use.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
