not login by using telnet

[S.S.]

Hi,

For one of my server i was unable to login by using telnet session as even though i have given right userid and password also. There is no problem when i supplied the same userid and password by using ssh protocol.
May i know what will the problem?

Thanks!

[Horia Chirculescu]

Hello,

> There is no problem when i supplied the same userid and password by using ssh protocol.

Then just forget about telnet protocol! ssh is safer, and telnet should be disabled as it send passwords in clear over the network.

Horia.

[Johnson Punniyalingam]

telnet, blocked,

you can also check by checking on the

/etc/inetd.conf
/etc/services

[S.S.]

Hi,

We have checked the /etc/inetd.conf file and we specifically not disabled this service as this is needed for our operation.

Please find the telnet service in /etc/inetd.conf file:

telnet stream tcp nowait root /usr/lbin/telnetd telnetd -b /etc/issue

The banner is working but when i supplied my authentication it displayed the message like login failed.


Thanks!

[S.S.]

Also, checked the file /var/adm/inet.sec file and the telnet service is allowed.

Thanks!

[Horia Chirculescu]

Please post here the result of a telnet session.

Telnet from the local server is working? (I mean ssh to the server then telnet localhost is working?)

Horia.

[thatiraju]

>>>>>>>i was unable to login by using telnet session as even though i have given right userid and password also. There is no problem when i supplied the same user id and password by using ssh protocol.<<<<<<<,]

Here is one cause :
Dear the problem may occur when u use the symbols like $,@ ,∧ # . If u have used these symbols in your passwd your system may not allow you to login through telnet .

The SSH will be working with the same passwords.

We had the same problem too . So please try to avoid the use of these ,
We had a same problem too . I was not aware what to do exactly , but suggested not to use these letters .

Dear Expertise , Could some one tell me why this occurs when we use these symbols .

Raj..

[Matti_Kurkela · Accepted solution]

When the first Unix systems were developed, only the most expensive terminals had a CRT display. The rest had a printer instead.

On a printing terminal, erasing a previous character is difficult and slow to do. Therefore, the standard convention was that the "#" character meant "disregard previous character", and "@" meant "disregard the entire line and start over". For example, if a terminal printout line read:

login: mike####sam

it meant the user had first typed "mike", then erased it and typed "sam" instead.
If the other special character was used, it might have looked like this:

login: mike@
sam

The support for these functions was built into the TTY driver. The default settings for the TTY driver were standardized in "System V Interface Definition, Third Edition" (SVID3).

Even though printer terminals can now be found in museums only, the default values of the HP-UX TTY driver have not been changed. The defaults are even documented: see "man 7 termio" on a HP-UX system, and find the sub-title "Special Characters".

These same defaults are used with "pseudo-TTYs" or pty devices, which are used to emulate the interface of a real terminal when using a telnet or SSH connection... unless the telnetd or sshd daemon configures the pty device differently.

The above-mentioned two characters "#" and "@" usually cause the most trouble when logging in.

But when logging in from a console, modem line or any other serial-connected terminal, there is yet another set of special characters to consider.

"getty" is the process that monitors a serial-connected terminal and produces the login prompt. On HP-UX, the man page for getty includes this:

-----
getty also understands the ``standard'' ESS2 protocols for erasing, killing and aborting a line, and terminating a line. If getty sees the ESS erase character, _, or kill character, $, or abort character, &, or the ESS line terminators, / or !, it arranges for this set of characters to be used for these functions.
-----

Most users aren't aware of this functionality, because after the user has been authenticated, the standard login scripts will reconfigure the TTY special characters to values more suitable with less-ancient hardware.

SSH was developed in the 1990s when the network connections were already the norm. Because sshd "knows" the client-side is reasonably modern, OpenSSH initializes the pseudo-TTY with a more modern set of default values, so the characters like "#" and "@" won't be an issue with it.

MK

[S.S.]

Dear All,

I have used only 1 capital letter and numbers in the password. There is no special character.
The same password i am using for other hosts and they are logging fine via telnet only the problem with one host.

Can anyone suggest me what will be the problem?

I have checked the inetd.conf, inetd.sec file and confirmed that the telnet service is not disabled.

Thanks!

[S.S.]

Dear All,

I have used a test user to login via telnet and given the same password to login which i am using for my account and it was working fine for the test user.

May i know why login problem only for my account?
Please find the telnet login messages when loging using my account.

login:
Password:
Last successful login for SN95599: Thu Mar 11 08:42:32 SST-8 2010 on pts/ta
Last unsuccessful login for SN95599: Wed Mar 10 16:57:05 SST-8 2010 on pts/ta
Exceeds number of logins allowed (3) for user SN95599

Wait for login exit: ..


Connection to host lost.


Thank you!