Replication with ADAM failed due to password complexity

[rowanld]

Hi all,

I'm using a password with special caracteres (like ♥, ♦,○ for exemple). I
haven't got problem to login using active directory but the replication with ADAM failed. Is there some restrictions in ADAM ? Witch ASCII code should we used to be sure password is replicated correctly ? Witch ASCII code mustn't be used ?

Thank You,

Olivier

[fumble]

Not sure if you've tried this, but go to DC and Run, secpol.msc. In the politics of the account or change the password policy "Passwords have to meet difficulty requirements" for disabled and testing of a job by forcing the policy on the computer and then try to reset your password. Not at all apply several templates to whatever thing without knowing what it essentially does. For all time make a backup of the default domain policy or never change at all and use one copy of it to make changes and set the order of priority. You can always delete the copy to quickly return to the original copy intact.

[EINSTEIN_007]

AD Replication failing with error 5 has multiple root causes. Attack the problem initially using tools like DCDIAG, DCDIAG /TEST:CheckSecurityError and NETDIAG that expose common problems. If still unresolved, "walk" the list of known causes in "most common, least complex, least disruptive order" to "least common, most complex, most disruptive" order. For more information visit this website - http://support.microsoft.com/kb/2002013

[Pabloa]

Can you tell us whether the configuration set is fully contained in an Active Directory domain, forest or forest trust? Also you should know that the configuration set should contain the Microsoft Windows NT 4.0 member servers. You can follow the below link to get more idea about the problem that you are facing:

http://technet.microsoft.com/en-us/l...=ws.10%29.aspx