Discussion Locked

Offline NT password

0 helpful
5 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
Traveling users who change their Windows domain user password while connected via the LAN on their desktop cannot log into the netwok when they dial up with their laptop PC. Cached account info is the old account name and password which the user logs in with. The user then starts the dial up software that authenticates to the domain using their new password. The local cached copy never gets updated. How chan they change the laptop cached account to match the account created in the LAN?

5 replies

by mmartinez108

To get around the issue immediately you can delete the *.pwl files.

The long term answer is in the procedure you follow to change the password. How is the user change his Network password? How does the user change the local Windows password?When you are prompted to change your network password because it has expired it will sync the network and the local password. Do you have any policies forced on to the computer?

by timwalsh

Are the laptop computers also using NT or something else?

There are 2 possible issues here:
1. If the laptop is using NT, then users are logging on to the local machine (instead of the domain) before dialing-in and authenticating to the domain. There are two different accounts here: the user account on the local computer and the user account on the domain. The only way to synchronize these is manually.
2. If you are using Win9x/ME, then the password is cached locally. In Win9x, it is possible to have 2 different passwords: the domain password and the local Windows password. Usually when a domain password change occurs from the laptop (if done properly), these 2 passwords remain synched. If done imporperly or from another location, then there is now way to resynch the passwords automatically. Therefore, your mobile users need to do 1 of 2 things everytime they change their password: either do it from the laptop (properly), or remove the users .pwl file from the Windows directory (on the laptop) (as mentioned in Answer 2). What this causes to happen is that the next time the user logs on to the laptop, Windows will no longer find a locally cached password, will ask the user to verify the new password, and the 2 willbe resynched again. This will have to occur each time the user changes his domain password.

Hope this helps.

by deltree

Are they using a roaming profile? If so, delete their local profile on the laptop and have them log in while the laptop is attached to the LAN. this will pull a fresh copy of their profile to the laptop.

by wagnerrc

Sorry, users have W2K on the client and the Domain controller is NT 4. All users log into the Domain not to a local account. Local accounts would prevent them from doamin resources, i.e. network folders, pcs'...

This discussion is closed to new replies.