Hello all, 
I have the following problem both at my home network and at work. Once many
cleints access a share, and traffic grows up
extensively connections start to terminate themselves unexpectedly. It may be an
open file or a locked share - either way it
reflects a mesaage similar to 
  oplock_break: receive_smb error (Success)
  oplock_break failed for file John's Publications/Show Price List
05-16-03.xls (dev = 900, inode = 8077379, file_id = 940).
[2003/06/16 15:05:07, 0] smbd/oplock.c:oplock_break(843)
  oplock_break: client failure in break - shutting down this smbd.
 and then simply terminates the connection. 
This wouldn't be such a pain if it wasn't for the accounting software
Peachtree Accounting. While it's running it needs to
maintain a constant open connection to the data files. Once it senses something
went wrong (a killed smbd) it crashes as
well and you are forced to reboot the workstation with following data loss. I
tried to play with the socket_options with no
luck. Also this behaviour is extremely rare with 9x clients but happens almost
once a week with nt/2k/xp clients. Included
are parts of my smb.confs as well as verinfo. Thank you in advance for your
help.
Version 2.2.3a-6 for Debian
-----------------------------------
[global]
    interfaces = eth1
    bind interfaces only = yes
    invalid users = root
    log file = /var/log/samba/log.%m
    syslog = 0
    security = share
    encrypt passwords = yes
    socket options = IPTOS_LOWDELAY TCP_NODELAY
    local master = yes
    preferred master = yes
    os level = 64
-------------------------------------
Version 3.0.0beta1-1 for Debian
---------------------------------------
[global]
    interfaces = eth2
    bind interfaces only = yes
    invalid users = root
    log file = /var/log/samba/log.%m
    syslog = 0
    security = user
    encrypt passwords = yes
    socket options = TCP_NODELAY
    domain master = yes
    local master = yes
    preferred master = yes
    os level = 65
---------------------------------