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 access. Smaller size folders seem to transfer sometimes but the larger size folders fail. This happens with folders of multiple files and big individual files(like an mkv file). I use Windows explorer(windows7) to transfer the folder. On the remote side of it, Windows gives me an error.
I'm not sure what I'm doing wrong or if theres some type of other way to configure this. The ftp logs doesn't show an error off the readynas side. I've tried using ftp clients as well with the same failure. It just loses connection it seems.
Windows message displays the following error:
Error copying file or folder
An error occurred while copying the file. The operation timed out
Heres what the ftp log from the readynas shows:
Sep 08 20:29:29 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session opened.
Sep 09 00:29:29 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): Preparing to chroot to directory '/home/ftp'
Sep 09 00:29:32 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): ANON ftp: Login successful.
Fri Sep 09 00:45:41 2011 900 64.17.230.98 89035020 /home/ftp/media/Music/Thrice/2011_-_Major-Minor/01_Yellow_Belly.flac b _ o a User@ ftp 0 * c
Sep 08 20:51:32 NAS proftpd[26853] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session opened.
Sep 09 00:51:32 NAS proftpd[26853] 192.168.1.2 (64.17.230.98[64.17.230.98]): Preparing to chroot to directory '/home/ftp'
Sep 09 00:51:36 NAS proftpd[26853] 192.168.1.2 (64.17.230.98[64.17.230.98]): ANON ftp: Login successful.
Sep 09 00:55:42 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP no transfer timeout, disconnected
Sep 09 00:55:42 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session closed.
Fri Sep 09 01:07:19 2011 921 64.17.230.98 89035020 /home/ftp/media/Music/Thrice/2011_-_Major-Minor/01_Yellow_Belly.flac b _ o a User@ ftp 0 * c
Another example from another try of transferring over ftp doesn't even show anything wrong from the log:
Sep 22 19:33:04 NAS proftpd[29139] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session opened.
Sep 22 23:33:04 NAS proftpd[29139] 192.168.1.2 (64.17.230.98[64.17.230.98]): Preparing to chroot to directory '/home/ftp'
Sep 22 23:33:07 NAS proftpd[29139] 192.168.1.2 (64.17.230.98[64.17.230.98]): ANON ftp: Login successful.
Thu Sep 22 23:39:07 2011 295 64.17.230.98 41950800 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/01_-_Tempting_Time.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:42:47 2011 218 64.17.230.98 32319996 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/02_-_Soraya.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:46:59 2011 251 64.17.230.98 30766606 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/03_-_Thoroughly_at_Home.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:52:21 2011 321 64.17.230.98 44997419 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/04_-_On_Impulse.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:53:12 2011 50 64.17.230.98 4475972 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/05_-_Tessitura.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:59:40 2011 387 64.17.230.98 33270296 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/06_-_Behaving_Badly.flac b _ o a User@ ftp 0 * c
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 access. Smaller size folders seem to transfer sometimes but the larger size folders fail. This happens with folders of multiple files and big individual files(like an mkv file). I use Windows explorer(windows7) to transfer the folder. On the remote side of it, Windows gives me an error.
I'm not sure what I'm doing wrong or if theres some type of other way to configure this. The ftp logs doesn't show an error off the readynas side. I've tried using ftp clients as well with the same failure. It just loses connection it seems.
Windows message displays the following error:
Error copying file or folder
An error occurred while copying the file. The operation timed out
Heres what the ftp log from the readynas shows:
Sep 08 20:29:29 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session opened.
Sep 09 00:29:29 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): Preparing to chroot to directory '/home/ftp'
Sep 09 00:29:32 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): ANON ftp: Login successful.
Fri Sep 09 00:45:41 2011 900 64.17.230.98 89035020 /home/ftp/media/Music/Thrice/2011_-_Major-Minor/01_Yellow_Belly.flac b _ o a User@ ftp 0 * c
Sep 08 20:51:32 NAS proftpd[26853] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session opened.
Sep 09 00:51:32 NAS proftpd[26853] 192.168.1.2 (64.17.230.98[64.17.230.98]): Preparing to chroot to directory '/home/ftp'
Sep 09 00:51:36 NAS proftpd[26853] 192.168.1.2 (64.17.230.98[64.17.230.98]): ANON ftp: Login successful.
Sep 09 00:55:42 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP no transfer timeout, disconnected
Sep 09 00:55:42 NAS proftpd[26515] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session closed.
Fri Sep 09 01:07:19 2011 921 64.17.230.98 89035020 /home/ftp/media/Music/Thrice/2011_-_Major-Minor/01_Yellow_Belly.flac b _ o a User@ ftp 0 * c
Another example from another try of transferring over ftp doesn't even show anything wrong from the log:
Sep 22 19:33:04 NAS proftpd[29139] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session opened.
Sep 22 23:33:04 NAS proftpd[29139] 192.168.1.2 (64.17.230.98[64.17.230.98]): Preparing to chroot to directory '/home/ftp'
Sep 22 23:33:07 NAS proftpd[29139] 192.168.1.2 (64.17.230.98[64.17.230.98]): ANON ftp: Login successful.
Thu Sep 22 23:39:07 2011 295 64.17.230.98 41950800 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/01_-_Tempting_Time.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:42:47 2011 218 64.17.230.98 32319996 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/02_-_Soraya.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:46:59 2011 251 64.17.230.98 30766606 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/03_-_Thoroughly_at_Home.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:52:21 2011 321 64.17.230.98 44997419 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/04_-_On_Impulse.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:53:12 2011 50 64.17.230.98 4475972 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/05_-_Tessitura.flac b _ o a User@ ftp 0 * c
Thu Sep 22 23:59:40 2011 387 64.17.230.98 33270296 /home/ftp/media/Music/Animals_As_Leaders/2009_-_Animals_As_Leaders/06_-_Behaving_Badly.flac b _ o a User@ ftp 0 * c
10 Replies
Replies have been turned off for this discussion
- What is the MTU setting on the NAS (Network tab)? If it's set to 1500, try dropping it to 1492. I've seen this help in similar FTP cases.
- I have jumbo frames enabled so the MTU on the NAS is set to 7936. Sadly when I set my laptop to use jumbo frames it makes a local transfer to the NAS awful, the best setting for file transferring locally for me seems to be by having the nas with jumbo frames enabled and my windows laptop set to standard MTU(1500). I don't think the Verizon router I have can support jumbo frames but from testing with a drag and drop locally on my network it seems this setting is the best.
If I disable jumbo frames my transfer speeds to the NAS locally will be horrible, usually not going over 4Mbps. Right now I'm lucky to get 11Mbps consistently transfering to the NAS via drag and drop through windows.
Maybe that's my issue right there? I have a crappy verizon router and maybe i should try drag and drop tests directly connected to the NAS? - Okay so I managed to get my network working better as far as transfer speeds locally. I dropped the MTU size to 1492 but the same problem is happening. At the very very last second the transfer fails.. Any ideas what else I could be looking into?
- Anyone have anything to try for this? I'm unable to download a 700Mb file from my ftp server off my readynas... It's really aggravating.
- So the transfer will occur normally for 99% of the file, then fail at the end?
Try downloading with an FTP client and posting the session log from the client here. - Yea, it will say less than a second remaining and then fail the transfer. I've tried with an ftp client in the past with the same results. I'll try again soon but I'm expecting the same results as the last time. All it shows on the client side usually is ftp session ended or something along the lines of that.
- So with using windows the transfer will fail at the very last second. When using a ftp client, it seems to be failing but then auto-resuming.. I dunno how to read the log really other than it telling me that it resumes the file transfer again.. anyone have an ideas?
. 2012-01-13 12:02:24.116 File: "/media/Music/Metallica/1988 - And Justice for All/vinyl/08. To Live Is to Die.flac"
. 2012-01-13 12:02:24.118 Copying "/media/Music/Metallica/1988 - And Justice for All/vinyl/08. To Live Is to Die.flac" to local directory started.
. 2012-01-13 12:02:24.119 Binary transfer mode selected.
. 2012-01-13 12:02:24.119 Starting download of /media/Music/Metallica/1988 - And Justice for All/vinyl/08. To Live Is to Die.flac
> 2012-01-13 12:02:24.192 TYPE I
< 2012-01-13 12:02:24.325 200 Type set to I
> 2012-01-13 12:02:24.325 PASV
< 2012-01-13 12:02:24.482 227 Entering Passive Mode (108,34,173,17,132,239).
> 2012-01-13 12:02:24.484 RETR 08. To Live Is to Die.flac
< 2012-01-13 12:02:24.750 150 Opening BINARY mode data connection for 08. To Live Is to Die.flac (410302103 bytes)
< 2012-01-13 12:18:53.108 226 Transfer complete
. 2012-01-13 12:18:53.120 Download successful
> 2012-01-13 12:19:24.306 TYPE I
< 2012-01-13 12:19:24.306 200 Type set to I
> 2012-01-13 12:19:53.727 TYPE I
< 2012-01-13 12:19:53.727 200 Type set to I
> 2012-01-13 12:20:24.148 PWD
< 2012-01-13 12:20:24.148 257 "/media/Music/Metallica/1988 - And Justice for All/vinyl" is the current directory
> 2012-01-13 12:20:53.571 PWD
< 2012-01-13 12:20:53.571 257 "/media/Music/Metallica/1988 - And Justice for All/vinyl" is the current directory
. 2012-01-13 12:20:53.572 Retrieving directory listing...
> 2012-01-13 12:20:53.572 TYPE A
< 2012-01-13 12:20:53.613 200 Type set to A
> 2012-01-13 12:20:53.614 PASV
< 2012-01-13 12:20:53.676 227 Entering Passive Mode (108,34,173,17,128,63).
> 2012-01-13 12:20:53.676 LIST -a
< 2012-01-13 12:20:53.751 150 Opening ASCII mode data connection for file list
< 2012-01-13 12:20:53.848 226 Transfer complete
. 2012-01-13 12:20:53.848 Directory listing successful
> 2012-01-13 12:21:23.994 TYPE A
< 2012-01-13 12:21:23.994 200 Type set to A
> 2012-01-13 12:21:54.430 TYPE A
< 2012-01-13 12:21:54.430 200 Type set to A
> 2012-01-13 12:22:23.838 REST 0
< 2012-01-13 12:22:23.838 350 Restarting at 0. Send STORE or RETRIEVE to initiate transfer
> 2012-01-13 12:22:54.274 TYPE I
< 2012-01-13 12:22:54.274 200 Type set to I
. 2012-01-13 12:22:54.275 Retrieving directory listing...
> 2012-01-13 12:22:54.275 TYPE A
< 2012-01-13 12:22:54.318 200 Type set to A
> 2012-01-13 12:22:54.319 PASV
< 2012-01-13 12:22:54.383 227 Entering Passive Mode (108,34,173,17,77,7).
> 2012-01-13 12:22:54.383 LIST -a
< 2012-01-13 12:22:54.461 150 Opening ASCII mode data connection for file list
< 2012-01-13 12:22:54.553 226 Transfer complete
. 2012-01-13 12:22:54.553 Directory listing successful - Any ideas? I'm still getting file transfer dropouts.. no idea why...
- I've done a factory reset and this is still happening, only when transferring bigger files. How am I the only one with this problem? I've used multiple ftp clients and the clients log just disconnect and then auto-resume. Now it appears I'm getting a couple of other messages on the logs from the nas as well.. Is there anything I should be changing or doing differently? Should I remove the ftp masquerade for my dyndns service?
Here's the logs from the readynas(xxxx is used to keep the files and names anonymous):
Oct 17 01:33:14 NAS proftpd[1143] 192.168.1.2: mod_dynmasq/0.3: unable to resolve 'xxxxx.endofinternet.net', keep previous address: Name or service not known
Oct 17 21:22:40 NAS proftpd[8094] 192.168.1.2 (64.17.230.98[64.17.230.98]): USER admin: Login successful.
Wed Oct 17 21:22:40 2012 0 64.17.230.98 2683681240 /home/ftp/media/Video/Movies/xxxx.mkv a _ d r admin ftp 0 * c
Oct 17 21:22:42 NAS proftpd[8094] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session closed.
Oct 17 21:31:37 NAS proftpd[7558] 192.168.1.2 (64.17.230.98[64.17.230.98]): Data transfer stall timeout: 600 seconds
Wed Oct 17 21:31:37 2012 8476 64.17.230.98 2683681240 /home/ftp/media/Video/Movies/xxxx.mkv b _ i r admin ftp 0 * i
Oct 17 21:31:37 NAS proftpd[7558] 192.168.1.2 (64.17.230.98[64.17.230.98]): FTP session closed. - 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.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
