Your best friend for file transfer.Fetch
large file transfer stalled to NT server (4 posts)
- Started 5 years ago by iwasnevy
- Latest reply 5 years ago from Scott McGuire
If I transfer a file larger than about 11Mb, it stalls at the end of the transfer. Nothing shows up in the logs, but when I use cyberduck, it tells me that the transfer timed out during a read. I'm assuming that at the end of the transfer, the ftp client reads the file before saying it's complete? Anyway, things work fine when I use windows explorer to transfer the files. I've spoken with the admin on their end, and he's got the timeout set to an hour, so that's not what's happeneing. I've tried modifying all sorts of settings: active/passv, used all sorts of different proxys, and tried changing just about every other obscure setting I could find.
Scott McGuire Administrator
We'd like some more information in order to provide the best advice.
Which version of Fetch are you using?
Are you trying to download or upload the files?
What happens if you try to use Fetch's resume upload or resume download features (depending on which you're trying to do)? Both of these pick up where the previous attempt left off. Does that allow the transfer of the file to continue?
Sorry - It's the latest version of fetch - I dl'd it cause I though it was a problem with cyberduck.
I'm trying to upload a file to another person's ftp site. Their ftp site is running on a Windows NT server (I mention this only 'cause I've found via googling that there's sometimes issues with getting a mac ftp client to work properly with NT server)
I've not tried to resume the upload. What's happening is in the status area of fetch, below the file window, where it says how much data is being transfered, data transfer rate, etc, at the end of the transfer it shows "21.6mb of 21.6mb transferred" - the data transfer rate begins marching downward, and then it shows "stalled". It never finishes the transfer. When I stop the tranfer, it appears as though the file is not there, but if I navigate out of and back into the directory, it shows the file and the correct filesize. I've not asked the reciever yet if he's able to open the file ie: transferred completely.
The last log entry in fetch says data transfer started, and that's it until I cancel it and then I get an error -128 If I remember correctly (I'm not at work anymore) - basically that I cancelled it.
I'm sure it's something that's not being compatible on the NT side of things, since this happens with fetch 5, fetch 4 and cyberduck. after some time, cyberduck reports "read timed out".
Funny thing is that when I use Windows Explorer in Parallels, there's no problems - everything transfers fine.
I've spoken to the recipient about it, and he's going to have his IT guy look into it on their end, but I get the feeling they're not going to pursue this very far, as his attitude was "use windows." with a heavy undertone of 'frickin mac users...'
Scott McGuire Administrator
Thanks for the additional information.
I suspect your uploads are actually completing successfully; the problem is that the Mac FTP programs are just not getting (or not recognizing) a signal from the server that the upload is finished. Some servers don't send the proper signal at the end of an upload, or unexpectedly drop the connection after a long upload, so will never send the signal.
We have a beta version of Fetch that might fix the problem for you; we have specifically made some fixes to deal with this sort of problem. If you'd like to give it a try, please send a short note to:
bugs at fetchsoftworks dot com
with the subject "beta test." We'll add you to the beta test list and send you a copy of the beta version, and then you can give it a test and let us know if it fixes this problem for you.
- Page 1