similar to: oplock_break problem (PR#20285)

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

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,

Hi all. I know this has probably been asked before, but I need a quick answer, and didn't find anything on the net. Has anyone done any benchmark comparisons of server speed from Win95 clients, accessing files on a Samba 1.9.17p1 server share, as compared to an NT Server, running on the same server hardware? If so, how did Samba 1.9.17 measure up to the NT server? I need an answer to this,

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,

Hi! I've been struggling with this install of Samba 2.0.4b on Linux/x86 2.0.36. All of the client machines run Windows NT 4, SP 3. I'm exporting /tmp as pub, and if I right click in the folder and create a new folder, it doesn't show up until I go to 'view' and 'refresh'. If I delete something, it doesn't go away until I refresh. Why? Output of testparm:

I've been seeing these in my logs files ever since I upgraded to 1.9.18p10 and turned on oplock support for users' home directories: --snip -- 1998/10/07 10:05:44 oplock_break: receive_smb timed out after 30 seconds. 1998/10/07 10:05:44 oplock_break failed for file Start Menu/Open Office Document.lnk (fnum = 14, dev = 808446, inode = 45cb8). 1998/10/07 10:05:44 oplock_break: client

Dear Samba users, I've had a problem recently with Samba (2.2.3a, and now 2.2.5) on my OpenBSD 3.1-stable Installation. Bsd: OpenBSD 3.1-stable (CYNOSURE) #1: Fri Oct 4 01:06:45 EST 2002 avant@XXXX:/usr/src/sys/arch/i386/compile/CYNOSURE I get problems such as these: <poor formatting> [2002/10/13 23:00:04, 0]

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)

Phillip.Link@alcatel.fr wrote: > The problem > ----------- > I've been trying to install the latest samba distrib (2.0.5a) on a hpux > 10.20 machine, but the connection times out, apparently because of > shared memory access. > > Trying to make an smbclient connection (or using the windows nt explorer > to connect generates the following log.smb (smbd launched as smbd

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

Hi, Anyone know where I can get a .tar.gz of 2.0.2? I'd like this version, since the PDC code is reportedly more stable than 2.0.3. Or has this been fixed in 2.0.3? Thanks, -- Seeya, Paul ---- plussier@baynetworks.com Broadband Technology Division - Bay Networks (now a Nortel Company, Eh? :) If you're not having fun, you're not doing it right!

We recently tried the upgrade to 2.0 Beta series (just finished testing Beta 4) on our network. Everything works fine with 1.9.18pl10, but once we start 2.0 in its place we start getting the following in the log files: [1998/12/17 05:00:12, 1] smbd/files.c:file_init(219) file_init: Information only: requested 10000 open files, 246 are available. [1998/12/17 05:07:52, 1]

-----Oprindelig meddelelse----- Fra: Simo Sorce [mailto:idra@samba.org] Sendt: 8. januar 2003 15:40 Til: Preben S?rensen Cc: Andrew Tridgell; Jeremy Allison; samba-bugs@samba.org Emne: Re: oplock_break (PR#26342) Please send help request to the users mailinglist samba@samba.org Simo. On Wed, 2003-01-08 at 15:38, ps@datamann.dk wrote: > Full_Name: Preben S?rensen > Samba_Version: 2.2.5

I got mcp mag a day or two ago, Great writeup!! I was a little surprised that they ran such a glowing review of samba, with some of the negative implications on NT. It is very nice to see Microsoft show an interest in interoperability. -Steve Roylance > -----Original Message----- > From: Jeremy Allison [SMTP:jallison@cthulhu.engr.sgi.com] > Sent: Thursday, April 15, 1999 6:41 PM >

TO THE SAMBA TEAM: MAY YOUR TRIBE BE HERE FOREVER! YOU' SIMPLY GREAT BUT i CAN'T AFFORD TO BUY YOU A PIZZA BUT OUR NATIVE PIE "BUKO (YOUNG COCONUT) PIE" IS BETTER! i HAVE BEEN USING SAMBA 1.9.16P9 AND STILL ALRIGHT. PERHAPS I'LL DO CHANGE TO SAMBA 2.0 AND THIS IS A LONG WAY! i DID TRIED SAMBA SINCE MY OFFICE CAN'T AFFORD TO BUY NFS TO SERVE AT LEAST 20 PCs AND

Hi everyone, Just today one of our users informed me that a file she was working on in Microsoft Excel 97 got corrupted. She was working on the file directly on our server, which is running Samba 2.2.3a compiled using gcc-3.0.4 on Linux kernel 2.4.17-xfs and XFS-based filesystems. I checked the Samba logs for her machine and found the following in a search for the filename of the Excel file she

Many 2.0.x users have the: [1999/06/23 10:47:48, 0] smbd/oplock.c:oplock_break(773) oplock_break resend [1999/06/23 10:47:58, 0] smbd/oplock.c:oplock_break(773) oplock_break resend [1999/06/23 10:48:08, 0] smbd/oplock.c:oplock_break(773) oplock_break resend [1999/06/23 10:48:18, 0] smbd/oplock.c:oplock_break(790) oplock_break: receive_smb timed out after 30 seconds. problem. I get this

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

Hi there everyone! I'm using Samba 2.0.5a-19990721 on a RedHat 6.0 machine with Linux kernel 2.2.12. My system generally works fine, however recently I've had some complaints about some files being corrupted. The latest and best-handled to enable a debugging happened at around the same time. Both clients were using Windows95 OSR2 machines with Excel 97 SP-2. Two users reported the problem

Hi, I am running Samba 2.0.3 on Linux Kernel 2.2.5 (SuSE 6.1) in a test environment with a Win NT server (PDC), the Linux box taking over step by step the file- and printserver tasks, and Win 95 clients. Samba is setup with security=domain at this stage. It just happened again what I have seen only a few times before. When I use Outlook 98 on the Win95 machine and want to access the