samba - Sep 1999 - smbd timed out kills WinNT application

Hi,

Probably this problem is known and has already been discussed
in this group, but I did not find any hints in the archive nor
in the package description.
 
On a PII/400/256MB RAM I am running SuSE 5.3 with smbd 2.0.2.
Unfortunately, sometimes the WinNT client seems to loose its
connection which crashes a WinNT application (SolidWorks) if
the latter wants to save a project. (This happened 8 times
in 6 month). At this time, the log.smb says:
[1999/09/03 07:47:28, 0] smbd/oplock.c:oplock_break(742)
  oplock_break: receive_smb timed out after 30 seconds.
  oplock_break failed for file engrenage/eng_dev/eng_2C.SLDPRT (dev 309, inode =
40964).

Thus, I played a little with the "keep alive" option in
smb.conf, but nothing changes. Which value has to be set
in order to avoid this type of error? Or is it just another
problem or parameter to configure?

peterw
-- 
Dr. Peter Wurmsdobler

      CTM - Centre de Transfert des Microtechniques
39, av. de l'Observatoire, BP-1445, 25007 Besancon CEDEX 3
TELEPHONE: +33 3 81 47 70 20  TELECOPIE: +33 3 81 47 70 21           
                E-mail: peterw@cetehor.com

                  Ceterum censeo MIRCOSOFTem esse delendam.

On Fri, 3 Sep 1999 18:58:07 +1000, hai scritto:
>the latter wants to save a project. (This happened 8 times
>in 6 month). At this time, the log.smb says:
>[1999/09/03 07:47:28, 0] smbd/oplock.c:oplock_break(742)
>  oplock_break: receive_smb timed out after 30 seconds.
>  oplock_break failed for file engrenage/eng_dev/eng_2C.SLDPRT (dev >309,
inode = 40964).
>From the samba faq:
==The advisory message means that you have either a defective network card
on one of your clients, or else an MS Windows application is refusing to
respond to an oplock break request from another MS Windows client that
wishes to accessan already locked file.
==So check your nic's and cabling.

If the above doesn't help, you can set "oplocks = no" (so did I)
and the
problem will disappear, though the performance may be affected
negatively.

If you can reproduce the error "whenever you want" (that is if it
_always_ happens when you do a _certain_ operation), then write about it
to samba-bugs@samba.org.

-- 
giulioo@tiscalinet.it