GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Re: Trusted Mode
Operating System - HP-UX
1847054
Members
5009
Online
110261
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Go to solution
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2008 01:24 PM
04-03-2008 01:24 PM
I have an hp rx2620, HP-UX 11i V2. I put the server in Trusted Mode today and now all accounts are locked, including root. I get permission denied trying to log in via ssh and telnet. Any ideas?
Solved! Go to Solution.
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2008 01:44 PM
04-03-2008 01:44 PM
Solution
root is always allowed via the console whether disabled or not. ( this is ASSUMING the message during login failure states that the account is "disabled")
If somehow all users ended up with an "*" in their password field just prior to the conversion then the only way to get in is to crash the server and boot to single user so you can set the root password. Try the console first.
Once you get on you can run the usernames through a loop to unlock.
cat user.list|while read list
do
modprpw -k $list
done
getprpw username to list the status' of the user.
If somehow all users ended up with an "*" in their password field just prior to the conversion then the only way to get in is to crash the server and boot to single user so you can set the root password. Try the console first.
Once you get on you can run the usernames through a loop to unlock.
cat user.list|while read list
do
modprpw -k $list
done
getprpw username to list the status' of the user.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2008 01:45 PM
04-03-2008 01:45 PM
Re: Trusted Mode
When system is on trusted mode you must define a how many times the users are allowed to try log on the system and once you reach it the only way to unlock accounts is via sam with the user root.
If root is locked then you must login from the console and this will unlock the root account.
Regards!
If root is locked then you must login from the console and this will unlock the root account.
Regards!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-03-2008 02:11 PM
04-03-2008 02:11 PM
Re: Trusted Mode
This is normal if you use the un-recommended method to convert: tsconvert. The recommended method is to use SAM which will run tsconvert and also modprpw -V which resets the access times of all the user accounts. Just connect to the console (required) and login. Then run modprpw -V. If root's PATH is incorrect, you'll have to use the fullpath:
/usr/lbin/modprpw -V
Bill Hassell, sysadmin
/usr/lbin/modprpw -V
Bill Hassell, sysadmin
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2026 Hewlett Packard Enterprise Development LP