I was unable to reproduce the crash on Win2k or XP SP2 or SP3 (all slower and with less memory), where 220.127.116.11 loaded and seemed fully functional. I very mouch doubt that it was a coincidence, because my PC had been up for about 20 days before that and had no issues launching old FZ.
Lately, I rarely use the Client at all, and am doing my transfers in Total Commander
, which supports FTP implicit SSL as well and, since version 7, is now complete with the latest extensions such as UTF-8 and MLSD directory listing. Total Commander works very well for short sessions, because it doesn't have the ability to resume. It can easily initiate 2 streams by starting another backgroud transfer. Over LAN I can transfer any files using just Total Commander.TC connected to FileZilla Server over SSL and showing configration options
I find that FileZilla is the best method to transfer files between different Windows versions, which have problems connecting over SMB, and at higher speed than possible over Neighborhood.Edit:
I was confused about the different kinds of Secure file transfer protocols. After research I found that Total Commander supports FTP over SSL internally (used with FileZilla Server and similar), and SFTP (used with Linux boxes) with this plugin
. Both protocols need encryption DLLs on the system. They can be shared by several programs. Both protols are well integrated into the file manager, and in case of the SFTP(SSH) plugin, one can even extract compressed files directly onto a remote server.
The interface needs some getting used to (sites/servers are configured via TC's "Network Neighborhood" which is a catch all place for foreign file systems). SFTP appears to be faster and more reliable when sending many small files. I was able to initiate a background transfer and keep working in the file manager more fluently than with FTP.
Edited by j7n, 28 March 2014 - 01:18 AM.