Re: LDAP auth fails

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Assuming you're actually using the correct user name and password, then the
only thing that springs to mind is that you're using a different GINA to
hash your password, therefore the hash doesn't match when the DC performs
its lookup. This can happen if you're using NTSE or the newer Protect Tools
if it's not deployed everywhere, or you're not providing the obfuscated
password.

Does the NETDIAG test run successfully as a different user?

Does this happen on any other machines? It might not be the DC, it could be
the workstation. It won't harm if you reset the secure channel on the
workstation, but I can't see what difference that will do (but now that I've
said that it'll probably do something).

--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net


.

Relevant Pages

  • Re: No LM Hash - no really
    ... > i can see the policy cascaded down to my workstation, ... How do you know that was the LM hash being cracked? ... > phrase, and then that new pass phrase is instantly recoverable from the ... the NTLM hash crack in mixed case. ...
    (microsoft.public.win2000.security)
  • Re: Newest kde onto stable
    ... Hash: SHA1 ... and unstable has 3.3; they're both fit for workstation and PC use ...
    (Debian-User)
  • [9fans] Acme-SAC fstat issue?
    ... Hash: SHA1 ... What does it mean when acme-SAC says: ... between this workstation and the primary domain failed? ...
    (comp.os.plan9)
  • XP breakin
    ... Hash: SHA1 ... It appears that someone is broken into my xp workstation and changed ... my passwords. ...
    (comp.os.ms-windows.nt.admin.security)