ICE

TCP/IP Products => TCP-PRO => Topic started by: jgould on March 29, 2006, 10:29:36 am

Title: Secure Shell problem
Post by: jgould on March 29, 2006, 10:29:36 am: We have decided to implement SSH for all our clients. For the most part is has been problem free but we have 2 Windows 98 clients that can connect via SSH but after a short while Telnet Pro will terminate with an error in explorer.exe. It seems to be somehow keyboard related as it only appears when the client is keying data or using the return key. We have no macros or keymaps and we have upgraded the clients to the newest version 5.1.26 and the problem persisted even after the upgrade.

Any ideas what might be causing this?

Thanks
Title: Re:Secure Shell problem
Post by: jimn on March 29, 2006, 02:02:17 pm: A few questions:
On the two 2 Windows where this happens, does it happen everytime (ie always within a certain time frame or doing a specific function) or is it intermittent?

Does the errors seem to be triggered by a rapid succession of keystrokes?

Or, does it happen when you're expecting a large amount of of data (ie. a screenful, or many screen fulls of data) to come from the remote side?

Thanks.
Title: Secure Shell problem
Post by: jgould on March 29, 2006, 02:10:44 pm: It seems to happen every session, the time interval appears random but the problem does always seem to happen after a rapid sucession of keystrokes.
Title: Secure Shell problem
Post by: Bob on March 30, 2006, 09:22:35 am: Does it fail on other win98 machines or are they the only ones??

Try turning on the keepalive to see if it makes any difference in behavior. once per ten second interval should be fine.
Title: Secure Shell problem
Post by: jgould on April 04, 2006, 07:24:20 am: These are the only two having this problem. I tried changing the keepalive to 10 but with no luck. I also noticed the following error was appearing.

invalid page pault in DEJAVU.OCX at 0167:012d5998
Title: Secure Shell problem
Post by: Bob on April 04, 2006, 09:11:30 am: Sorry, what I was trying to get at was if it always fails on windows 98 machines for you (i.e. you have NO working windows 98 machines).