Windows XP client, 2003 server, user can't change password. Incorrect message about complexity requirements

- Windows 2003 servers (one Primary Domain Controller, one Backup Domain Controller)
- Windows XP SP 2 clients

Some users are unable to change their password, they get an errormessage "The password supplied does not meet the minimum complexity requirements....."

If I change the password on the server, it works ok.

The passwords tried absolutely meet the complexity requirements 100%, I've tried them on the client myself.
Does anyone know a solution to this annoying problem?
LVL 2
ITsAliveAsked:
Who is Participating?
 
Computer101Commented:
PAQed with points refunded (125)

Computer101
EE Admin
0
 
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
Are you sure that the passwords are meeting the complexity requirements?

The passwords must contain at least one character from 3 of 4 following groups:

Upper case - e.g.: ABC
Lower case - e.g.: abc
Number e.g.: 123
Symbol e.g.: !@#
0
 
ITsAliveAuthor Commented:
yes, I've tried  
Azerty..11
klm@1vbn

and several others, all of which are compliant.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
Well the password looks good. Are you enforcing password history? And if so, are they changing it to a previously used password?
0
 
ITsAliveAuthor Commented:
Not  sure about the password history, but one of these users is a newly created user (created it yesterday).
0
 
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
Well the only two other things I know to look for (which your example password fulfills) is a minimum of 6 characters and "Not contain significant portions of the user's account name or full name". I don't know what qualifies as significant.

Other than that I don't know what to tell you. I know event 627 in the security log is a password change attempt (success or failure) but I don't think it will give you much more information. But there may be some other entries that might be helpful...
0
 
ITsAliveAuthor Commented:
I just found this on the Microsoft site (http://support.microsoft.com/?kbid=273004), I'll give this a try first.
0
 
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
Nice find. It will be interesting to see if it works on 2003.

Keep us posted.
0
 
ITsAliveAuthor Commented:
Hi,

just to let you know: I've solved the problem using the info I found on the MS site, eventhough that article was for Windows 2000 server, not for 2003. Apparantly the same issue exists in Server 2003.
0
 
Jeremy WeisingerSenior Network Consultant / EngineerCommented:
Thanks for sharing.

Glad you got it fixed.

=)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.