[jcifs] jcifs.smb.SmbException: The parameter is incorrect.
Michael B Allen
ioplex at gmail.com
Wed Dec 15 12:21:10 MST 2010
An "Invalid parameter" error is very generic and could be caused by a
number of things including but not limited to incorrect configuration
or a bug in JCIFS. You would have to post a stack trace and code
fragment (or identify which example program you're trying) for a
further diagnosis. Your previous CreateFile example looks valid
(although you duplicate some properties and the
jcifs.smb.client.domainController property is not applicable in this
case). A wild guess at this point is that it could be due directly or
indirectly to disabling NTLMv2 using the jcifs.smb.lmCompatibility=0
and jcifs.smb.client.useExtendedSecurity=false properties. Most
servers do not do NTLMv1 anymore. If you remove those properties does
the CreateFile example then work?
If you have questions about Jespa, please direct those to IOPLEX
support. Jespa questions will not be answered here (nor will any
questions about HTTP authentication).
Michael B Allen
Java Active Directory Integration
On Tue, Dec 14, 2010 at 4:01 PM, Carl Dubois <c.dubois at f5.com> wrote:
> Carl Dubois <c.dubois <at> f5.com> writes:
>> New to jcifs. Using jcifs_1.3.15.jar which I assume has this parameter fix in
>> it, per the IOPLEX Jespa documentation.
>> So this only means that the parameter is actually incorrect?
>> Can someone confirm the smb syntax for me? This is just a test domain.
> From prior posts it looks as if most recommend Jespa for NTLMv2 authentication
> against a DC. Tried a 2003 r2 windows server with NTLM v1 and failed as well.
> Can someone get me on the right track here?
More information about the jCIFS