similar to: locked file that shouldn't be

Running 3.0.4 on FreeBSD 5.2.1. Today there is a regular text file that appears to be locked. It is an ini file for an application. The file can be opened with notepad but if you try to save it an error message pops up... "The process cannot access the file because another process has locked a portion of the file." smbstatus does not show this file as being open and it is mode 777.

Hi, I hope some of you have been in a similar situation and can shed some light on this: I have a VPN connection to a Samba 4.1.4 server and when I use Word 2010 on a W7 client to open an existing file I often get the following error: "document.docx has been locked for editing by another user." I should clarify that the document is not in use by anyone (confirmed by smbstatus), and

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,

Hi, would be great if someone could help me out with this. Strange, it happens from time to time, that some files- in this case *xls- are locked read-only, although they shouldn't be locked and are not currently being accessed by any other user. smbstatus also doesn't list the file at all.. Restarting the smb processes resolves this issue. This happens once in a week or two. Samba

Hi, We've been experiencing this same problem, however, with Samba 3.0.7-1.3E.1 running on RedHat ES 3.0. We've also experienced this on 2.2.7x on RedHat 9. The problem has been intermittently happening over the last several weeks, (I've posted list about it). This message, along with the others in the thread, describes the symptoms that we're seeing, however, I haven't

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi folks, I also have the problem that the notepad pops up (with desktop.ini opened), everytime I logon. I know the workaround that was mentioned a thousand times before: hide files = /desktop.ini/ntuser.ini/NTUSER.*/ I put the file to the [profile]-share, to the [global]-share, but it won't work! An extract of my smb.conf: [profiles]

Hi, How should you deal, as an administrator/root, with locked files that stay open after a PC crash and the user can't access them any more. For example: The PC crashes and the user restart. MS-Outlook complains that it can't open its outlook.pst file, that is on a samba share, with the proper read/write access and the user can't get any mail. As root you do a smbstatus -u and you

Hi, After trying too long I fixed the problem below by reverting to the old 3c905 NIC. Problem solved but not understood. I had a similar 3c2000 NIC in another Samba server and it also failed to copy a large amount (5000+) of files. So that's two completely servers (hardware and Samba / Slackware version) having the same problem with any number of different clients. I couldn't imagine

Whenever a person logs into a computer they've never logged into before, even if they already have a roaming profile, on the new computer, Windows XP is putting a desktop.ini in the startup folder, so when the person's desktop loads, notepad pops up with desktop.ini displayed. is there a way to prevent XP from creating the desktop.ini in the startup folder?

Hi, When trying to copy 5000+ files from a client PC to a Samba server I have the following problem. Halfway during the operation it hangs on always the same file. Windows XP (SP1) gives: Unable to copy file [filename]. Specified network name is no longer available. (I had to translate this from Dutch, so it is not the exact message). When checking with smbstatus I get this:

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

I have notepad popping up for every user with a long message that starts out: [.ShellClassInfo] LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787 I found an explanation here: http://www.hostingforum.ca/131016-samba-notepad-selfstart-login.html: > What is happening is that the desktop.ini file that is normally hidden is > having those attributes stripped off, possibly

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

hi all; I'm starting in PDC and need some help, i'm using samba for pdc but without ldap, and all time that a user make login, open a notepad with the content: [.ShellClassInfo] LocalizedResourceName=@%SystemRoot%\system32\shell32.dll,-21787 or [DeleteOnCopy] Owner=cesar Personalized=5 PersonalizedName=My documents and all folder have a document Desktop.ini... someone can say me why

Hi, I just installed Samba 3.0.4 on a Solaris 2.6 server. I had no problem compiling, intalling and configuring it, and everything seems to go OK. People can connect to all the configured shares without any problem. But I have some problems when getting server status either via SWAT/STATUS or using smbstatus: First, in the "Client" field of the SWAT/STATUS report I have problems

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 have a very small problem. Thanks for any suggestions. Say user1 logs onto a Windows XP workstation and opens file1. Then, if user2 attempts to open the file from another workstation the following message is displayed: "file1 is locked for editing by ''" Problem: *user1* is not displayed between the single quotes. However, say user1 logs onto a Win98 workstation and

On Thu, Dec 18, 2014 at 3:51 PM, Cj Tibbetts < cjtibbetts at heritageacademyaz.com> wrote: > > Thank you Ricky for responding. I am still new to linux and samba so I am > struggling with where to start. I will answer your questions the best that > I can. For memory use I see only a small increase over time. I used vmstat > after reboot and after 30 min. I am using samba 4.1.9

I am having a strange issue at one location which is running samba 4.1. Two or three PC's out of maybe twenty-five are unable to get to the sysvol share. If I run "gpupdate" on the systems it gives error 1058. Digging deeper says the path was not found, but if I click on the path in the event log it pops right up in notepad (gpt.ini). This tells me that the user accounts can access