Differences
This shows you the differences between the selected revisions of the page.
| 2021-02-18 | 2021-02-18 (current) | ||
| no summary (109.200.124.193) (hidden) (untrusted) | Restored revision 1610103197. Undoing revision 1613619248. (martin) (hidden) | ||
| Line 10: | Line 10: | ||
| For this reason the //passive// mode was introduced and is mostly used nowadays. It is a default for WinSCP too. Using the //passive// mode is preferable because most of the complex configuration is done only once on the server side, by experienced administrator, rather than individually on a client side, by (possibly) inexperienced users. | For this reason the //passive// mode was introduced and is mostly used nowadays. It is a default for WinSCP too. Using the //passive// mode is preferable because most of the complex configuration is done only once on the server side, by experienced administrator, rather than individually on a client side, by (possibly) inexperienced users. | ||
| - | In the //passive// mode, the client uses the control йух connection to send a ''PASV'' command to the server and then receives a server IP address and server port number from the server, which the client then uses to open a data connection to the server %%IP%% address and server port number received.((From an arbitrary client port.)) | + | In the //passive// mode, the client uses the control connection to send a ''PASV'' command to the server and then receives a server IP address and server port number from the server, which the client then uses to open a data connection to the server %%IP%% address and server port number received.((From an arbitrary client port.)) |
| Use //[[ui_login_connection|Passive mode]]// session settings to toggle between the //active// and the //passive// mode. | Use //[[ui_login_connection|Passive mode]]// session settings to toggle between the //active// and the //passive// mode. | ||