Scenario: I have two SSH windows open to the same host. I'm typing in one of them. Suddenly, the host starts loosing packets. A few minutes later the packet loss subsides.

Result: The SSH window that I was typing in loses connection with the remote host. However, the window that I was not typing in is still connected and working fine.

Does anyone know how I can make it so that both windows would remain connected? I'm guessing that it's something that I can configure on my end---my computer is noticing that TCP acknowledgements (for the text that I typed) keep failing to come back so it gives up and closes the connection. How can I make it not give up?

I'm using SecureCRT on Windows 98 (Dialup Networking).

Try toggling keepalive settings, If it is enabled, disable it, if it is disabled, enable it. See if it fixes your problem.

If that doesn't work, try another SSH client (such as the excellent PuTTY) to see if the problem is client related.

Hi!
I would agree with priyadi.
putty is a fine SSH client for windows.
It is free and cool... You can download it from here -
http://www.chiark.greenend.org.uk/~sgtatham/putty/download.html

Have a great day :)

regards
amar

I got this response from SecureCRT Technical Support:

This behavior is a function of the network
component of Windows. The Internet protocols
do not attempt to determine if a connection
is functioning constantly. However, if a
connection is discovered to be non-functional
during an attempt to transmit data it, the
connection has failed.

The remote systems react in the same way on
connection based protocols like telnet and
ssh, so both ends see the connection failure.

Web browsers and similar applications weather
short network outages better because the
protocols they use are not connection based
and the data transfers can be retried.

So, I'm guessing the solution would be a registry hack perhaps (and not a software problem), since it's the Transport layer and not the Application layer that causes these disconnects.