Custom Query (7834 matches)
Results (118 - 120 of 7834)
|#844||Failure to establish TLS connection behind NAT gateway|
FileZilla (2.2.12c) can't establish a TLS connection to a PureFTPd server (possibliy other servers, too?) when it (the FileZilla client) is sitting behind a NAT gateway. The problem already arises during the TLS connection negotiation (so this is _not_ a "classical" firewall issue with tracking the data connections!).
The conversation looks like this:
over again The connection does not get to the point, where the TLS encryption for the control channel is succesfully established (this would show up in the log files)
Whe the FileZilla client has a "real" IP address, it can cooperate with the same server. Other clients (I tested "lftp") have no problem to establish the TLS connection through the NAT gateway.
Attached is a packet dump of the network traffic ( which due to the encryption is not really enlightening)
|#845||transfer error when having site open in right window|
When having the remote site still open in the right window i occasionally gets "transfer error #xxx" trying again".
When closing the remote connection this problem dissapears and i do not get any more "transfer error". I.e. the transfer is errorfree.
This problem has existed as long as i have used filezilla both as server and as a client. ( aprox 6 months ) and duing this time i frequently have updated to latest versions on both sides.
Currently using client 2.2.12c and server 0.9.6a(beta). Both sides are using WinXP, Serverside is SP1 and client is SP2.
|#847||No keep alive over SOCKS5 proxy|
After getting a tcp capture from both sides of the proxy, it is clear that the FTP control session is timing out on the proxy due to inactivity. This causes the ftp server to shut down the FTP data session.
I have verified that Enable the Keep Alive System box is checked, but there is no evidence of traffic being sent to the proxy over the control session once the data transmission has started.