07-18-2011
You get that error when
1. the account has been aged off - password is expired
2. the account is locked
You have to get the account cleared (re-enabled) on the remote box. You cannot fix it on your end.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Every one
I disable the root account entering wrong password for many time
How can I enable the root account
I am using Tru64 Unix V4.0G
Thank you (2 Replies)
Discussion started by: Syed_45
2 Replies
2. AIX
I'am set the root account locked ON, using smitty, so I can't login or su with root user in my AIX system, some one can help me to unlock root account login ???,
sample :
:~>su
root's Password:
3004-301 Your account has been locked; please see the system administrator.
3004-501 Cannot su to... (1 Reply)
Discussion started by: Maker
1 Replies
3. Linux
Hi all,
I've been using linux/unix now only for a couple of months and was doing ok until about 30 minutes ago...
I needed to reboot into my windows 2000 partition, so, in a terminal I typed:
shutdown -r now
which duly rebooted the PC for me. On getting to the OS selection screen I... (5 Replies)
Discussion started by: alarmcall
5 Replies
4. HP-UX
I knew I had had seen this somewhere:Q: How can I re-enable my root account when I typed in my password wrong 3 times and the account got disabled?
A: When your HP-UX system is in the more secure "trusted system" mode, your account is automatically disabled after
you have entered your password... (0 Replies)
Discussion started by: Perderabo
0 Replies
5. AIX
we have a user name "Test1" that account is alwyas locked out. The user has been used to many servers to ftp a file from the main server. i already increase the MaxStartups to 99. And still after how many days account will locked. (3 Replies)
Discussion started by: invinzin21
3 Replies
6. Solaris
Hi Gurus,
i have ussers cannot change their passwords, neither can root change the user's password.
O.S. Solaris 8
up−to−date on security patchaes as far as I know.
Examples (names have been changed to protect the guilty):
User logged on:
$ passwd
passwd: Changing password for <user>... (8 Replies)
Discussion started by: raziayub
8 Replies
7. Solaris
Hi,
I have enable Account lock for failed login attempts.
I have configured
1) /etc/security/policy.conf
2)/etc/default/login
To lock an account if it make multiple incorrect attempts to login to Solaris 10 server.
I can see the account gets locked in /etc/shadow.
I would like to... (1 Reply)
Discussion started by: menonk
1 Replies
8. UNIX for Dummies Questions & Answers
Hi
How do i list all locked account in my linux distributiion
I have tried
passwd -S -a
but it seems to not working .
My distribution details.
# lsb_release -a
LSB Version: :core-3.1-ia32:core-3.1-noarch:graphics-3.1-ia32:graphics-3.1-noarch
Distributor ID: OracleVMserver... (3 Replies)
Discussion started by: pinga123
3 Replies
9. Solaris
I am facing strange problem where after three failed login attempt user password must be locked. Actually what is happening, when I take the putty session of the server & enter user name on the prompt at the login prompt & then press enter to enter the password at this time when I checked the... (10 Replies)
Discussion started by: sb200
10 Replies
10. UNIX for Dummies Questions & Answers
I am facing an Issue with a particular Unix Account ( ie a particular Userid) getting LOCKED everyday between 7:30am and 8:00am. The Password associated with this particular Account has been setup such that it should never Expire at all but it does LOCK the Account after more than 3 failed... (5 Replies)
Discussion started by: pchegoor
5 Replies
LEARN ABOUT HPUX
userstat
userstat(1M) userstat(1M)
NAME
userstat - check status of local user accounts
SYNOPSIS
[parm]...
[parm]...
DESCRIPTION
checks the status of local user accounts and reports abnormal conditions, such as account locks.
If any parm arguments are specified, abnormal status is displayed only for those parameters, otherwise abnormal status is displayed for all
parameters. The section describes the various parameter values that can be used for parm.
Each account with an abnormal status is displayed on a single line. Each line contains the username followed by one or more parameters,
indicating what abnormal conditions exist for the account. The section describes the various parameters that can be displayed.
Options
The following options are recognized:
Display the status of all users listed in
(Quiet) Do not print anything to standard output.
This can be used when interested only in the return value.
Check the status of only the specified user
name. The user must be a local user listed in
Parameters
The parameters that could be displayed to indicate abnormal account status, or that could be used with the option, include the following:
is displayed if an administrator lock is present on the account. This lock indicates that the encrypted password in or begins with An
administrator lock can be set, for example, with
is displayed if the account is locked because the account expiration
date has been reached. days is the number of days that the account has been expired. See the description of the expiration field
in shadow(4).
is displayed if the account's password has expired.
days is the number of days that the password has been expired. days is displayed only if its value can be determined.
is displayed if the account is locked because there have been no logins
to the account for a time interval that exceeds the maximum allowed. days is the number of days that the account has been inactive.
See the description of the attribute in security(4).
is displayed if the account is locked because the number of
consecutive authentication failures exceeded the maximum allowed. num is the number of consecutive authentication failures. See
the description of the attribute in security(4).
is displayed if the account is locked because the account has
a null password and is not allowed to have a null password. See the description of the attribute in security(4).
is displayed if the account has a time-of-day login restriction.
times defines the time periods that the user may login. See the description of the attribute in security(4).
Security Restrictions
Users invoking this command must have the authorization. See authadm(1M).
is not supported for trusted systems.
RETURN VALUE
exits with one of the following values:
did not find abnormal status
found abnormal status
invalid usage or user not found
EXAMPLES
The following example reports all abnormal status for all local accounts.
The following example shows that the account for user is not locked due to too many consecutive authentication failures.
FILES
standard password file
shadow password file
user database
SEE ALSO
authadm(1M), passwd(4), security(4), shadow(4), userdb(4).
userstat(1M)