topic Re: Telnetd refusing connections in Operating System - HP-UX

Telnetd refusing connections

Jason Magouirk — Thu, 17 Aug 2000 19:00:06 GMT

I have a B2000 running 10.20 that I installed the other day that is refusing all telnet connections. SAM does say that telnetd is enabled and active, but the only way I can get in remotely is by rlogin. All other network activity (NIS/DNS/NFS/et cetera) is working properly. Any suggestions?

Re: Telnetd refusing connections

Rick Garland — Thu, 17 Aug 2000 19:08:22 GMT

Do a inetd -c to reread the inetd file.

Hope it helps.

Re: Telnetd refusing connections

Vikas Khator — Thu, 17 Aug 2000 19:09:34 GMT

Since it's a new installation I don't expect a /var/adm/inetd.sec file having an entry out there but you may want to check it out.

Re: Telnetd refusing connections

Rita C Workman — Thu, 17 Aug 2000 19:09:53 GMT

Alot of possible situations here...I'll start with a first possibility.
Have your checked your /var/adm/inetd.sec file and made sure that it isn't denying access.
Then check your /etc/inetd.conf and make sure telnet is set up right in there..
Regards,

Re: Telnetd refusing connections

Antoanetta Naghiu — Thu, 17 Aug 2000 19:12:39 GMT

Do more /etc/inetd.conf | grep telnet
Is it the line starting with # (commented out)?
Check in the box that do not accept the connection the /var/adm/inetd.sec file (more it). See man inetd.sec.

Re: Telnetd refusing connections

wyan lowe — Thu, 17 Aug 2000 19:13:28 GMT

if you're telneting as "root" to box,
maybe should also check
/etc/securetty - if it's there, this will cause "login incorrect" for root

file allows you to restrict root access to console-only login

Re: Telnetd refusing connections

Jason Magouirk — Thu, 17 Aug 2000 19:37:15 GMT

Thanks to all those who resonded. The inetd -c suggestion took care of the initial problem. The numerous suggestions to check ou t /var/adm/inetd.sec didn't fix the initial problem, but there were some entries there that would have been problematic. As for /etc/securetty, this wasn't part of my problem, but it is good information to know. Thanks to all!

(As an aside, this box wasn't a "new" box as such, because it came from a client that wants us to do some testing. So though it was new to our network, it was in fact a fully preconfigured system--for someone elses network, anyway :-).