Differences
This shows you the differences between the selected revisions of the page.
| 2018-01-18 | 2018-01-18 | ||
| no summary (103.79.96.24) (hidden) (untrusted) | Restored revision 1515754533. Undoing revision 1516273271. (martin) (hidden) | ||
| Line 37: | Line 37: | ||
| ==== [[passive_local]] Notes for Uncommon Local Network Configurations ==== | ==== [[passive_local]] Notes for Uncommon Local Network Configurations ==== | ||
| - | When the %%NAT%% happens on a client side, what the %%FTP%% server cannot know, the IP address it provides is wrong too (from a client's perspective). You can force WinSCP to ignore the %%IP%% address provided by the server using a //[[ui_login_ftp|Force IP address for passive mode connections]]// session setting.. | + | When the %%NAT%% happens on a client side, what the %%FTP%% server cannot know, the IP address it provides is wrong too (from a client's perspective). You can force WinSCP to ignore the %%IP%% address provided by the server using a //[[ui_login_ftp|Force IP address for passive mode connections]]// session setting. |
| When using a restrictive local firewall that blocks even outgoing connections, you need to open not only control connection port 21, but also a port range for data connections. To open as little ports as possible, find out what ports is the %%FTP%% server configured to use. If you cannot know that, you have to open all unprivileged port range, 1024 - 65535. | When using a restrictive local firewall that blocks even outgoing connections, you need to open not only control connection port 21, but also a port range for data connections. To open as little ports as possible, find out what ports is the %%FTP%% server configured to use. If you cannot know that, you have to open all unprivileged port range, 1024 - 65535. | ||