10 replies
by dft3
by kevin h.
by mjervis
We have expierienced this problem in the past.
1. On the NT Server go to User manager and double click on the user in question change the setting from password never expires to change password at next login.
2. On the win 9x machine go to Start>Find>find files and search for *.pwl
3. Delete the person you are having problems changing the password and reboot
When the system comes back up login as that user you should be prompted for a password and to confirm new password. After youconfirm the new password make sure you go to the NT server and set the user domain setting back to password never expires (or whatever setting your protocol calls for).
by kevin h.
by portertech
The first proposed answer might resolve your problem. With win95 networked into NT server, you typically have 2 passwords at work: one for the PC itself, the other for the network.
The password for the PC is stored in a .pwl file in the windows directory. This is known as the windows password (not to be confused with the MS Network Password. The windows password exists to support unique profiles for users on the pc. This works fine in a home environment, but can be a user/maintenance headache in a network environment. Additionally, the windows password offers no securiy for any files on the workstation. Anyone can hit ESC past the login, and the computer will be fully functional with full access to all its local drives.
I suggest doing the following on win95 stations in a network environment: (1) Be sure unique profiles are not activated for the PC. (2) After deleting .pwl files, restart the machine and when prompted for a windows password, leave it blank.
Now when users go to change their
by kevin h.
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending