- Joined
- Mar 6, 2014
- Messages
- 9,553
A few quick points regarding NTLMv1 vs NTLMv2:
If NTLMv1 works, but NTLMv2 doesn't try the following:
- NTLMv1 is utter crap. Horrifically insecure. Don't use it in a business environment.
- MS claims windows is supposed to automatically negotiate the highest supported protocol, but I have heard this is a lie. Windows does what it bloody well pleases. Disable LM and NTLMv1 on clients to prevent auto-negotiation stupidity.
- I believe samba stores the same password hash for NLTMv1 and NTLMv2. The key difference is how the challenge-response is calculated.
If NTLMv1 works, but NTLMv2 doesn't try the following:
- Disable LM and NTLMv1 on client
- Verify that Netbios name, workgroup, hostname are set correctly and consistently.
- Authenticate using UPN
<netbios name of server>\<UserName>
. I.e. for user "bob" on "freenas"freenas\bob
- From samba-technical - "The primary use of NTLMv1 is MSCHAPv2 for VPNs and 802.1X. For example, PEAP/MSCHAPv2 for wireless network or VPN authentication with RADIUS will need this option enabled."
Last edited: