sshd times out and disconnects client

Sat Mar 29 19:15:40 GMT 2025

On Fri, Mar 28, 2025 at 2:42 PM C. Linus Hicks <linush@mindspring.com>
wrote:
> On the server side, you can update the sshd_config file and set the value
> of the ClientAliveInterval to a non-zero value, like 60 seconds. Or you can
> set the ServerAliveInterval option to a similar value in your client
> options, either on the command line or in your local config file.
>> On Fri, Mar 28, 2025 at 4:28 PM Soren <somian08@gmail.com> wrote:

> Hello Linus H. and others,
> Ok! The quick reply was especially helpful today. Thanks very much,
> Linus, for the expert advice! I edited /etc/sshd_config according to your
> information and stopped and restarted sshd. Then logged in from a Linux
> box and all seems well.
> Cygwin still rocks.
> Soren Andersen
>I am guilty of premature exaltation. When I wrote the above, I had not
allowed a couple hours go by to see if the ssh sessions would disconnect. I
was just happy that making the recommended change to sshd_config did not
"break" anything, and took it on faith that I'd solved the problem. It
didn't.
I'll add a bit more information in hopes that we can still find a fix. This
Windows 10 laptop goes into "sleep mode" after a couple hours of no
keyboard or mouse input, and when it does so sshd disconnects any sessions.
I didn't mention that in my first message. Sorry. The way I would *like*
Windows to work would be to stay in full power mode while a service like
sshd is active. I don't know my laptop well enough to know if there is any
setting I can toggle to avoid this semi-shutdown, or at least extend the
time before it does this. Perhaps someone on the list knows?
Also, I remember hearing of a "mouse jiggler" utility that would simulate
use of the mouse to keep Windows from going to sleep, but that was years
ago. If such a thing still exists, maybe a list reader knows about it.
I really appreciate the help. Thanks,
 Soren A