similar to: NAS and 2 active Samba servers / locking not working

I'm running a samba pdc on my gentoo box in a mixed environment with a couple of Windows XP clients and only a few MacOSX clients. The users told me, the file locking across the platforms does not work properly sometimes. I tried to google my problem, but without luck. I switched all the flags related the lock mechanism of samba on and off, but the problem seems to be solved yet. The only

Hello.. File server freebsd 6.2-STABLE + samba-3.0.25a + ldap + acls Problem: I've a situation where file locking does not seem to be functioning as expected, in that more than one user can open and write to a file without any notifications being displayed about the file already being opened by another user. I have two Windows XP clients accessing the same shared file, user1 has the file

> I've now managed to replicate the error on my test setup. I added a > third host and all hell broke loose - no locking at all when opening > Excel files apart from same-host. It seemed fine with two. > > I then downgraded to 4.4.5 and the problem persisted. So it cannot be > a regression from that patch. > > Regards, > > Alex > Here you go: Locked files:

hello, can anybody explain or point me to a document that explain the locked files section produced by smbstatus -L (see below). what means denymode ? access ? what means exclusive+batch in the oplock section ? can anybody point me to a document explaining the way file locking works ? regards # smbstatus -L Locked files: Pid DenyMode Access R/W Oplock Name

-------- Original Message -------- Subject: File Locking and Permissions Issue Date: Wed, 14 May 2008 15:10:28 -0700 From: Jack Lauman <jlauman@nwcascades.com> Organization: nwcascades.com To: mailto:samba@lists.samba.org I'm trying to get Lacerte 2007 Tax Accounting software working on a Samba v3.0.28a based server. When one user is logged in it works fine. When two or more users

Samba version 3.0.24-4 on a Fedora Core 5 box. I've been working solidly on this for the last 2 days but don't seem to be getting anywhere. Any and all help would be greatly appreciated. I've found that once a file has been opened, smbstatus shows the file is locked as expected (see below) Locked files: Pid Uid DenyMode Access R/W Oplock

On 21/10/16 10:52, Ralph Böhme wrote: > On Fri, Oct 21, 2016 at 10:30:46AM +0100, Alex Crow via samba wrote: >> Interestingly I have a setup here for testing for rollout of S4 AD. The file >> servers are in an AD domain and are running Sernet 4.4.5, so one version >> older than production. > maybe it's related to bug 12005 that was fixed in 4.4.6? Can you test > with

I have some identical windows 7 clients. All connected to Samba 3.5.4-1.1-2382-SUSE-SL11.0. If I'm the windows-owner of the file, swat shows me under "oplock" "exclusive+batch". Other users get: "none". What is the reason for this? ___________________________________________________________ Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt

Hi Ralph, I applied the patch to a new build of Sernet 4.4.6 SRPM. I could still open the file from both hosts, and in fact this time I could actually open it on the same host without any problems: host 1: smbclient -U ajc //172.31.0.120/ifa_v ... smb: \jmi\Corporate Accounting\ISL Ltd Accounts\2016\1609\> open "201609 213_ ISL Balance sheet variance analysis.xls" open file

After having migrated my machines and user to Samba 4.3.11 on Ubuntu 16.04.1 (no domain upgrade, new provision, all accounts new defined) and old data copied over to the new machines, I have now a broader testbed and notice issues I didn't see prior to that. Having roaming profiles (defined in the user object in LDB)... Seemingly at random smbd keeps locks on NTUSER.DAT and ntuser.ini for a

Hello, I have manually mounted the SYSVOL share, sync it with samba and run samba-tool ntacl sysvolreset. But I'm not sure if all windows policies are acceptable by samba because of errors logs: 2015/03/18 09:30:52.197934, 0] ../source3/smbd/oplock.c:338(oplock_timeout_handler) Oplock break failed for file myDomain.local/Policies/{31B2F340-016D-11D2-945F-00C04FB984F9}/USER/Registry.pol --

A user has recently moved his .pst file onto a samba shared folder for testing, but he is seeing the following error message on a samba 2.2.8a installation (linux/s390 SuSE SLES8): "Can't open this item. The file z:\Personal Folders.pst could not be accessed because another workstation has modified it. Close and then restart all mail-enabled applications." Has anyone else seen

16.03.2024 21:26, Ralph Boehme wrote: > On 3/16/24 18:18, Michael Tokarev wrote: >> Enabling strict renames does not change anything.? Yes it prevents from >> renaming a directory if a file is open inside.? But not renaming a plain >> file which is locked. > > oh, you mean just rename a plain file that is currently opened by some client? That is possible as long as all

Of course, the sysvol is located on a windows controller from the forest. mount -t cifs -o username=domain_admin_user //windowsDC.myDomain.local/SYSVOL /mnt/smb/sysvol and copied the files with -R --preserve to /usr/local/samba/var/locks/sysvol/ Below logs are provided from /usr/local/samba/var/log.smbd file. regards, On Wed, Mar 18, 2015 at 3:36 PM, Rowland Penny <rowlandpenny at

On Tue, 23 May 2017 16:34:29 +0200 Asbjorn Taugbol via samba <samba at lists.samba.org> wrote: > Yes, the users exist as both Linux and Samba users. My question was > if the Windows client user "Admin" also needs to be Linux and Samba > user. > There is no windows user called 'Admin', there is one called 'Administrator', if it is the later, then it

Hello, Our samba fileserver is a member of a Windows 2008R2 domain, and has different shares. These shares are set with a "read only = yes" and have an explicit "write list". This works as planned. But when an "read only" user opens a pdf with Adobe acrobat, the file gets DenyMode DENY_WRITE and the user who can edit the file can't save the document anymore.

Hi... I've been running samba 3.0 for quite some time now (Debian's stable version, currently 3.0.14) and I've had no problems. That's probably been because all my clients were Windows XP boxes. I've now moved several users to Linux (Ubuntu Breezy) as their desktop and I've noticed there seems to be a problem in accessing files across the platforms. If a Linux box

At an account running 3.0.14a Debian (same account as the dual log file issue posted earlier). A user sporadically cannot update an Access mdb file and gets access denied errors. The log: [2005/09/08 12:14:31, 2] smbd/open.c:open_file(245) ginny opened file database/EACM & ECC Reports Secure.ldb read=Yes write=Yes (numopen=4) [2005/09/08 12:14:36, 2] smbd/open.c:open_file(245) ginny

Sorry, I have omitted to post the config file. # cat /usr/local/samba/etc/smb.conf [global] workgroup = myDomain realm = myDomain.local netbios name = DCLINUX server role = active directory domain controller dsdb:schema update allowed = yes [netlogon] path = /usr/local/samba/var/locks/sysvol/rcs-rds.local/scripts read only = No [sysvol]

Is it possible to define a different location for the profiles and sysvol folder during the provision of samba4 ? how can I do it ?