similar to: 2.0.6 and oplock break problems.

btenison@dibbs.net wrote: > > I keep getting the following in the log files now that we've upgraded to > the latest cvs 2.0 branch. Any ideas what we can do to fix this? > > Mar 23 08:45:34 gate smbd[22692]: [1999/03/23 08:45:34, 0] > smbd/oplock.c:oplock_break(773) > Mar 23 08:45:34 gate smbd[22692]: oplock_break: end of file from client > Mar 23 08:45:34 gate

Hi! I keep getting errors like these: oplock_break failed for file Word/einaikoon/v-Locator/IBB-Beantragung/0_Antrag_AZK.doc (dev = 301, inode = 2469218, file_id = 7). [2003/07/31 15:43:22, 0] smbd/oplock.c:oplock_break(843) oplock_break: client failure in break - shutting down this smbd. [2003/07/31 15:47:12, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb error (Success)

We are running Samba 2.0.5a on an AIX 4.2.1 box, and since we upgraded from 1.9.18, a Windows 95 client reports intermittent problems (timeouts) when saving small files. The log.smb file has entries from those events: [1999/09/08 14:59:07, 0] smbd/oplock.c:oplock_break(905) oplock_break resend [1999/09/08 14:59:17, 0] smbd/oplock.c:oplock_break(905) oplock_break resend [1999/09/08 14:59:27,

I've used oplocks = no for a long time now, because of the famous "oplock_break" error, but I decided to give 2.0.7 a try. I still get "oplock break" errors as before, but this time I got a new error too: [2000/05/02 10:04:52, 0] smbd/oplock.c:oplock_break(976) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file XXXXX/xxxxxx/mailbox.pst

After upgrading from 2.0.10a to 2.2.4, I'm seeing many new messages being logged. What does this mean? Jun 5 09:42:50 files2 smbd[27585]: [2002/06/05 09:42:50, 0] smbd/oplock.c:oplock_break(788) Jun 5 09:42:50 files2 smbd[27585]: oplock_break: no break received from client within 30 seconds. Jun 5 09:42:50 files2 smbd[27585]: oplock_break failed for file

Hi, I have referred to the archive and some of you were having the oplock_break problem. Does anyone have any solution for this? Will reboot fix the problem? Please advise. regards, Bridget

When trying to delete or copy over certain files on my Samba server, Windows hangs for some time and then gives "access denied". I can delete these files directly from the server, so it's a Samba or Windows problem. There seems to be nothing special about these files, other than that Samba doesn't like touching them. Upon checking the Samba logs, I find this message or

Im running an accounting package (Sage Businessworks) and I'm running into issues with file locking with this program when I put the businessworks data files on a Samba file share. I'd like to get it off a NT file share if at all possible as Im about to decommission our NT server. Im running Samba 2.0.6 Im seeing errors from any machine accessing the Accounting data: ==> log.ryan

Hi all, I have made a RedHat 6.0 i386 binary rpm of 2.0.4b with the glibc2.1 configuration fix available at : ftp:<samba.org mirror>/pub/samba/Binary_Packages/redhat/RPMS/6.0/samba-2.0.4b-19990527.i386.rpm This rpm is to be preferred over the one on the RedHat 6.0 cd as it contains an autoconf configuration test to work around the glibc2.1 bug w.r.t. 64 bit locking (the one that

Giulio Orsero wrote: > I've used > oplocks = no > for a long time now, because of the famous "oplock_break" error, but I > decided to give 2.0.7 a try. > [ snip ..] > > - the server is linux 2.2.14/samba2.0.7; it's not the server where I > used to made oplock_break tests. It's another one on another lan. It's > used almost exclusively to store

mjt@tls.msk.ru wrote: > > I posted some messages about this, but there is still NO RESPONCE AT ALL!! > As I see, more and more users encountered this problem -- > oplocks code in 2.x (starting from all betas and now in 2.0) DOES NOT WORK!!! > > David! You can place "oplocks = no" into your [global] section and all > will be fine. But problem is opened! > There

Hi Does any one has idea if Samba supports client side oplocks. i.e if we are using "smbclient" If yes how to enable/disable it. Where can we get the details. Thanks Pankaj

Hello! I need help (but who doesn's huh? :-) ) I meant to run one program - Money2000 (no, it is _not_ program from Microsoft) together with samba on linux, but i have problems with oplocks. This program is installed locally on win9x/NT and shares its databases. We tried to place databases on novell, on NT server and on win95 acting as server and everything worked fine. But when we tried

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

Hi, We are having connection timeout issues in Excel and Word. Was this an issue that was resolved in post 3.0 versions? We are running 2.2.8a. Below is the samba log file and I have attached a netmon output. Thanks, Domenic [2005/01/24 09:13:48, 0] smbd/oplock.c:oplock_break(797) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file

We recently committed to replacing our Netware server with a Samba server running on an old SPARC box (using RedHat 6.0). This seemed like a good idea at the time, but now I'm wondering... We have two labs of PCs (each of 16 machines, all running Windows 95) and we use PC-Rdist to ensure that the hard disk images on the PCs are kept fairly clean and up-to-date. The master disk images are

Hello everybody, I have 2 questions about Samba operation: First, hostnames don't work in my "hosts allow" directive, although smb.conf(5) explicitly says "You can specify the hosts by name or IP number". If I specify a client by its name, that client is not allowed access, even though the server can do reverse DNS on the client's IP. The message I get in the

Hi, I use samba for 5 years in a small enterprise network. We have recently changed our windows client and migrate from windows 95 to windows XP :-). Samba is running on a debian woody. Since we are using windows XP home edition I can see the following log messages : [2004/04/02 15:27:50, 0] smbd/oplock.c:oplock_break(758) oplock_break: receive_smb error (Success) oplock_break failed for

I continue to have the same problems in Samba 2.0.6 with smbfs that I was seeing in 2.0.5: (1) After a mount (mount -t smbfs etc.), the volume is often not yet fully mounted. For instance, if I write a Perl script like: system('mount -t smbfs -o password=pwd //MACHINE/SHARE /mnt/machine_share'); system('find /mnt/machine_share > find.out'); the 'find' may not find

I found these articles that talk about the oplock_break problem (specifically they are related to problems with word97): http://support.microsoft.com/support/ntserver/serviceware/nts40/e9msge2bc.asp http://support.microsoft.com/support/kb/articles/q163/5/25.asp Basically they say: either apply sp3 on the winnt client or disable oplock on nt server But they don't say anything about win9x,