Discussion Locked

User Lockout when signing onto NT Networ

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am trying to implement Account Policy with forced password changes, minimum password aging, lockout for 3 unsuccessful tries. Most users logon onto Novell 4x and NT networks symultaneously. Problem seems to arise after User Changes password. Gets locked out in future logins. Are removing PWL files and setting desktops to not save login name and password. Ideas as to what can be causing users to be locked out out? Indicating they are somehow attempting 3 or more times to login unsuccessfully.

7 replies

by jcannon1

It's sounding like that either NT or Novell 4x is not seeing the passwords changed. For example, the password is being changed in Novell but not on the NT network so when the use enters the new one more than 3 times, since it wasn't changed in NT, NT locks them out.

by smozden

Although the passwords for both are changed manually, they are being changed at the same time using the Control Panel Password Change app. We have a large Domain, 3000 Users with a number of BDC servers located all over the state. Is it possible we have a cache of the password somewhere which is not being updated?

by estebandelatorre

The problem arise with w9x clients more often
Because of the ESCape key, users are not force to log in to a domain (wheter or not defined (or requiered)), there may be some drive mappings to NT shares with the "reconnect at logon" check box. Once the users put a wrong password or press the ESC key, they are Locked OUT! .
This will not happens to WinNT users, since loging into the domain is a must in order to use the workstation

by shanghai sam

Thank you for the response. After reading and reading again, I realized the most significant part of your answer was that pertaining to the drive mappings. While the ESC key portion did not apply to our situation, the drives do. Was unable to find anything on Microsoft Web site about this.

by pxttocyob

This happens when users are prompted to change a password at the logon screen, and they do it. The secret is to have them NOT change the password while loggin on, but wait untill thay are on the network (and on both systems) and then use the controlpanel to change them all at once.
This way all the passwords will be synchronized. If they change one at login, the other system will not validate them because of a newly changed, cached password.

This discussion is closed to new replies.