Unsolved
This post is more than 5 years old
54 Posts
0
53175
Account locked
Hey guys,
I kind of forgot the sysadmin password, and need to iterate them...
Can anybody tell me how the PAM settings are set on the Data Domain 2500 ?
i.e.: How many time will it take to let me try another login attempt after a failed one ?
Thanks.
jbrooksuk
208 Posts
0
May 22nd, 2014 01:00
I think the timeout to allow another login is about 10 minutes after multiple failed log in attempts.
You may need to disconnect and reconnect to get another attempt.
Regards, Jonathan
iimnordic
19 Posts
0
June 2nd, 2014 00:00
Account is locked for 1minute before you can make a new login attempt,
Keep in mind sysadmin password by default is the Serial number,
If you have changed it and cant remember any passwords there is a factory reset option avaliable wich will make the serial number the password for account Sysadmin , Keep in mind factory reset deletes all backed up data on the DD-system.
So my advice is to think realy hard and try to remember the password
Jim-10
7 Posts
0
June 2nd, 2014 04:00
If you ever to get log on you can avoid this situation happening again.
SSH can be configured on your desktop with putty or Linux/Unix so that you can logon without a password. This technote explains how to set this up on a Data Domain box.
See https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000tNK
Using Secure Shell(SSH) Article Number:000181556
DELL-Leo
Community Manager
Community Manager
•
6.1K Posts
0
June 17th, 2014 20:00
Hey Labonte,
There is a lockout that occurs after three failed attempts to login. The lockout period is two minutes but will reset after each failed attempt after the initial lockout. Older Data Domain systems used “abc123” as the default password. On newer systems the default password is the system serial number. Because the default password changed, it is common for the incorrect password to be entered as installers are used to the older default password. Another common cause of lockout is that passwords are case sensitive and can be entered incorrectly.
On DD OS 5.4 and greater, to increase security, the lockout time was increased to 5 minutes with 5 unsuccessful and each additional attempt will increment the timeout. An example of this would be a system where the incorrect password was entered 10 times. Each unsuccessful attempts will increment the timer an additional 5 minutes. that means this system will have a 30 minute period that the system logon is locked.
For more info, please refer to this article.
System Password Not Working
Hope this helps!
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
December 22nd, 2014 07:00
Thanks ,
its been a help
LeonardB3
6 Posts
0
February 23rd, 2015 07:00
so with this math 23 failed logins would be 75 minutes?
Anonymous
5 Practitioner
5 Practitioner
•
274.2K Posts
0
April 4th, 2016 05:00
I have a DD990 running OS 5.4 that has been locked for over 2 weeks now, any suggestions on how i can unlock it?
umichklewis
1.2K Posts
0
April 4th, 2016 05:00
Keep in mind, too - if you have any external tools that authenticate via SSH, such as Data Protection Advisor, if it's using the wrong password, this will also keep you from being able to login, too!
ble1
14.3K Posts
0
April 4th, 2016 05:00
I doubt it is locked - most likely not the same password. Unless there is process which keeps trying to get in using that login/pass which is not correct to keep it locked all the time. From autosupport you should be able to see in messages if something like this is going on. If not, you will need to log in as some other (admin/ddboost) user, go into SE mode and reset it from there. If you don't know how to do this, ask EMC (wait, you are EMC... you should reach one of your colleagues from DD department).
Filip Hasa
1 Message
0
August 14th, 2018 01:00
hi, disable/enable worked for me. I was able to login again. Thank you Filip
rblindberg
1 Message
0
September 27th, 2022 10:00
Appears that when the site self signed certificate expires that login will fail with an unknown error and will eventually lock the user account you are logging in with.
What fixed it for me was generating a new self-signed-certificate.
Procedure is as follows:
Login via SSH and then at the command prompt:
then:
if any of the users show locked then:
That did if for me!