topic connection refuse when telnet in Operating System - HP-UX

connection refuse when telnet

keh — Tue, 06 Jun 2000 05:21:08 GMT

when I open a window command prompt and telnet to my hpux sever, I got connection refuse. I have perform followings checks;
1)at console, I verify that the telnetd is running
2)issue netstat -a | grep telnet
I can see there are number of user connections are ESTABLISHED and the telnet is LINSTEN
3)I try to telnet to itself at console, but face the same problem
At that time, the cpu are very busy, is only about 10% idle. I suppose telnet does not need much resource. I am more incline to think that problem is on the tcp/ip settings. like max number of socket has reach limit. Any body can help ?

Re: connection refuse when telnet

Anthony Goonetilleke — Tue, 06 Jun 2000 06:02:20 GMT

Check /etc/inetd.conf for something like

telnet stream tcp nowait root /usr/lbin/telnetd telnetd

All on one line and issue the following command

inetd -c

Also check /var/adm/inetd.sec
for any funny looking restrictions to do with telnet.

Re: connection refuse when telnet

Steven Sim Kok Leong — Tue, 06 Jun 2000 06:03:08 GMT

Hi,

The telnetd process is spawned by your inetd when a new telnet connection request is accepted. telnetd is not meant to run by itself.

Check your /etc/inetd.conf and ensure that the line beginning with telnet is not commented out. If the line has been commented out, uncomment it and restart inetd by running inetd -c. Check that your inetd process is running. If it still does not work, check your /var/adm/inetd.sec for any IP restrictions for the telnet clients.

Regards.

Steven Sim.

Re: connection refuse when telnet

Jag_2 — Tue, 06 Jun 2000 19:09:39 GMT

How many user license do you have.

Re: connection refuse when telnet

Berlene Herren — Tue, 06 Jun 2000 19:57:52 GMT

You may also want to adjust your nstrpty/npty and nstrtel in your kernel. Databases take up twice as many as telnet sessions do, so you may be deficit.
type
#kmtune (or #sysdef at 10.20)
and see how many are in your kernel now.
Then type
/dev/ll pt* | wc -l
and see how many device files you have. They should be close.
If not, increase them (and your nstrpty and npty should be the same) in the kernel and/or /dev and reboot.
to increase in kernel, the easiest way is to use SAM. To increase in /dev, type
#insf -n -C pseudo >> where is the number you want to increase it to. This will not cause a reboot, increasing them in your kernel will.

For more information, see
<>

Berlene