Re: telnet authentication fails

["Alan Mead" <amead8695 home com>]

RE: telnet authentication fails> Nathalie Boulos wrote:
>
> > > be sure that the server is accepting access using telnet| :-)
> >
> > I tried telnet on the POP3 port of the server (telnet 192.168.0.245 110)
it
> > accepted the connexion and authentication of the same user succeeded!!!!
> > But "telnet 192.168.0.245" returns "Login incorect", for the SAME user
and
> > the SAME password.
> >
> > What might be the problem???
> >
> > Thx!
> > Nat.
> >
> > > ----- Original Message -----
> > > From: "Nathalie Boulos" <nboulos usj edu lb>
> > > To: <redhat-list redhat com>
> > > Sent: Wednesday, May 16, 2001 2:54 PM
> > > Subject: telnet authentication fails
> > >
> > >
> > > > Hi,
> > > >
> > > > I'm trying to connect to RH6.2 server through telnet on a LAN. The
> > > > authentication fails and I get the following in my
/var/log/messages:
> > > > (userX IS NOT root)
> > > >
> > > > login: FAILED LOGIN 1 FROM <IP> for userX, Authentication failure
> > > > inetd: exit status 1
> > > > telnetd: ttloop: peer died: EOF
> > > > inetd: exit status 1
> > > > inetd: exit status 1
> > > > PAM_pwdb: auth could not identify password for [userX]
> > > > login: FAILED LOGIN 1 FROM <IP> for userX, conversation failed
> > > > ...
> > > >
> > > > The telnet service is launched by the inetd. It seems telnet
couldn't
> > > access
> > > > "password files" for user authentication.
> > > > Does telnet use "/etc/passwd" or "/etc/shadow" for authentication?
> > > > Does anyone know what my problem might be?
> > > >
> > > > I would greatly appreciate any help, and thanks in advance.
> > > >
> > > > Regards
> > > > Nathalie

Telnet uses /etc/passwd or /etc/shadow depending on whether you enabled
shadow passwords.  This happens every time and only to the telnet service?
And other users can consistently log on?

I would create a new user and see if your user can use that new login.  If
so, I would examine the relevant files (/etc/shadow, /etc/passwd,
/etc/group) to see what the difference between the two entries are.

If a new login also fails, then you have other problems like the telnetd
server binary being hosed (for example and not to scare you, but trojaned
warez often misfire), the telnet client (please tell me it's not the windows
default) being used is not working (the "peer died"message is a fairly
common problem, I've never heard a good explanation of why it happens), or
network issuies are causing the problem (which, admitedly  sounds unlikely
given your description).

I suppose I'd be crass to solve your problem by suggest simply dumping
telnet in favor of OpenSSH?

-Alan