similar to: 2 Samba problems (oplock & hosts allow)

Robert Dal Santo wrote: > Is there any work underway to get Samba to support OPLOCKS? I know > they are difficult to implement but I'm faced with a decisions now to buy an > NT box (Ugh!) or do a lot of messing around to get this application > to perform decently. The application in questions takes around 5 > hours to do a taks without OPLOCKS and around an hour to do the

Hi All, I'm experiencing some really funky Samba errors, and I'm hoping that some of you might have some ideas. This only happens sporadically, and when it does, I loose Samba connectivity for a while. Here are my Samba logs: Jun 2 13:29:01 nasone smbd[20289]: [2004/06/02 13:29:01, 0] smbd/nttrans.c:call_nt_transact_ioctl(2076) Jun 2 13:29:01 nasone smbd[20289]:

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)

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

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

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

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

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

We are running samba 2.2.3a ( for about 3000 users ) on HP/UX 11.11 fileservers. Our customers are complaining about slow response on the opening/closing of files in office/excel etc. In the samba log file we see the following messages : [2002/10/29 09:03:27, 0] ../source/smbd/oplock.c:(761) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file My

Guys, I think the answer to my question is to upgrade samba. However, since this is my production machine, I thought I would try and understand the problems I'm having a little better to insure that an upgrade will correct my issues. My setup - Mandrake 7.2, samba 2.09. Win98, ME and XP clients. The 98 and ME machines have no problems. The XP machine has some intermittent slowness

Hi all, I have the following problem. A Linux (2.2.19) machine is running Samba 2.2.2 as a PDC. The clients are Win2K SP2. A user accesses several Excel 2000 files on a share. This sometimes results in long(ish) delays (the user reports around 10 seconds, although this could be longer) and the message from Excel that the file is in use and can only be read. After closing and re-opening the file,

We're using CentOS samba for about 20 workstations, mostly XP, some 2000 and two win98. Samba shares a data directory with Word, Excel and Access documents/db's. Also Exact for Dos is running from this share (executable and data). The users experience a long delay every morning opening the first Word document (Word 97, Word 2000). This could take 10 minutes or so. If they close

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

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]

> I have samba v 2.2 on one of my production server, the client connections > seem to drop sometimes, these clients run overnight jobs and when this > happens there job crashes and they have to manually start it. > > Below is the snippet of the log for one of such clients with problems. > > ###########cut-paste of log (only part of it)######### > > oplock_break:

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, I am running Samba 2.2.2 with acl-0.7.16 on RedHat 6.2 (2.2.19). The PDC is a Windows 2000 Server and the Samba server is a domain member using Winbind. All the workstations are Windoze 2000 Pro with SP2. Everything seemingly works fine but every day or two I get a runaway SMBD process which hogs the CPU and becomes unkillable. The only resolution is to reboot the server completely.

For some strange reason, a samba setup which was previously working has suddenly stopped working, and I can't figure out why. The symptoms is that attempts to write some files onto a samba filesystem take a long time, and then error out with the error message (in Windows dialog box): "Cannot create or replace <filename>: The specified network resource or device is no longer