Oplock not working with Win98 client?

Jeremy Allison jallison at cthulhu.engr.sgi.com
Sat Oct 9 21:52:35 GMT 1999

Mike Thompson wrote:
> Hello,
> I hope this is the right place to ask this question.
> I have a Win98 client accessing a Samba version 2.0.5a mount
> on a FreeBSD 2.2.8 system.  When a Windows application attempts
> to write a file to the samba mount the application freezes for
> about 30 seconds and then finally the write takes place.  Looking
> in the log.smb file I find the following tell tail debug messages:
> [1999/10/07 12:03:31, 0] smbd/oplock.c:oplock_break(905)
>    oplock_break resend
> [1999/10/07 12:03:41, 0] smbd/oplock.c:oplock_break(905)
>    oplock_break resend
> [1999/10/07 12:03:51, 0] smbd/oplock.c:oplock_break(905)
>    oplock_break resend
> [1999/10/07 12:04:01, 0] smbd/oplock.c:oplock_break(922)
>    oplock_break: receive_smb timed out after 30 seconds.
> This gave me enough of a hint to add the following to my
> smb.conf file to avoid this problem:
> oplocks = no
> Is there a known issue with oplocks not working with Win98
> clients or FreeBSD 2.2.x servers?  I would like to work
> with oplocks enabled to get the higher performance offered
> by this feature.

We're doing a lot of work in this area in Samba 2.0.6 to
get Samba to do exactly what NT does in these circumstances.

If you'd like to test the pre-release code we have to see
if it fixes your problems (*WARNING* ! It's *pre* release
code :-) then email me and I'll send you a snapshot.


	Jeremy Allison,
	Samba Team.

Buying an operating system without source is like buying
a self-assembly Space Shuttle with no instructions.

More information about the samba-ntdom mailing list