samba - Sep 1999 - Transfering large files

Hello!

I've been seeing some weird problems with transfering large files from a
Samba (2.0.4a[1]) server to Windows clients. Sometimes (but not always) the
Windows client will stop copying the file after a few megs and claim that
the share is no longer available (it is, of course).

This used to happen *a lot* with the default read/write buffer of 8k. The
buffer is now 250 K, which has almost eliminated the problem (aswell as
speed things up). But the problem still seems to exist.

I've searched the archives and I found a message from someone else having
the exact same problem (but on an older version of samba); but I didn't find
a solution.

Does anyone have an idea what might be causing the behavior? Could it be a
configuration problem, or is it definitely a bug in samba (or, perhaps more
likely, a bug in Windows that is triggered by samba)?

[1] It will be upgraded pretty soon, but judging by the changelogs, this
particular problem has not been addressed

Thanks!

-- 
/ Peter Schuller

PGP userID: 0x5584BD98 or 'Peter Schuller
<scode@scode.webprovider.com>'
Key retrival: Send an E-Mail to scode-getpgpkey@scode.webprovider.com
E-Mail: scode@scode.webprovider.com Web: http://hem.passagen.se/petersch
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 248 bytes
Desc: not available
Url :
http://lists.samba.org/archive/samba/attachments/19990919/7c857df4/attachment.bin

On Sun, 19 Sep 1999 scode@scode.webprovider.com wrote:
> I've been seeing some weird problems with transfering large files from
a
> Samba (2.0.4a[1]) server to Windows clients. Sometimes (but not always) the
> Windows client will stop copying the file after a few megs and claim that
> the share is no longer available (it is, of course).
> 
> Does anyone have an idea what might be causing the behavior?
> 
See my message to the list on Sat 18th Sept
about "oplock and SCO 5.0.4" which is essentially the same problem.
I found that setting "oplock = False" in the smb.conf made the problem
go
away, but thats not exactly ideal.

What OS is your samba running on ?
--
Alastair Broom               Valley Technology, Edinburgh, Bonnie Scotland
abroom@valleyt.co.uk