topic Re: telnet problem in Operating System - HP-UX

telnet problem

Luca Rasconi — Fri, 18 Oct 2002 13:06:48 GMT

Hi all,
when I try to make a telnet to a machine don't appear the login prompt:
[h3mih109]/# telnet 10.195.66.4
Trying...
Connected to 10.195.66.4.
Escape character is '^]'.

After a bit of time appear that connection is closed by foreign host.

When I try to make the same command from another machine it's works fine:
[root@h3mil008 ~] # telnet 10.195.66.4
Trying 10.195.66.4...
Connected to 10.195.66.4.
Escape character is '^]'.

HP-UX h3rmh005 B.11.11 U 9000/800 (td)

login:

Sombody can suggest me something?

Thanks in advance
Luca

Re: telnet problem

Ken Hubnik_2 — Fri, 18 Oct 2002 13:15:09 GMT

Have you checked the /var/adm/inetd.sec file and see if there are any restrictions on telnet?

Re: telnet problem

Luca Rasconi — Fri, 18 Oct 2002 13:17:29 GMT

That file doesn't exist.

Luca

Re: telnet problem

Nashford Ramdeen — Fri, 18 Oct 2002 18:36:04 GMT

check the /var/adm/syslog/syslog.log file on the system at 10.195.66.4 and see if there are any telnetd related errors (like device files missing)

Re: telnet problem

Telia BackOffice — Mon, 21 Oct 2002 06:39:28 GMT

You have a DNS problem look at the /etc/resolv.conf for you DNS settings.
Consiter to make changes to you /etc/nsswitch.conf to only or first use hosts file, then last make the changes to the /etc/hosts file (include the host and ip).

BR,
Jannik

Re: telnet problem

Marco Queirolo — Mon, 21 Oct 2002 14:56:30 GMT

Hello,

Check the /etc/hosts and /etc/passwd files permissions. (at least r--r--r--).

Regards.

Re: telnet problem

jim bidebo — Mon, 21 Oct 2002 15:07:00 GMT

(please excuse my poor english)

i assume that you have physical access to the non working mashine.

check that telnet isnt commented in /etc/inet.conf
you should have a row looking something like this:
telnet stream tcp nowait root /usr/lbin/telnetd telnetd
(make sure that its not commented out with a #)

if you dont want to reboot the mashine try to restart inetd.
ps -ef |grep inetd
(get something like this: root 715 1 0 Sep 2 ? 0:00 /usr/sbin/inetd, the second field is the pid)
kill -HUP 715 (or the pid that your inetd is running at)

Re: telnet problem

Rita C Workman — Mon, 21 Oct 2002 16:02:53 GMT

Well it could be working for the other machine because this server 'knows' it.
Remember when you telnet, the receiving server will try to resolve who is trying to connect first. Based on your ~nsswitch.conf...so if host file is the first thing it checks and you have no entry for this client..then it moves to next thing to try like DNS, so it checks and if it can't resolve...it continues to next option and only then it will present a login prompt (unless your network times out first....!!!) if there is enough time. I think your getting timed out !

Look at your ~nsswitch.conf, if it shows the hostfile is checked first..then do a quick test and put an entry into the receiving box hostfile for this client...Then see if it will allow the connection.

Just a thought,
Rita

Re: telnet problem

Anil C. Sedha — Tue, 22 Oct 2002 20:31:49 GMT

Luca,

Your message post states that telnet is getting connected. I don't understand why the login prompt doesn't appear.

Do you press enter after you see

Connected to 10.195.66.4.
Escape character is '^]'.

It happens sometimes to me, on my remote systems and after i press enter 2-3 times it works.
This feels very stupid but this is the way it works sometimes. Have you tried pressing "Enter"

Regards,
Anil

Re: telnet problem

Luca Rasconi — Wed, 23 Oct 2002 06:03:50 GMT

Thank you all,
i don't know why, but now it works.
Who tried to resolve the problem told me that it worked after he made a telnet to 127.0.0.1!

Bah

Bye
Luca