Differences
This shows you the differences between the selected revisions of the page.
| 2016-08-12 | 2016-10-03 | ||
| bug 1436 is released already (martin) | consistency + reduce acronyms (martin) | ||
| Line 82: | Line 82: | ||
| * With [[SFTP]] or [[SCP]] protocol, all reasons and hints for [[message_connection_refused|"Network error: Connection refused"]] apply to this error too. | * With [[SFTP]] or [[SCP]] protocol, all reasons and hints for [[message_connection_refused|"Network error: Connection refused"]] apply to this error too. | ||
| - | * With [[ftp|FTP protocol]], a reason is likely a firewall or NAT blocking a data connection. Learn about [[ftp_modes|FTP connection modes and required network configuration]]. | + | * With [[ftp|FTP protocol]], a reason is likely a firewall/proxy/NAT blocking a data connection. Learn about [[ftp_modes|FTP connection modes and required network configuration]]. |
| If you are getting the error with the FTP protocol (on a control connection) when finishing a lengthy transfer: | If you are getting the error with the FTP protocol (on a control connection) when finishing a lengthy transfer: | ||
| - | * A reason is typically a broken firewall/proxy/NAT that aborts the FTP control connection as it sees no traffic during the file transfer. Note that there's no way for WinSCP to keep the control connection alive during the transfer. It would violate the FTP protocol specification. | + | * A reason is typically a broken firewall/proxy/NAT that aborts the %%FTP%% control connection as it sees no traffic during the file transfer. Note that there's no way for WinSCP to keep the control connection alive during the transfer. It would violate the %%FTP%% protocol specification. |
| ===== [[transfer_channel_cant_be_opened]] Transfer channel can't be opened ===== | ===== [[transfer_channel_cant_be_opened]] Transfer channel can't be opened ===== | ||