Telnet/SSH screen stops responding after a while but the session is still active
The system is Redhat 9. I just did a RPM update using the Check4Update utility included with Redhat distributions, which upgraded my kernel from 2.4.20-30.9 to 2.4.20-31.9, together with a bunch of other RPM's. I have done this many times and no problems so far.
Everything went okay with this update, except one problem I just noticed. When I telent or SSH to the server and leave the session idle for a while, the screen will stop responding to my typings. In other words, if I don't do anything for a couple of minutes and start to type again, the curson won't move and the whole screen just freezes. I have to close the window and reconnect again.
However, I know the session is still active when the screen freezes. The reason I know this is that I used the "screen" command when I telnet/SSH over, and when I reconnect to the server after the screen freezes, I can pickup my previous "virtual screen" by using the "screen -r" command. And when I resume the previous "virtual screen" by doing so, I saw all the text I typed when the screen freezes.
So the whole problem looks like this: in my telnet or SSH session, if I leave it idle for a couple of minutes and start to type again, the text I typed is sent over to the server, however, the server didn't send the respond back to my telnet / SSH client and therefore, makes the client window looks frozen.
Does anyone know what might be the cause? And unfortunately, I don't have the list of RPM's that was just updated.