similar to: oplock problem on NTUSER.DAT

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

Hello, on my Samba 3.0.14a PDC (Debian Woody) I created a local unix group named "gpusers". Then I mapped it to a new NT domain group named "GPPower": # net groupmap add rid=1005 ntgroup="GPPower" unixgroup=gpusers Then added a user "mdv", who already had its own initial group "mdv", to the new gpusers group: # usermod -g mdv -G gpusers mdv

Hi, I posted this some time ago but it remained unanswered; sorry for the repost, but I hope to receive at least some confirmations or otherwise by other people using WinXP Pro. Using Samba 2.2.8a, I have a problem on a WinXP Pro client regarding the read-only attribute on folders; the problem does not appear on Win2000 Pro clients. Here it is: setting and unsetting the read-only attribute on

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)

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

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

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

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

Hi ! I'm having some problems, where the user lose connection with Samba and the Windows98 Workstation crash. Looking at logs I found the follow messages: ---- [2004/10/15 11:36:49, 0] smbd/oplock.c:oplock_break(807) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file Notes.ini (dev = 904, inode = 18530507, file_id = 1). [2004/10/15 11:36:49, 0]

I keep getting the following in the log files now that we've upgraded to the latest cvs 2.0 branch. Any ideas what we can do to fix this? Thanks! Bruce Mar 23 08:45:34 gate smbd[22692]: [1999/03/23 08:45:34, 0] smbd/oplock.c:oplock_break(773) Mar 23 08:45:34 gate smbd[22692]: oplock_break: end of file from client Mar 23 08:45:34 gate smbd[22692]: oplock_break failed for file COMM.INF

Well I'm having some trouble with samba, I had those troubles on a box for quite some time and not long ago I moved all the stuff to a new box to see if it'll work better but it doesn't. I'm monitoring one person in particular because she's the one who do most of the editing stuff in there. What happens is when she opens a document (.doc or .xls most of the time), when she

Hi , Before I copy and paste the oplock message(s), here is the setup I have. I have samba server (on Solaris 2.8) which shares out the NFS mounted directories to the windows world. All was working fine till today morning when users complained of extreme slow performance , looks like there is problems with oplocks accessing some files. Below is the snippet to the error log. [2003/03/24

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

btenison@dibbs.net wrote: > > I keep getting the following in the log files now that we've upgraded to > the latest cvs 2.0 branch. Any ideas what we can do to fix this? > > Mar 23 08:45:34 gate smbd[22692]: [1999/03/23 08:45:34, 0] > smbd/oplock.c:oplock_break(773) > Mar 23 08:45:34 gate smbd[22692]: oplock_break: end of file from client > Mar 23 08:45:34 gate

We see the following errors that cause the NT 4.0 workstation Word file saves to fail. I have been tweeking the oplock parameters for awhile now. Can't seem to get the right mix. Does anyone see this same problem with older versions or the v2.0.7 version. [2001/03/13 10:43:26, 0] smbd/oplock.c:(973) oplock_break: receive_smb timed out after 30 seconds. oplock_break failed for file

Hi all, I want to migrate from 2.2.6 to 3.0.10 (with ldap). Is it possible to change the SID in the ntuser.dat on the server-saved profile? -Peter

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