>From email@example.com Wed Sep 25 16:26 EDT 1996
Date: Wed, 25 Sep 1996 14:12:42 -0400 (EDT)
From: firstname.lastname@example.org (Frank Pardo)
Subject: rlogin failure.
Many thanks to those who responded:
Liew Chee Wah
The solution turned out to be deleting and recreating the problem user's
entries in /etc/passwd and /etc/shadow, like this:
useradd ...otherstuff... vlnntnne
passwd -d -f ...otherstuff... vlnntnne
rlogin -l vlnntnne ...thismachine...
At which point user "vlnntnne" was asked to choose a new password, which
he did, and all was well.
The problem analysis never did get finished. I don't know exactly what
was wrong with /etc/passwd or /etc/shadow (or both). Doesn't seem very
important at this point...
* * * * * * * * DIGEST OF ORIGINAL QUERY
I created two dummy users for testing purposes; one of them can rlogin,
and the other can't. Can anybody suggest what's wrong here? Or how to
analyze the problem further?
[followed by some examples of the differences between the two users]
* * * * * * * * DIGEST OF SUGGESTIONS
Date: Wed, 25 Sep 1996 15:30:11 -0400
From: email@example.com (Manjit Singh)
"Login incorrect" apears when you enter the wrong passwd. Check the passwd
or just take out the passwd entry from /etc/shadow file and try again just
hit enter when it asks you for the passwd.
Date: Wed, 25 Sep 1996 15:32:06 -0500 (CDT)
From: Asim Zuberi <firstname.lastname@example.org>
are you using NIS or NIS+. If not, than find out that the passwd file
on m/c garcia does the user vlnntnne exits.
Date: Wed, 25 Sep 1996 13:17:23 -0700
From: A.Chan@CdnAir.CA (Alan Chan)
Make sure you can indeed login on your local host first.
I suspect you have some "funny" characters in your password that
the system doesn't like.
Date: Thu, 26 Sep 1996 14:20:52 +0800 (GMT+0800)
From: "Liew.Chee.Wah" <email@example.com>
Have you check whether the account is locked ? ( check on the /etc/shadow
file ). If the account is locked, we still can su to the user but unable to
login as the user using rloigin or telnet.
Date: Thu, 26 Sep 1996 09:00:49 +0200
From: Casper Dik <casper@holland.Sun.COM>
Could be a shdow entry or kastlog problem which may cause the system to think
the accoutn has expired.
You can try truncating /var/adm/lastlog and see if that helps.
* * * * * * * *
-- Frank Pardo <firstname.lastname@example.org> System Administrator Transaction Information Systems New York City
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:11:10 CDT