similar to: Problem with Office (and Windows 2000) and oplocks (and even without)

hello, until last week I had 2.2.1a in place, which, except some fox (dos) share which needed 'veto oplocks files', worked ok; upgraded to 2.2.3a with the same smb.conf (details below) and suddenly I started having oplocks problems (not on the dos share, that one is ok) with almost every other share (those hold windows files: programs, *doc, *xls): [2002/02/19 12:31:28, 0]

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

Can any one help me ? This has been bugging me for ages. I have been using different versions of samba for a while on different versions of Redhat (7.0, 7.2, 7.3). I regularly get erratic freezing (for about a minute) whenever I right click on files. This has happened on different computers on different sites on different networks, so I assume it's quite consistent This is what I get when

Hi all, I use samba 2.2.2 on AIX 4.3.2 (1500 NT4 sp6a / w2k sp2 workstation). since i had updated from 2.0.7 to 2.2.2 the CPU load will very fast go to 100% an d teh memory use of a smbd process will grow up to 100 MB. In teh log-files are many errors like that: PANIC: open_mode_check: Existant process 22700 left active oplock smbd/open.c:open_mode_check(555) open_mode_check: exlusive oplock

Hello there. I'm having a few problems using samba 2.2.3a and sharing a paradox database. On the whole everything works fine but (there's always a but), every now and again. a machine's shares will close causing the database to crash (sometimes only that machine) - the other networked machine recover after a few error messages. I guess the easy answer would be to disable oplocks

In my smb.conf file, I've got the following section: [homes] comment = Home Directories valid users = %S guest ok = no read only = No create mask = 0640 directory mask = 0750 browseable = No veto oplock files = /*.mdb/*.MDB/*.pst/*.PST/ And yet, in the syslog, I'm still getting these... Mar 10 10:22:34 riffraff

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

---------- Forwarded message ---------- Date: Tue, 29 Jul 2003 19:40:48 -0400 (EDT) From: Rashkae <rashkae@tigershaunt.com> To: Marco De Vitis <starless@despammed.com> Subject: Re: [Samba] oplock problem on NTUSER.DAT Hi Marco Try to veto oplocks for that file. In the global section of your smb.conf, add the following veto oplock files = /NTUSER.DAT/ Let us know if that changes

TEST: ===== SAMBA STRESS OVER GIGABIT NETWORK: This is a simple Read/Write/Compare/Delete kind of test over the network via Samba. Multiple clients with multiple threads try to read/write/compare/delete(in a loop) a finite sized file (64K block size) over samba for a prolonged period of time in an effort to stress test the server. SERVER SIDE CONFIG: =================== ARCH: x86 OS: RHL AS

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 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)

Hi! Been having the same problem with oplocks for a while and have been trying to figure out what's going wrong. The FAQ says that we may have a networking (hardware?) problem, but according to the Linux box's ifconfig results, we have had no errors and no dropped packets on the internal network. I am able to reproduce the error pretty much at will on our network, and it is not isolated

Hello list! I've seen the threads in this months archives on oplock issues, so I hope I am not hitting a sore spot by bringing it up again. The reason I am beating on this is that I've got a testable, repeatable issue with Win2K terminal server (SP2) running CorelDRAW 10 (patched to current) against a Debian Woody box running Samba 2.2.3a-6 for Debian. Since I can repeatedly test 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

Hello, I'm having problems with samba share and trying to make multiple connections from one PC. Here are the errors I'm seeing in the log file: [2006/12/19 09:02:48, 1] smbd/service.c:make_connection_snum(648) amcfp001 (10.210.4.65) connect to service bvvol02_U1 initially as user bvvol02 (uid=502, gid=502) (pid 17671) [2006/12/19 09:02:48, 1]

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,

Hello, all. I'm using Samba 2.2.2 at my FreeBSD 4.4-STABLE server, and have next problems: There is pool of W2K machines, each starting compilation job (usually 2 at one dual CPU machine). Then these jobs trying to simultaneously access sources, located at Samba server, appear problems. Then I running 2 compilation threads from single machine - there is no problems. For jobs error seems

hello i have "oplock_break failed " in logs, see below. should i consider removing oplocks ? regards --------------- [2004/09/09 11:08:53, 1] smbd/service.c:make_connection_snum(705) ul_55 (129.199.59.202) connect to service users initially as user DOM_BIBLIO+Daniele (uid=10029, gid=10000) (pid 19058) [2004/09/09 11:09:23, 0] smbd/oplock.c:oplock_break(807) oplock_break: receive_smb

Hello, i am running Samba 2.2.3a on a Red Hat Linux 7.3 box with kernel 2.4.18-10. I am experiencing some problems on a particular samba share, which is accessed by 10 Windows 98SE clients working on a COBOL production packet by mapping with a G: letters this samba folder. Well, some times a day it happens that this packed blocks because some files on that samba folder remains locked; i