Users cannot change password after upgrading Domain Controllers to 2003.

pts.
Tags:
Microsoft Windows Server 2003
Microsoft Windows XP
Policies
Windows 2000 desktop
Windows client administration and maintenance
Hi there, We recently upgraded our DC's from 2000 to 2003, which were themselves upgraded from NT4. Since the upgrade users cannot change their pwds. Keeps coming back with the msg: "Your password must be at least 6 characters, cannot repeat any of your previous 5 passwords and must be at least 21 days old. Please type a different password. Type a password which meets these requirements in both text boxes" The pwd do match this criteria. If I check a user details on the Security tab the Everyone group is ticked to allow change passwords. So why isn't it allowing? It was possible to do this in 2000. We had some difficulty upgrading the AD, it is currently still in mixed mode. Do not want to change to native until this is sorted. thx. B!

Answer Wiki

Thanks. We'll let you know when a new response is added.

control and change your policy (Default Domain-Policy) entries

Discuss This Question: 6  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • DRAGONKZ
    As Jari11 said, Its your default domain controller policy (or some other sort of group policy you've got set up) doing this. From memory, by default, the "default domain controller policy" on a Win2k3 server has the exact same settings that you have mentioned. When you find the policy, the settings you need to look at are under "account policies" then "password policy" Good Luck! :-)
    0 pointsBadges:
    report
  • Melenie
    Hi, Windows Server 2003 includes more than 200 new policy settings. The new 2003 policy settings allow us (administrators) to control the behavior of among other things, Roaming user profiles and Group Policy. By default, Windows Server 2003 requires complex passwords for all newly created users. (Password complexity requirements may, however be disabled through Group Policy also.)I would start there first. Hope this helps.
    0 pointsBadges:
    report
  • DigitalCreature
    I recently setup a Windows Server 2003, when I was testing things and creating user accounts, there were problems with complexity of password, I am pretty sure the passwords I entered matched the criterias and requirements, but I sat there typing all these passwords and none worked, so I editted the policy to suit our network instead of the picky default settings, and it worked! Good luck!
    0 pointsBadges:
    report
  • GrahamPD
    This is more a side note, not related to your specific question. If you have multiple DCs I would suggest that upgrade one, do clean installs on the others. Once you have all the other rebuilt and back on the domain, nuke and do a clean install on inital box. This was highly recommended to us, versus using an upgraded box in production. It should eliminte problems and increase stability.
    0 pointsBadges:
    report
  • Elangeland
    This is just a guess, but the password age information may have been set when you did the upgrade, as I don't think the minimum password age condition was available with Windows 2000. If it has been less than 21 days since the upgrade, then the passwords don't meet the minimum age criteria yet. As others ahve suggested, you can change the Default Domain Policy to turn off the minimum age condition, or you can just wait for the 21 days to elapse.
    0 pointsBadges:
    report
  • Maclanachu
    Thx Everyone, Turns out that 21 days hadn't lapsed since we installed the new DCs was the criteria it was failing. They are now able to change passwords once again. Looks like the Default Domain Policy had been re-set or whatever when the new servers were installed. phew!
    0 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following