Discussion Locked

Account Disabled/Lock out

0 helpful
16 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Recently I have been getting "bumped off" the network. I can see everything, but when I try to save work, or go to another drive - I don't have access. When I check my account on an NT Server, I find my account is disabled/locked out. I have fiveNT4 Servers, and two other Win2000 Servers. I want to resolve the conflict so I don't get lock out of the network permanently. Thanks. Robert

16 replies

by carydahl

This would happen if a user has entered an incorrect password too many times with Either you learn to enter the password correctly or check the password never expires option.

by stillatit

When your account was set up in each domain, your administrator had various security settings enabled. One of these causes your account to be automatically disabled if you try to log in and enter the wrong password some (settable) number of times ina row. If you do this, the system will lock out your account for a (settable, may be infinite) number of minutes.

All accounts except the built-in administrator account are subject to this feature if it is turned on.

The accounts can be manually reset by an administrator using the User Manager for Domains program. Bring up the account and clear the "Locked out" checkbox.

If you are in a domain environment and all servers are members of the domain, you need to change this only on the domain. If you are in a workgroup environment this needs to be checked on every server.

Note also that in a workgroup environment if you plan to attach to various servers, your username and password must be the same on all of them, or you must specifiy your username and password as you attach to each server. This could be part of why you are being kicked out. If your password is not the same on all boxes, when you are logged on to box A and try to mount a disk on box B, it asks you for a password and you fail multiple times to attach, you will be locked out of box B for the time-out period.

If you are not the administrator, you need to talk to your administrator. If you are the administrator you need to examine the accounts you are using.

Good luck.

by cryingdragon

I've seen this many times on my network.
It usually takes place when a user is
logged onto one machine and later logs
on to another machine and changes his
password without logging off of the first
machine. Since the user is still
connected to the first machine, the "old"
password is being passed along and
locking out the "new" password.

Find out if you are logged on to another
location and log out of that one.

Hope this helps.

Mike

by robertd.

After much searching, I did find a machine on the network that I was logged on - before I changed my password. Once I logged off that machine, the system accepted my password completely, and all disabled/lock out problems were resolved. Thanks to everyone for the help.

by vagab0nd

If you have administrative rights, run User Manager for Domains, open Policies menu, choose Accounts. In window appeared take a look at Account Lockout part.
There you can specify number of bad attempts until lockout, lockout counter reset and lockout duration.
The last is the one you need. Set some reasonable time after which your account will be automatically unlocked.

If you don't have administrative priviledges you need to talk to administrator.

by kaisersose

This is a problem I've come across many a time before. The reason the account is locked out usually is because that account is being used to authorise the startup of NT services on machines on the network. Check any machine on the network which you have had dealings with. In control panel, services check 'startup' on each service to see if your account is being used - if it is change it to an account that has equal rights but which has 'account never expires attribute ticked'.
The password being used along without your username could be an old password so everytime the service trys to start it causes an incorrect password count. The admin of the domain decides how many incorrect trys you're allowed before getting locked out!

by jlcampbell

Does this seem to happen after a particular time? Say, when your company?s normal workday is over (i.e.: 5:00pm or so)? If it does, check the Logon Hours settings in the User Man. for Dom. Changes are your logon time has expired and your NT systemis not set to warn you or kick you off, just prevent you from making new connections and using resources after a set time (you can verify this by opening the Policies/Account menu and looking at the checkbox at the "Forcibly disconnect.." at the bottom).

If you have Admin rights, adjust your logon hours as you see fit, but remember, someone adjusted them that way for a reason in the first place (probably to kick everyone off the system to run the network backups).

by donhuffman

I believe I know your frustration. Answer #2 is about right on all the rest that I read are not what you are talking about right? If you have drives on other boxs mapped on your workstation and your login on the other boxs is different than the one on your machine then when you log on to your box OS tries to automatically log on to mapped drives. Wrong password hammers at login and gets account locked out. Change all accounts to have same login and password usually solves this problem. Sure way out is to not have mapping connect automatically upon login. There is a check box for this when setting up the map.

This discussion is closed to new replies.