max xmit default to 0x4104 (16644). Why ...
donmccall1 at yahoo.com
Mon Nov 3 20:14:03 GMT 2003
As I recall, it WAS reading from the server that showed the issue; you'd end up getting twice the reads you would expect; What my customer was experiencing was:
On a read customer would expect to see 61440byte packet sent,
they have traced and found that it (samba) is sending 61377byte packet request
on the read and then 63byte request to make up the rest of the request.
This was happening when the client was an NT 4.0 sp6 client.
A Win2k sp2 client did not evidence the problem. And they were seeing it doing drag and drop in the NT explorer from a samba share to their local drive.
Hope this helps,
Richard Sharpe <rsharpe at richardsharpe.com> wrote:
On Mon, 3 Nov 2003, Jeremy Allison wrote:
> On Mon, Nov 03, 2003 at 10:43:34AM -0800, Richard Sharpe wrote:
> > In addition, I have copied a 1.3GB file from Samba to Win2K using DOS (as
> > I said above) with max xmit set to 65535 and 32768 and there appears no
> > subjective difference in the time taken. I will now try it with the
> > Explorer, which seems to be the issue as well.
> That's because max xmit doesn't affect the SMBWriteX calls
> I don't think, or at least not the "large write" version.
However, it was using Read&X calls ...
I think I have an example of the problem. I think the explorer has
problems with a max xmit of 65535 when copying files from Samba to Win2K.
I will look at the trace.
Richard Sharpe, rsharpe[at]ns.aus.com, rsharpe[at]samba.org,
Do you Yahoo!?
Exclusive Video Premiere - Britney Spears
More information about the samba-technical