Results 1 to 3 of 3

Thread: Incorrect password Error Code?

  1. #1
    Join Date
    Jan 2006
    Posts
    278

    Incorrect password Error Code?

    I am using ADAM prod environment, and when bind attempts fail due to bad password, the error that is shown to the sec log uses the 0xC000006D error code for "bad user name" instead of the 0xC000006A code that I should be getting. It normally used to return 6A with bad passwords though looking back through the archives some months ago, I can only see the 6D. But I confirmed that my dev enviroment properly returns 6A. Can anyone please help.

  2. #2
    Join Date
    Jan 2006
    Posts
    830
    There are some ways to do it, but it is not a good idead to run ADAM, or any other software, on a DC, you will make it more vulnerable. So, the first option would be, if you are on the machine itself, then ckeck HKLM/Software/Microsoft/Windows/CurrentVersion/ADAM_Shared key. Among something other, it contains version strings of installed ADAM binaries. ADAM 1.0 version is 1.0.XXX.XXX, ADAM SP1 is 1.1.XXX.XXX.

  3. #3
    Join Date
    Oct 2005
    Posts
    792
    The other option would be, if ADAM is running, and you can connect to it through LDAP, then read dsaVersionString from rootDSE. You will have to explicitly request this attribute, as it is not returned by default, and you should have admin priviledges in this ADAM instance, which also means you have to issue a bind before reading this value.

Similar Threads

  1. Replies: 3
    Last Post: 04-09-2011, 08:06 AM
  2. Replies: 5
    Last Post: 27-10-2010, 06:27 PM
  3. Replies: 9
    Last Post: 27-10-2010, 01:30 PM
  4. Replies: 3
    Last Post: 16-08-2010, 12:39 PM
  5. Windows live messenger error: password is incorrect
    By Ekadant in forum Windows Software
    Replies: 3
    Last Post: 30-03-2009, 12:36 PM

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •  
Page generated in 1,717,388,528.97154 seconds with 16 queries