Opened 11 years ago

Last modified 11 years ago

#8488 new Bug report

Incomplete File Transfers to Server

Reported by: Chris Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Windows
Operating system version: Win 7

Description

With recent versions of FileZilla, we have been seeing a number of incomplete file transfers. Here are our steps to reproduce:

1) Connect to the FTP server (on Windows CE device). (No encryption, anonymous FTP).
2) Transfer a file of size > 1MB from client to server.
3) Often the file transfer will "complete" after only ~200kB have been transferred. Sometimes a client PC will get stuck in this state, unable to transfer larger files.
4) The file remains on the server with a size of ~200kB.

The reason why I suspect FileZilla is the culprit is because other FTP clients (such as Microsoft command line ftp client and Windows Explorer) work OK from the same machines that have trouble with FileZilla.

Furthermore, I once took a Wireshark capture during the transfer and it seemed evident that FileZilla was dropping the ball on the communications.

This seems to happen with 3.6.0.2 but not with 3.6.0. However, I am not certain of that.

Thank you for your assistance. Please let me know if there is more information I could provide that would be helpful in tracking down this bug.

Detailed version information below:

FileZilla Client


Version: 3.6.0.2

Build information:

Compiled for: i586-pc-mingw32msvc
Compiled on: x86_64-unknown-linux-gnu
Build date: 2012-11-29
Compiled with: i586-mingw32msvc-gcc (GCC) 4.2.1-sjlj (mingw32-2)
Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.12
GnuTLS: 3.1.4
SQLite: 3.7.6.2

Operating system:

Name: Windows NT 6.1 (build 7601, Service Pack 1)
Version: 6.1
Platform: 64 bit system

Change History (1)

comment:1 by leuk_he, 11 years ago

This is nothing new for me. I see this a lot. I do suspect the server in my case, but in any way the real problem is that if filezilla transfers less bytes than the filesize, it still puts the file in the completed file transfer, and not in the failed file transfer, which would allow me to take action.

Note: See TracTickets for help on using tickets.