When performing a lengthy operation via SSH connection is dropped, then you can solve this problem!
The challenge is to increase the timeout interval.
The appropriate settings can be done by editing the file sshd_config:
TCPKeepAlive-defines the support link in the active state, the use of special control messages sent with a certain time interval. If the directive is set, the connection will be broken in time observed, and the process will be killed. Possible values are “yes”, “no”.
ClientAliveInterval-client idle time in seconds after which the sshd daemon sends via secure channel request to the client. Directive works only for Protocol 2. The default is set to 0, i.e. no client will be sent to such requests.
Number of verifications the availability-ClientAliveCountMax client that may remain unanswered. If the limit is reached, sshd will complete the session. These requests are different from TCPKeepAlive, as are sent through the secure channel and cannot be tampered with while the TCPKeepAlive admits.
SlientAlive is useful if the client or server behavior depends on the activity of the compounds. If ClientAliveInterval is 15 seconds, and ClientAliveCountMax is left by default SSH clients that do not conform will be switched off after approx. 45 seconds.
It Is Important!
If the # commented out then remove the # sign in front of them.
Some options are only available for Protocol version 2. The default is set to 3. On this we are in the same file
Below give examples of settings for SSHD
TCPKeepAlive checks whether the customer is on the line, ClientAliveInterval-idle time, in seconds, after which the sshd daemon sends a request to the client, and ClientAliveCountMax-specifies the number of checks the availability of the client in the example above, ukazna support for 3:0 connection (180 minutes).
Next, configure the PuTTY (or your other ssh client)