Telnet Sessions Disconnecting

[Timothy P. Jackson]

Hello everyone!

I have just moved to from a K200 to an rp5430. On the K200 all the users were using serial connections through DTC's. On the new rp5430, they are using telnet connections. Now it seems that the users are getting disconnected for no reason, or at least one I can find.

I am logging some errors in the syslog.log

Jul 10 09:46:54 rp5430 telnetd[16158]: gethostbyaddr: km00148.kurt-mfg.com. != 1
72.16.8.144
Jul 10 10:07:01 rp5430 telnetd[24750]: gethostbyaddr: km00146.kurt-mfg.com. != 1
72.16.8.118
Jul 10 11:11:43 rp5430 telnetd[16918]: gethostbyaddr: km00148.kurt-mfg.com. != 1
72.16.8.144
Jul 10 11:21:39 rp5430 telnetd[17031]: getpid: peer died: Connection timed out
Jul 10 11:36:34 rp5430 telnetd[23035]: gethostbyaddr: km00148.kurt-mfg.com. != 1
72.16.8.144
Jul 10 12:52:16 rp5430 telnetd[15458]: gethostbyaddr: km00148.kurt-mfg.com. != 1
72.16.8.144
Jul 10 13:22:02 rp5430 syslog: gethostbyaddr: km00148.kurt-mfg.com. != 172.16.8.
144

I am not sure it this has anything to do with it.

Any help would be greatly appreciated!

Tim

[Steven E. Protter]

Shalom Tim,

Have you increased the number of telnet sessions permitted by the kernel beyond the default of 60?

kmtune | grep tel
or grep nstel to get the parameters, this is a common issue.

insf -e

Try again.

Seems you have an unrelated host resolution issue you may want to deal with.

SEP

[Timothy P. Jackson]

Hi Steven,

Yes, I have increased the npty, nstrpty and nstrtel all set to 160.

Tim

[Greg Vaidman]

Check the environment variable TMOUT in your user's shells. If set to anything other than 0, they will automatically be disconnected after the specified number of seconds of inactivity.

The gethostbyaddr errors you're seeing in syslog are due to HP-UX's silly default maximum of 35 IP addresses per hostname. If you were to do an nslookup of your host km00148.kurt-mfg.com, you'd likely see the error "MAXADDRS exceeded: skipping address" repeated multiple times. There's not much you can do about this other than changing your DNS (not recommended - it's set up that way for a reason) or waiting for HP-UX 11.3, when this is supposed to be fixed.