5 replies
by sdbytnar
Is the user account in question connecting from any other locations? If so, that connection may have the incorrect password and is locking the account out. Have you tried have the user logon at a different workstation to see if the same thing occurs?
Sean
by bnagy
by ian mclaws
I think the key in your question is in the last sentence. Properly configured, a Win2K pro client logs onto the network once, only. It sounds as though your clients are logging on to their local systems instead of the domain. If the two passwords don't match, after a few attempted connections the account will be locked out.
The local account database in a properly configured 2K domain should have only the built in accounts, normally. Your users should not have accounts even defined in their local systems. To log on properly, instruct your users to enter username, password, then click the options button and use the third box to select a domain logon, instead of the default local logon. This should cure your woes.
You should also delete the local user accounts from your client systems. They serve no purpose and weaken your security.
When the 2kPro system joined the domain, it was given the ability to have all logon attempts authenticated by the domain controllers, instead of doing its own authentication. All you have to do is choose it.
Once the domain logon is chosen, you can close the options button again to simplify client logons.
Good luck,
Ian
by bnagy
by bnagy
This discussion is closed to new replies.
Trending Windows Forum posts
Sort by Trending