[jcifs] Jcifs 1.3.17 & Isilon Server

Michael B Allen ioplex at gmail.com
Fri Jun 29 09:04:51 MDT 2012

On Mon, Jun 25, 2012 at 5:20 PM, Lummis, Patrick J <PJL at dolby.com> wrote:
> Howdy,
> Before I move up the software stack to VFS2 (commons-vfs), I'm experiencing
> the following...
> An issue has come up whereby the latest jcifs, jcifs-1.3.17, fails to
> connect to an Isilon server with credentials or as anonymous. Previous
> version, jcifs-1.2.13, connects fine.
> Furthermore, connecting to Windows SAMBA shares and Linux CIFS shares over
> the same network utilizing jcifs 1.3.17 works beautifully.
> Also, connecting to the Isilon share utilizing linux smbclient through the
> machine executing the jcifs 1.3.17 client also works as expected, which
> leads me to believe its narrowed down to the jcifs 1.3.17 distribution or
> VFS.
> The following is the thrown exception….
> Caused by: jcifs.smb.SmbAuthException: Logon failure: unknown user name or
> bad password.
>         at jcifs.smb.SmbTransport.checkStatus(SmbTransport.java:546)
>         at jcifs.smb.SmbTransport.send(SmbTransport.java:663)
>         at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:390)
>         at jcifs.smb.SmbSession.send(SmbSession.java:218)
>         at jcifs.smb.SmbTree.treeConnect(SmbTree.java:176)
>         at jcifs.smb.SmbFile.doConnect(SmbFile.java:911)
>         at jcifs.smb.SmbFile.connect(SmbFile.java:954)
>         at jcifs.smb.SmbFile.connect0(SmbFile.java:880)
>         at jcifs.smb.SmbFile.exists(SmbFile.java:1415)
>         at
> org.apache.commons.vfs2.provider.smb.SmbFileObject.doGetType(SmbFileObject.java:133)
>         at
> org.apache.commons.vfs2.provider.AbstractFileObject.getType(AbstractFileObject.java:497)
> Likewise, the same exception is thrown utilizing the SmbShell.java example
> code with jcifs 1.3.17.jar provided by the jcifs project.
> Any insight as to what may be going on? Is this a known issue with Isilon
> servers?

Hi Patrick,

Does the "Isilon" server support NTLMv2?

If not you must set jcifs.lmCompatibility = 0 and
jcifs.smb.client.useExtendedSecurity = false to force JCIFS 1.3 to use
NTLMv1 as it did in 1.2.

If the server really does not support NTLMv2, then you really should
figure out how to upgrade.

If this isn't the problem, there are other things we can try ...


Michael B Allen
Java Active Directory Integration

More information about the jCIFS mailing list