[jcifs] Connection Timeout
Michael B Allen
mba2000 at ioplex.com
Thu Jan 26 01:19:42 GMT 2006
On Wed, 25 Jan 2006 15:32:43 -0500
"Tony Thompson" <tony.thompson at stone-ware.com> wrote:
> I am using jCIFS 1.2.7 running against Samba (YAST says
> 3.0.14a-0.4-suse) on a SuSE Linux server. I am having an issue that
> appears to be the same as was reported here:
> I only notice it failing after the connection has been idle for a while
> (like the Linux server decide my client was done and should go away).
> If I retry the request after it fails, it works. I did a packet trace
> of the failed attempt and the server is responding to the SYN request
> and even part of the conversation starts but then the server doesn't
> appear to respond with an SMB Protocol Response packet. I am attaching
> the packet trace (hopefully it makes it).
> I have never noticed this happening with a Windows server so, I am not
> sure if it is a Samba or a jCIFS issue.
Interesting. The capture only has 5 frames in it but indeed it shows
a SYN, to which Samba responds, and then what looks like a legitimate
Negotiate from JCIFS, to which Samba does NOT respond. It wouldn't exactly
hold up in court but if it's true, I think it might be a Samba bug.
Can you temporarily increase the samba log level to see if anything
interesting is logged when Samba doesn't respond to the Negotiate?
Or if you don't feel like wearing your Sherlock Homes hat today you
might just try upgrading Samba to the latest. The Samba guys probably
won't look at the bug seriously unless you try a 3.0.20 version anyway.
More information about the jcifs