we try download files over 2GB from sftp server (freeFTPd, RebexTinySftpServe, CoreFTPServer, ... ). but always download failed and Server is down or crash.
isn't chilkat lib support files over 2GB ?
Chilkat certainly supports uploads and downloads over 2GB.
It should work. To understand and solve a problem would require more information than just saying "it doesn't work".
2 GB was an old limitation on file systems. So it probably is OS related.
Hello, I have the same problem, I try to download a file from 4Go and at 2,074 Go I lose connexion. I must disconnect, connect and start resumefile to continue. I had a old version of Chilkat (9.3.2) with almost the same problem, but the lost of connexion was after 162.58 Mo, so now it s better :)
I did it again, and I have a log, but not so interesting, because I just have a timeout and after I restart resumedownload... MAy be my log could help
> ChilkatLog: DownloadFileByName: > DllDate: Dec 28 2016 > ChilkatVersion: 184.108.40.206 > UnlockPrefix: XXXXXXX > Architecture: Little Endian; 32-bit > Language: Visual C++ 6.0 > VerboseLogging: 0 > SshVersion: SSH-2.0-SSHD > SftpVersion: 3 > downloadFileByName: > PreserveDate: 0 > fromFilePath: /dummy.szf > toFilePath: d:\temp\dummy.szf > OpenRemoteFile: > sftpOpenFile: > remotePath: /dummy.szf > access: readOnly > createDisposition: openExisting > v3Flags: 0x1 > Sent FXP_OPEN > handle: 30 > --sftpOpenFile > timeToOpenMs: Elapsed time: 219 millisec > --OpenRemoteFile > FetchRemoteFileAttributes: > fetchAttributes: > filename: /dummy.szf > Using FXP_STAT > Sent message to fetch attributes. > Received SSH_FXP_ATTRS > --fetchAttributes > timeToFetchAttrMs: Elapsed time: 31 millisec > --FetchRemoteFileAttributes > remoteFileSize: 4294967296 > resumeFlag: 0 > numBytesToDownload: 4294967296 > newDownloadLoop: > socketOptions: > SO_SNDBUF: 262144 > SO_RCVBUF: 4194304 > TCP_NODELAY: 1 > SO_KEEPALIVE: 0 > --socketOptions > startingOffset: 0 > numBytesToDownload: 4294967296 > bReadUntilEnd: 0 > sockRecv: Socket operation timeout. > SSH read timed out. > discardRemaining: > sockRecv: Socket operation timeout. > SSH read timed out. > --discardRemaining > timeToDownloadFileDataMs: Elapsed time: 458860 millisec > NumBytesSentToOutput: 2227716477 > --newDownloadLoop > Num bytes sent to output was not equal to the expected number. > numBytesExpected: 4294967296 > numBytesSentToOutput: 2227716477 > sftpCloseHandle: > handle: 30 > Sent FXP_CLOSE > sockRecv: Socket operation timeout. > SSH read timed out. > Failed to read expected SFTP packet. > Failed to receive response to FXP_CLOSE > --sftpCloseHandle > timeToCloseHandleMs: Elapsed time: 10062 millisec > Closing local output file... > totalTimeMs: Elapsed time: 469172 millisec > --downloadFileByName > Failed. --DownloadFileByName > --ChilkatLog
You might try overriding the default.
Also I have had major issues with clients that were using really old SSH Libs. With a manual logon, should print out a line showing what ssh lib on server.