[jcifs] Problems with certain clients using NTLM filter
Alfie Kirkpatrick
Alfie.Kirkpatrick at ioko.com
Tue Feb 17 13:02:55 GMT 2004
Eric, many thanks. What are the drawbacks to option 2... that is, why isn't it the default?
Regards, Alfie.
-----Original Message-----
From: eglass1 at comcast.net [mailto:eglass1 at comcast.net]
Sent: Tue 17/02/2004 12:44
To: Alfie Kirkpatrick
Cc: jcifs at lists.samba.org
Subject: Re: [jcifs] Problems with certain clients using NTLM filter
The failing client appears to be set up to use NTLMv2 authentication; there
are two ways to fix this situation:
1) On the affected client, look at the registry value:
HKLM\System\CurrentControlSet\Control\Lsa\LmCompatibilityLevel
it's probably set to 3, 4, or 5. Set it to 0, 1, or 2. This setting is
described in detail at:
http://support.microsoft.com/default.aspx?scid=KB;en-us;239869
Setting it to 0 or 1 will do LM/NTLM (version 1); 2 will just do NTLM.
2) Set the jCIFS property "jcifs.smb.lmCompatibility" to 3. This will cause
jCIFS to use LMv2 (which is kind of a "stripped down" NTLMv2).
Either of the above should allow the client to authenticate properly.
Eric
More information about the jcifs
mailing list