Telnet Problem

[Hazem Tolba_1]

Hi,

We are facing a strange problem recently about telnet on OpenVMS running on DEC AXP 4000-610. The customer is using Pathworks to connect to the alpha server using LAT and TCPIP(Telnet).
The users using LAT are working fine.
The other users using TCPIP/Telnet were working fine for long time, but recently they started to face some strange problem. Sometimes, the system disconnects some of those users out, and when they try to re-connect, they can't and get session closed messages. during the time of problem, they can't even telnet from the DOS prompt. Also, the ping is ok during same time.
The customer has to restart the TCPIP and Pathworks to clear the problem.

Have anyone faced similar problem before? Please, advise.

[Volker Halle]

Hazem,

this sounds like some kind of resource problem with TCPIP.

What version of TCPIP are your running ($ UCX SHOW VERS) ?
Do other TCPIP services have the same problem (e.g. FTP), when the TELNET problem exists ?

Volker.

[labadie_1]

do
$ define tcpip$bind_res_options "debug"
before the telnet
and post the messages

[Wim Van den Wyngaert]

Did you try autogen to find out what system parameter might be to low ?
Is keepalive to high (or forever) and thus a lot of devices open (ucx show dev) ?

Wim

[Hazem Tolba_1]

Hi again,

After some troubleshooting, we find the the telnet session limit is causing the problem when the limit is exeeced.
Now we are trying to increase the limit through UCX/TCPIP using "set service telnet /limit=n" command, but unfortunately the command is returning with "%tcpip-e-invrecord: invalid information" error.
I tried the same command for ftp, and it works fine. I also tried the set command to change other paramaters other than the limit, and it also works fine.

Do anyone knows the reason of the command error, or knows how to increase the telnet session limit by different method?

we have OpenVMS Alpha V7.1-2 and TCPIP V5.0A.
Regards.

[Volker Halle · Accepted solution]

Hazem,

there is an old ATW article, which describes this error message and a workaround:

http://h71000.www7.hp.com/wizard/wiz_9232.html

Changing the service limit of any TCPIP service always requires the service to be re-started (disabled/enabled), so ALL your TELNET session would be disconnected.

When trying to use the workaround as described in above article, use the same commands to re-define the service as found in your current SYS$MANAGER:TCPIP$CONFIG.COM (search for 'SET SERV TELNET').

Volker.

[Wim Van den Wyngaert]

But this limit should never disconnect users. Only prevent new users.

Wim

[Hazem Tolba_1]

Hi,

Thanks a lot for Volker Halle. I found the exact problem in the mentioned ATW and so I The idea was to first remove the service from the TCPIP "set noservice telnet" and then set the service with the total parameters including the new session limit and restarting the TCPIP.

Regards.