![]() (2) Your rating of this post will be much appreciated. (1) The solution above describes a successful problem-solving experience and may not be applicable to other problems with similar symptoms. My PuTTy connection became inactive because my PuTTY client was not sending "keepalive" packets to the server to prevent the connection from becoming idle and consequently, the server dropped the connection. ![]() ![]() So, after completing STEP 1, you must go to the Session window and click the "Save" button. Saving your PuTTY session is not the most obvious feature of PuTTY as there’s no SAVE button on every configuration window. The default value is 0 which tells PuTTY not to bother about keeping the connection alive. When you need to come back/check on it again, start up SSH, and enter. Amount of time, in milliseconds, that the (TCP) connection must be idle before keepalive probes (if enabled) are sent. The value you select must be less than the idle session timeout of your server for PuTTY to keep your connection active. To exit session: Ctrl+B then D (this leaves the tmux session). I found the answer it depends on tcp keepalive settings: For the list of available TCP settings (FreeBSD 4.8 an up and 5.4): sysctl -A grep. If you do not know the idle session timeout defined on your server, then choose a small value for the "seconds between keepalives". This ensures that your PuTTY client sends NULL packets to the server regularly. Go to PuTTY Configuration –> Connection and set the "seconds between keepalives" to a non-zero value. In order to prevent the server from dropping your PuTTY connection and making it inactive, your PuTTY client must send packets to the server even when you’re not using it. For users who use putty.exe to connect to ssh can use the following setting in Putty to keep the session live. This is done to protect the server (and network components) against a build-up of several redundant connections that could affect performance. Preventing SSH session timeout using putty. This is the total amount of time for which, even without activity, our SSH session will be kept alive. When a server determines that your session is idle (you have not used it for a pre-defined interval), it will drop your connection. In other words, the client will send a keepalive message to the server every 120 seconds (2 minutes), 30 times. Why does a PuTTY connection become inactive? Connections use resources like cpu and memory on the client and server. How to identify an inactive PuTTY connection? When you cannot type anything in your PuTTY window and you see " (inactive)" in your PuTTY window’s title bar, it means that your connection is inactive (has been dropped by the server). My PuTTY connection becomes inactive, thereby requiring me to reconnect to the server and login again.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |