|Subject:||Incorrect password Error Code?|
|Posted by:||Oscar P. (Osca…@discussions.microsoft.com)|
|Date:||Mon, 25 Feb 2008|
In my ADAM prod environment, when bind attempts fail due to bad password, the
error written to the sec log uses the 0xC000006D error code for "bad user
name" rather than the 0xC000006A code I would expect.
I could have sworn that it used to return 6A with bad passwords although
looking back through the archives a couple months I only see the 6D.
However, I have confirmed that my dev environment correctly returns 6A.
Any ideas out there?