[jcifs] Dealing with simultaneous users in a Win2k3 environment

Michael B Allen mba2000 at ioplex.com
Sat Mar 20 00:21:43 GMT 2004

Michael Kerley said:
> Thanks for the quick reply.
>> > 1. new SmbFile("smb://").listFiles()  --> Fails (expected because no
>> > authentication was given)
>> Actually I don't recall ever seeing this fail. All systems that I work
>> with use null credentials to get the list of domains. Maybe Win2k3
>> changed
>> that. Donno. What was the error?
> I think Win2k3 did change it.  Here's what I'm seeing:
> jcifs.smb.SmbException: Unverifiable signature.
>         at jcifs.smb.SmbTransport.send(SmbTransport.java:681)
>         at jcifs.smb.SmbSession.sessionSetup(SmbSession.java:138)
>         at jcifs.smb.SmbSession.send(SmbSession.java:102)
>         at jcifs.smb.SmbTree.treeConnect(SmbTree.java:125)
>         at jcifs.smb.SmbFile.connect(SmbFile.java:580)
>         at jcifs.smb.SmbFile.connect0(SmbFile.java:550)
>         at jcifs.smb.SmbFile.list(SmbFile.java:1149)
>         at List.main(List.java:36)
> (List.java is not the same one included in the jCIFS examples)
> The only time I ever see "Unverifiable signature" is when I try to do
> something in this Win2k3 environment.

The unverifiable signature error should never happen. But the jCIFS
signing code is flawed for reasons that have not been identified. See the
0.7.19 release bullet on the jCIFS site for a link that describes the
details of the problem. I suspect the errors you're encountering are
related or a similar problem. Unfortunately I do not have a Win2k3 machine
to test and fix this. The signing code should probably be disabled by
default (try setting jcifs.smb.client.signingPreferred=false maybe).


More information about the jcifs mailing list