similar to: Samba client file locking

I have the same problem as described below for a while. samba 3.0.23c-2 under Fedora 6 clients Win XP and Fedora 6 app. OpenOffice 2.1 / 2.0.4 will there be any progress ? thanx -- Kristian Lauritsen Laser Product Manager PicoQuant GmbH phone: +49 30 6392 6563 http://www.picoquant.com On Mon, Oct 31, 2005 at 09:41:04AM +0000, Phill Gillespie wrote: > Hi... > > I've been

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

I first asked this question at the end of October, got a response which didn't solve the problem, and have finally got back to the issue now. I'm running 2.2.7a, recently upgraded from 2.2.0 as Domain Logons for Win2K were suspected to be part of my problem. Anyway, the issue relates to AutoCAD (actually a vertical product called Land3) and a command which works with winXX boxes, but

I help an NT admin that has recently added a redhat 8.0 based samba server to his network. the share is one that is a core service for the operation of the business and has about 50 users constantly accessing data from several accounting and tax preparation applications. One of the primary applications requires update farily recently as of late and the admin is having problems getting all files

Hi I look at list archives and at samba docs but I did not found ... please can some one help me? I have to write a unix program that need to check if it can write to a file and place the apropriate locks before write. Those files are in a Samba share. I intend to use fcntl() function to check and set the locks. I wrote a test program to see if the fcntl() function can see the samba locks

All, I'm running the latest stable version of SerNet-Samba on a Debian Sarge box (I switched from the traditional Samba package for certain reasons which I won't delve into here), but I've come across a serious issue. Every day, the Samba processes become so numerous that the server begins acting really flaky. That is to say, there are so many smbd -D processes that the server

I am running samba 4.5.1 on Ubuntu 16.04. The samba server is running as an AD DC and stores the user profiles, the clients are all windows 10 professional. One user reported being locked out of the profile pretty regularly. After investigating the case I saw that a lot of files in the profile are still locked even after logging out and shutting down the system. After restarting the samba server,

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

Hi list, recently upgraded from 3.0.10 to 3.0.21a on debian sarge. Congratulations guy 's many problems gone but .......... a) a couple of users reported the following: If they open outlook for the first time they are not able to send/receive emails. If they close/open oulook the second time everything is fine. I 'd set a high debug level and observed the log but nothing that will

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

I'm concerned about the machine known as accountingii in the below smbstatus: Samba version 3.0.5pre2-SVN-build-1326 PID Username Group Machine ------------------------------------------------------------------- 2727 bbeerman users bbeerman1 (10.2.240.172) 30957 llawrence users df2x1121 (10.2.240.190) 28942

Hi, I have one NAS which I can access via NFS or Samba. This storage is accessed by 2 linux servers with Samba where I re-export the NAS share. This is sort of an active/active loadbalancing cluster. The only thing not working is locking... If a client opens a Word-File via server1 and another opens the same via server2 it won't inform the user that he can only open the file readonly. I was

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

Hello, We've been seeing a problem with Samba server 3.0.33-0.17 handling lock files for Microsoft Powerpoint 2007. The problem is observed in both Windows XP and Windows Vista. If a user opens an existing file, smbstatus looks like this: 10781 11021 DENY_WRITE 0x2019f RDWR NONE /usr/test/dssg test1234ecg2.pptx Fri Oct 23 17:21:52 2009 10517 11021

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 would like to know, what the oplock 'EXCLUSIVE+BATCH' exactly means. Does anybody know a good manual about samba's oplocks? Could it possibly cause oplock-trouble and even disconnections, if a user is constantly logged in on one AD-workstations and also frequently accesses network files from a WinXP+SP2 workstation (that is not part of the AD-Domain) via

Hi, I updated from Samba 2.2.5 to 2.2.8a. und Redhat 6.2 and since then, smbstatus shows strange values The dates and the pid's are wrong. Any ideas? Was there a change in a locking.tdb? Do I have to remove it? Greetings Hansj?rg 28643 DENY_NONE 0x3f407996 RDONLY LEVEL_II ?7??W? Tue Jan 6 22:38:12 1970 1633824626 0x706d622e NONE ?7??W? Thu Jan 1 02:00:00 1970 1836017711 0x56414143

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

Hello I use a new samba server with LDAP support as PDC for some Windows2000 and WindowsXP machines. All is working nice. The useer can login with a user/password in the domain, we have remote profiles, the user can access the samba shares and print etc. But after some time (< 1 day) we get a smbstatus output like the attached file. Users are connected multiple times with the same share

Hello. I have a DOS application which works with database files. The problem is, that Samba doesn't "unlock" the files when DOS app finishes its work. So files stay locked: 27690 DENY_NONE 0x3 RDWR EXCLUSIVE+BATCH /home/samba/FAK/P_RACI03.DBT Fri May 9 13:27:09 2003 27741 DENY_NONE 0x3 RDWR NONE /home/samba/FAK/MATPOD03.DBF Fri May