similar to: Good old file locking

This problem was somewhat irregular in the past, but is becoming a major nuisance now... On connecting a drive, users (all W95) have their NT domain accounts locked out. In the logs, I see things like: [2000/02/09 07:24:49, 1] smbd/password.c:(1131) password server <PDC> rejected the password [2000/02/09 07:24:49, 0] passdb/smbpass.c:(50) startsmbfilepwent: unable to open file

Does anyone know if it is possible to use the "printer" with WordPerfect 9-Linux and WINE? I think that I have set up the configuration files correctly, but I don't see the fonts in the application (I don't know if they would print since I cannot select them). Note: my "printer" is GhostScript but WINEPS shouldn't know the difference, and I am using the

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

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

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

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

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

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

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

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,

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

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