1833464 Members
2695 Online
110052 Solutions
New Discussion

Re: Telnet issue

 
Tom Danzig
Honored Contributor

Re: Telnet issue

Are you trying to telnet as root? Is /etc/securetty present? If it exists and only contains console, you won't be able to telnet in.

Is the system trusted? If so, you may need to add the appropriate tty to the allowed list of terminalts (/tcb/auth/tty ??)
Gabriel_23
Frequent Advisor

Re: Telnet issue

I am unable to rlogin (receive "connection closed" message immediately). This server is running 11.11.

I also checked /var/adm/inetd.sec. This file appears to be ok.
Gabriel_23
Frequent Advisor

Re: Telnet issue

I am unable to rlogin (receive "connection closed" message immediately). This server is running 11.11.

I also checked /var/adm/inetd.sec. This file appears to be ok.

Gabriel_23
Frequent Advisor

Re: Telnet issue

No, I am not trying to telnet as root. Checked /etc/securetty (looks ok).
Sridhar Bhaskarla
Honored Contributor

Re: Telnet issue

One of the old issues that I remember is - check the root's account in /etc/passwd file. Is it normal?. Do you have /etc/passwd at all?.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Gabriel_23
Frequent Advisor

Re: Telnet issue

Sri,

Checked passwd file. Root passwd entry appears to be ok.
Hai Nguyen_1
Honored Contributor

Re: Telnet issue

Have you tried to login as more than one non-root user? Just try to eliminate a specific user problem.

Hai
Gabriel_23
Frequent Advisor

Re: Telnet issue

Yes, I have tried to login as several non-root users...after the login id is entered, I receive the message ("connection closed by foreign host")
Hai Nguyen_1
Honored Contributor

Re: Telnet issue

Gabriel,

Can you post the output of the following command:

# grep telnet /etc/inetd.conf /etc/services /var/adm/inetd.sec

Hai
Sridhar Bhaskarla
Honored Contributor

Re: Telnet issue

Hi Gabriel,

As a last resort, try 'insf -e' on the box and see if it helps. I am running out of ideas for now.

I would suggest one more to get more debugging information. Run 'tusc' against inetd. You will need to download tusc from HP's porting center. Once you got it installed, do

#ps -ef|grep inetd
(note the process id (pid))
#/opt/tusc/bin/tusc -f -o /tmp/inetd.out pid

Telnet to the box. Once the connection is closed, do a control-c on the above and post inetd.out file.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try
Gabriel_23
Frequent Advisor

Re: Telnet issue

Found the following telnet entries:

/etc/inetd.conf:
telnet stream tcp nowait root /usr/lbin/telnetd telnetd -b /etc/issue

/etc/services:

telnet 23/tcp


There are no telnet entries in /var/adm/inetd.sec

Thanks for all your help guys...I am currently signing off, but I will keep you all posted on the results tomorrow....thanks again...




Kelli Ward
Trusted Contributor

Re: Telnet issue

Gee Gabriel, you're tough. :)

Do you have an /etc/hosts.allow and hosts.deny?

What's in them, if so?

Thanks,
Kel
The more I learn, the more I realize how much more I have to learn. Isn't it GREAT!
Gabriel_23
Frequent Advisor

Re: Telnet issue

Hey everybody... I finally found the problem...
After more investigation, we found that the /etc/pam.conf file was corrupted. We restored this file from /usr/newconfig/etc and it was all good.
Sridhar Bhaskarla
Honored Contributor

Re: Telnet issue

Hmm... I thought of asking you to check your pam.conf. But since you were able to do 'ssh', I discarded that idea. Obviously your ssh was not compiled with PAM that mis-guided us.

-Sri
You may be disappointed if you fail, but you are doomed if you don't try