Discussion Locked

Users cant change p/w in W2K domain

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I administer a Windows 2000 network which was upgraded from NT4 domain by performing an in-place install of Win2K on the NT PDC. Since then we have had a problem with some (about 30) of our 300 or so users who are unable to change their passwords.When they attempt to change them, they get an error message stating that they are unauthorised to change their passwords. I have searched the Microsoft website, knowledgebase and Technet and so on without finding a solution to this. Any help that can get rid of this problem would be appreciated, I don't want to have to keep changing thirty or so user password every month for the rest of my life! Plus I think that the network should work as advertised...

9 replies

by cg it

I take it that Active Directory is running on the W2K PDC. Question: are all the users who can't change their password members of the same group? [e.g. domain users or domain power users or some group like that?]

by cg it

If their AD account doesn't show them having the restriction of not changing their password, then some group policy is in effect that does not allow them to change their password. Try resetting the group policy for those users.

by nick_t

Currently all my user accounts are still sitting in the Users container as I have not yet moved them into the OU structure. The only group policy that has been applied has been at the domain level (there is only one domain in the forest) and I have gone through it with a fine toothed comb trying to find a setting that might be effecting the users - to no avail.

by nick_t

Thanks for the response D.R.
AD is running on several servers (now) in the domain. The original PDC was later de-commissioned (after transferring masters of operations to other DCs)
The only group the users have in common is Domain Users. Otherwise they appear to be spread across both our main sites, in different departments etc.
Waht do you mean by re-setting the group olicy for those users? (please excuse my ignorance, I am fairly new to W2K)
I have only recently applied some GP settings to the entire domain - unrelated to this problem - but was unable to find an apparently related GP setting that would explain this behavior.
I have already studied the mentioned MS articles - did not help, unfortunately.
Does this info give you any other ideas?

by cg it

upgrading to W2K with AD from NT has it problems. If only 30 users out of 300 have the problem, I would say recreate their account.

For Group Policy open the group policy snap in on the PDC [click run type mmc. When the console opens up click file, open and find the group policy snap in [it's gotta be there, default group policy minimum, unless no one's made one up] This sets the group policy for users, computers, etc....everything from hiding the shutdown tab on the welcome screen to password etc.

Also Active Directory user accounts controls users passwords unless group policy takes precedence. Look up the users who have password changing problems in the Active Directory users and computers console and check their accounts. If they CAN change their password as per Active Directory, the group policy for those users might override that with a do not change.

I'll make a suggestion. find Joseph Moore, Maxwell Edison, Tim Walsh, or DKlippert. These guys know more about WIndowsNetworking than Microsoft does.

by cg it

Security settings in W2K environment are multi-layered. There's the Domain Security settings which you see in the administration tools. There's the Active Directory users account settings, there's group policy and then there's the local computer security settings. The multi-layered approach is parent/child based. If you set security settings at a child level say local computer, but the domain level for that setting is different, the domain level security setting will override the local. Group Policy will also apply to users in OU's or in groups or singularly. Gets confusing without a road map. So you might think you set them but have not.

by ewgny

From what I recall passwords must be changed on the DC that is the PDC Emulator, I think there is a policy setting that forces the client to authenticate to a DC of your choice. Make sure they authenticate to the PDC emulator and see what happens.

by nick_t

Because it only happens to a relatively small, fixed group of users and for them it happens all the time, I do not see how this could be the cause. I do not want to force all my users to authenticate to the DC with the PDC emulaotr becauseat least half of them are on the other end of a relatively narrow WAN link which has a heavy traffic load. If the problem was intermittent then I could see your point, but I am afraid it is not relevant to my problem, unfortunately

This discussion is closed to new replies.