similar to: SAMBA digest 1937

Sorry for all my emails. I don't know where to post this problem, so I also post it to the ntdom mailing list... Since I upgrade to 2.0beta5, I got a lot of messages like this in log.smb: [1999/01/08 16:30:38, 0] smbd/oplock.c:(734) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file GN/previsions/previsions 99/previsions globales 99.xls (dev = 800073,

Howdy all: For those who are curious (eg, Peter de Groot <pdgtech@wantree.com.au>) here are the (I think) relevant posts from recent samba digests concerning win98 and or NT performance problems copying files between local drives and samba shares. It looks like there should be some new options to play with in the next samba release. Could Jeremy or Andrew confirm? (BTW, nice

hello list, testing the 2.18 release i got following core dump. Maybe Timo you can get a look at it. greetings dominik Core Dump: root at hbs-buko:/var/vmail/hbs-buko.info/dominik.breu# gdb /usr/lib/dovecot/imap core GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1 Copyright (C) 2014 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is

I have installed a small Limux box in my local primary school, in order to sahre CD iso images. The system works fine, untill several w/s's concurrently access the same program , whereupon, we get spurious crashes. I have tried disableing op-locks, which seemed to help, but only slightly. Any suggestions gratefully received. Shane oplock_break: no break received from client within 30

Hi all, I have a problem opening file on a samba share with Word 6.0. We use samba 2.0.5a running on a HP9000/800 (HP-UX 10.20). Often when try to open file, Word stop responding for some minutes (generally from 2 to 5) and then word succed to open it. In the sambadir/var the corresponding log file is like this : [1999/09/20 17:10:52, 1] smbd/service.c:make_connection(521) pc000320

I would really appreciate some help figuring out why one of my students has "disappeared" from the user list, and what to do about it. I'm using Samba3 on Fedora; the client machines are running WinXP. The system has been up and running since the beginning of September. Today one of my 4th-graders was unable to log on; she didn't read the error message carefully, so she

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 >

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

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

Unknown recipient ----- Original Message ----- From: <samba@samba.org> To: Multiple recipients of list SAMBA <samba@samba.org> Sent: Thursday, July 08, 1999 1:02 AM Subject: SAMBA digest 2158 > SAMBA Digest 2158 > > For information on unsubscribing see http://samba.org/listproc/ > Topics covered in this issue include: > > 1) msaccess and samba prob solved -

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)

2.0.4b, RH60 (2.2.6+raid1, non root-raid), accessed from win98/ie5. Intermittently ie5 takes very long to load an html page from samba; at the same time it loads another html page ok from another linux/samba1.9.x At 10:47:34 I click on the html page and it is loaded at 10:48:18. [1999/06/23 10:47:34, 1] smbd/service.c:make_connection(488) go (10.0.0.115) connect to service go as user go

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! Even with 2.0.4, I'm still seeing a lot of oplock break failures (clients failing, see log further down). The client hangs for approx 30 secs (sometimes more) and then gets back online. At least one user can't use the file shares at all; it hangs whatever he does, and on any computer he uses (NT or 98, laptop, desktop...) Other users have less problems, but maybe they are less

I'm using samba 2.1 pre-alpha. When I right click an .exe file on the most shares, explorer freezes, and must be killed to recover. The problem doesn't show up on the home shares, but appears on any other shares I create. I've experienced this problem on many different workstations. Looking at the logs, it seems to be a problem with oplocks; the part of the log that seems to apply is

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

Dear Samba team. I have hybrid network with MSDOS / Win9x(ME) / Win2k/XP(NT) computers at home. I'm using Samba as PDC. W9x/me clients works fine as so as with roving profiles, but I'm experiencing problems with w2k, NT4/XP just not test because i'm testing on my box at home and when it'll work fine then I'll go to clients from which smaller part has XPs installed on PC.

Below are a number of errors that appeared in a log file today. I am running Samba v2.2.5 on a Red Hat Linux v7.3 system. The client experiencing/causing the errors below is a WinXP(SP1) machine. The log entries below pertain to 2 errors, the first in handling file "6.zip" and the second in attempting to run file "DiskeeperWks413zssi.exe". I didn't see the first

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,