Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[Sbrown]

I am using ICE TCP version 5.0.67 (with a 50 user licence) on windows 98se PC's and telnetting into a Unix SVR4 NCR box. I have a few users that cannot connect using Telnet Pro when they get to work in the morning when they come in. The Telnet Pro program opens up, but will not connect to the server and I have to usually do a ctrl-alt-del and kill off the process and then try to connect again. Sometimes this works, and sometimes I have to reboot the PC to make the connection work. Are there any known issues about this? I have tried just about everything I can think of to fix the problem. I've reinstalled the software, replaced network drivers, and network cards. Turned off the settings that allow the NIC to go to sleep. I'm pretty much out of idea's.. Thanks for any help you can give.

Thanks,

Scott Brown....

[jimn]

The only thing that comes to mind is that the Unix system is not always responding. Most of the time Pro should timeout gracefully and tell you it can't connect, but under some situation it can just hang. If you are connecting using SSH the current version has a fix that will prevent Pro from hanging and time out gracefully.

[SSOLOMON]

We feel that the issue is most likely not an issue with the unix server. The issue occurs only occurs in a few select PCs consistently, and the rest never have any issues connecting. We are not using SSH currently. The PC displays a blank screen and just hangs on the program. Don't know if that helps you at all. Thanks.

Scott Solomon

[jimn]

Hi Scott,

I suggest updating to the current version on one of the PC that is having a problem, and see if it makes any different.

I would suppose there are other 98se machines on the site that work fine. Is this correct?

Jim

[Bob]

Sounds to me like you may have hanging telnet sessions on the NCR box. Log in there as root and do a:

netstat -an | grep 23

and look for something  in the leftmost column of ip address/port pairs for something like

192.168.254.1:23  1.2.3.4:1025 TIMEWAIT (or something like FIN_ACK or something other than ESTABLISHED)

This would indicate a hung socket:port pair on the NCR box. I'm guessing that you need to turn keepalives on the NCR box (which is tuning the kernel and probably requires a kernel rebuild).