similar to: closed connection to service xxx

Hello, Sorry to bother all with this simple(?) configuration question, Little background: I recently migrated our samba server from Ubuntu 9.04 to Ubuntu 14.04.1.LTS. Migration was done like this: moving conf-files from the old server to the new one. My samba server is member of a windows domain, that is controlled by a Domain Controller running Windows Server 2008. We have three types of

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

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

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

Hello, we frequently face locking issues with office applications and documents on samba shares. The office applications claim that the document is locked and hence no write access is possible. I can check on the samba server that there is no concurrent access/locking from other computers or users. It looks like the same user holds some lock and is denied to access the document because it?s

Hello, I am trying to work out the file locking mechanism on our Samba server when connecting from Linux clients. I am getting some strange behaviour in a mixed Linux/Windows environment when multiple clients open/lock the same file for writing. Everything seems fine when a Windows client creates the lock, but if a Linux client creates the lock, we get either two or more Linux clients being able

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

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

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

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

We have a server which runs Samba and Apache. Web developers edit their files (via Windows mapped drives) from Windows XP SP2. These files are typically CGI files and the developers' routine is: while (web page not quite right) { 1. Edit file 2. Save 3. Click Reload on web browser 4. Check results } They go around that loop many times during a typical development run.

We have a lot of [2006/01/04 18:44:40, 0] smbd/open.c:open_file_ntcreate(1355) Trying to delay for oplocks twice in the logs. Do they harm in general? And only in one single case I got this, don't know if I ever will get it reproduced, so maybe not related and happened by accident: Samba version 3.0.21a PID Username Group Machine

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

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

Hi list We recently upgraded our fileservers from Centos supplied 4.2.10 to Sernet 4.4.6, and then our DCs from 3.6.x to 4.4.6. It seems that since then we've had problems with locks not being obeyed on all nodes - they only seem to work when a second client opens a file on the same node as the first client. For example, when a user opens an Excel file I will see something like this

Hi, We are running Samba 2.2.5 on RedHat 7.3 rebuild with ldap support. We run Win2k Terminal Server, which provides most of the clients for the samba server. After a fairly long samba server up time (usually a couple of days, but this happened overnight), we end up with some odd entries in the smbstatus output in the "Locked files:" area.... Here is one line of the type I mean:

Hi, I'm running smbd 2.2.8. I'm a little green when it comes to file locking with samba. I have two users that access a single data file on a FreeBSD box. It's a moneydance data file and obviously it gets messed-up if two users are writing to it at the same time. Is there a way with samba to stop a second instance of the file from being opened, something like a "File In

On Fri, Oct 21, 2016 at 05:48:52PM +0100, Alex Crow via samba wrote: > > > 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