• The general timeout issue you raised. I am going to attach our FTP connectivity troubleshooting guide. There is something in your logfile that definitely indicates a firewall issue:
2015-01-27 18:23:42.650 TLS connection established
2015-01-27 18:31:44.330 Timeout detected.
This likely means after the initial handshake, the FTP client tried to open a new port for data transfer, and it failed. The attached will give you some useful things to try.
We recommend that you try the following things in order and see if any of them resolve your issue.
1. Change active vs. passive mode. FTP clients and libraries have two modes of operation: Active mode and Passive mode. If the default doesn't work for you, try the other mode. As you try the other suggestions below, make sure to try each suggestion under both Active and Passive mode. Different firewalls work with different modes.
2. Try SSL. If you aren't using SSL, try switching to FTP-over-SSL on port 990 (implicit) or port 21 (explicit). In many cases, using SSL will get around any firewall blocking.
3. Try alternate ports. BrickFTP offers port 3021 as an alternate port for FTP. Often times, simply using port 3021 will allow your connection to work through your firewall.
Their analysis of the timeout issue is wrong.
Particularly this does not make any sense:
This likely means after the initial handshake, the FTP client tried to open a new port for data transfer, and it failed.
The connection is obviously already opened. The TLS handshake occurs on the connection.
The timeout happended only 7 minutes (!) later, when the transfer completed and WinSCP timeouted waiting for the FTP server to acknowledge the transfer. So it's unlikely that any of his suggestion will make a difference (and you are using SSL/TLS already). It still can be a firewall (or router or proxy) issue though. If the firewall is stupid enough to close the FTP control connection due to an inactivity, during a long file transfer.
