[jcifs] NTLM usrname/password failure after each 5 mins

Michael B Allen mba2000 at ioplex.com
Tue Jul 18 22:25:35 GMT 2006

Refcounting basically just forces the transport to stay open in which
case you might as well just make the soTimeout some huge value like
10 hours. As long as a new session was created every 10 hours causing
communication with DC it will never close (unless the DC closes it).

I doubt Alepods problem is the jcifs.smb.client.soTimeout value though
because the test script would have to use the cache cred in the HTTP
session for the DC transport to be idle long enough and timeout. But if
that were true he wouldn't get the error in the first place because the
cached cred would bypass any further authentications. If the container
is expiring sessions every 5 minutes that might change the diagnosis
so hard to tell ...


On Tue, 18 Jul 2006 16:35:07 -0500
"Tapperson Kevin" <Kevin.Tapperson at hcahealthcare.com> wrote:

> We have experienced issues with transports being closed in the middle of
> the multi-step handshake process.  We implemented some basic reference
> counting in the SmbSession and SmbTransport classes to alleviate this.

Michael B Allen
PHP Extension for SSO w/ Windows Group Authorization

More information about the jcifs mailing list