The LM authentication protocol uses the LM hash. NTLM, NTLMv2, and Kerberos all use the NT hash, also known as the Unicode hash. For backward compatibility, Windows 2000 and Windows Server 2003 support: However, versions of Windows earlier than Windows 2000 don't use Kerberos for authentication. Windows 2000 and Windows Server 2003 servers can authenticate users that connect from computers running earlier versions of Windows. This article describes how to make Windows only store the stronger NT hash of your password.

So you may want to prevent Windows from storing an LM hash of your password. The LM hash is relatively weak compared to the NT hash, and it's prone to fast brute force attack. These hashes are stored in the local SAM database or Active Directory. When you set or change the password for a user account to a password that contains fewer than 15 characters, Windows generates both an LM hash and a Windows NT hash (NT hash) of the password. Instead, it generates and stores user account passwords by using two different password representations, known as hashes. Windows doesn't store your user account password in clear-text. This article provides three methods to prevent Windows from storing a LAN Manager (LM) hash of your password in Active Directory and local Security Accounts Manager (SAM) databases.Īpplies to: Windows 10 - all editions, Windows Server 2012 R2 Original KB number: 299656 Summary

Windows 98 computer