From: Anthony Roberts (anthonyrcalgaryhotmail.com)
Date: Mon Feb 02 2004 - 12:27:45 CST

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

>"Jan 30 13:24:38 knight sshd[23215]: Disconnecting:
>Timeout, your sessionnot responding."

I get this all the time when I log in to home from work, and some friends
have this problem logging in to my computer from behind the university's
firewall. It happens because their firewall/nat drops the connection after
the connection has been idle for a given period. I don't know why that would
happen on a Windows machine on the physical network. Something is making
idle connections time out on Windows computers, and I don't think it's your
client software. It's probably either firewall software or Windows itself.
It occurs to me that the Windows network stack might actually have been
altered to time out idle connections all by itself, so they don't have to
fix other parts of the OS that are being sloppy. I don't know, but I
wouldn't be surprised either way.

In either case, something is timing out the connection. The workaround is to
enable client side keepalive signals. This can be done in Putty in the
connection properties. I don't know about other software, but it can
probably do it too.

_________________________________________________________________
MSN 8 with e-mail virus protection service: 2 months FREE*
http://join.msn.com/?page=features/virus&pgmarket=en-ca&RU=http%3a%2f%2fjoin.msn.com%2f%3fpage%3dmisc%2fspecialoffers%26pgmarket%3den-ca

• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]