root login fails

[David Rodman]

My admin guys changed all the passwords on the system. Now I can't login
as root - but I can su to root with the new password. A user account that I have
has the same problems.
Running a trusted system, HP ux 11.00

I tried reseting the user account by deactivating and them reactivating it.
The reactivate noted that the user account was locked by admin and by too many
mistypes. No change to the logins. I was afraid to try this on root.

Anyone with bright ideas?

[Andy Monks]

Try logging on as root on the console. It should always let you on here. The reset it.

[Antoanetta Naghiu]

Hi,
I'm not sure I clearly undersood what you are looking for.
If your system is converted to trusted system and you want you re-enable a user that has been locked, the easiest way is to go to sam->accounts for users and group-users->>highlight user name->actions->activated. You can to cd /tcb/files/auth/user's_login_initial
vi the user's_name_file
and modify it the file but it is not recommended.

[David Rodman]

Yep, been to sam as well atleast for the user. As I stated I have
the same problem on the root and a user account.

[David Rodman]

Im not 100% sure I tried from the console, but even so changing the
password is not a problem. I su (ed) in this morning and changed it.
Still can't rlogin or telnet in with root.

[Andy Monks]

One thing you could try, is to untrust the system (see if the problem persists) and then trust it.

While untrusted change the password anyway before trusting again. Sam can untrust the system

[Antoanetta Naghiu]

check /etc/securetty file if exist and contains the word console on it, this is way. That enable root to login directly only from the console. If you want to login as root directly from any terminal or telnet or login, delete /etc/securetty.

[Kofi ARTHIABAH]

Hi David: For a trusted system, a /etc/securetty file is created to prevent root logins remotely. If you want to be able to login (with telnet or rlogin) you will have to remove the /etc/securetty file... although I think you should leave it in place if you want the extra security it offers.

Good luck.
BTW you might want to look at setting up ssh.