We recently moved our main server from an XServe running AFP to Windows 2008r2 using the SMB protocol. We are experiencing an problem with our users being unable to move and/or rename folders and files on the server when connected via SMB from a Mac. It seems to be that when a folder is open or in use by another user, the file is locked and asks for Admin credentials to move or change the folder.
Share Files From Windows to Mac OS. Select a folder on Windows and right-click on it then select Properties and On the folder Properties click on Advanced Sharing.
We haven't been able to figure out a fix for the problem. I was wondering if anyone else has stumbled across this problem or has a solution? Just did a little more digging and this seemed to do the trick - haven't tested in a big group but you guys might want to give it a try: Problem: Finder creates a.DSStore file that stores metadata for all files that are opened. What happens with the network share it that the.DSStore file is recognizing that the file is in use. Solution: Prevent Finder from creating.DSStore files on local machines.
Run this command in terminal and reboot. Defaults write com.apple.desktopservices DSDontWriteNetworkStores true I tested with one file and will keep testing but I figured I'd give you all a heads up, I mad a little progress. The problem only happens when another user has a file open in a folder.
For Example: Test folder contains a folder called Nested Test Folder and Nested Test Folder has multiple files in it. When a user opens a file (using smb on OSX) inside Nested Test Folder it locks it on the SMB server. This means if a user is trying to Create a new folder called Nested Test Folder Archive and tries to move Nested Test folder into the Nested Test Folder Archive, it asks for an admin username and password - the file doesn't unlock when the admin password is entered. If the user Force quits finder the file then becomes unlock and you can move things around, but this is definitely not a great work around for the users and we are stumped as to how to fix it. We have tried everything we can think of including using 3rd party tools like ExtremeZ-IP.
This may or not apply to you, but reading the first post, it sounded similar to something we ran into and I used the below link as a reference. OS X v10.4 and later implements SMB/CIFS-compatible access control lists (ACLs). Although individual users cannot set or alter ACLs, server administrators can do so. (Administrators can use the SMB server command line to manipulate ACLs, but only if both the client and server are bound to the same Active Directory domain.) However, enforcement of permissions is done only on the server, not on the client. I know this is ages after the problem.But I have a answer. I came across this thread when I was trying to fix my own problem. Mac OS would force admin credentials to touch anything on samba.
It also would show locked if samba was mounted anywhere else. My server uses JBOD for its drive pooling. I found that the files on the drives (not samba but the actual drive) had new file ownership. This was deceiving because Samba reported a different owner making me over look it. For some reason samba shows file ownership of the person that logged in versus who actually owns the files (admittedly this will probably vary system to system). Unmount samba shares.
Set ownership on all drives. Problem solved. Hope this helps good luck to everyone else.
I have the same issue with 10.6, 10.8, and 10.9. I have pin-pointed it to finder not closing the SMB share. I can use openfiles.exe from a windows box to verify. Run in powershell ISE as administrator to copy paste into notepad for csv viewing. Then filter on username column to find the suspect file or folder that still has a session open. Below the first query finds the open sessions and the 2nd one disconnects.
This isn't a great solution, but it stopped me from wanting to pull out my hair or throw the iMacs out the window of a very tall building! Openfiles.exe /query /s /fo csv /v openfiles.exe /disconnect /id /s Openfiles documentation. Not sure if you guys found your answer but to the OP this occurs because Apple and all their wisdom decided to have the Mac OS create preview files for all items contained within that folder.
So if a user, even in list mode, is on the server their computer can lock the files, causing the other user to lose their privileges. You can fix this by going to the root of the share on the end user station and doing an apple-J and disabling preview. Now you might still have an issue. Go back to the server and take ownership of all the files. After that reapply all the permissions. You should be good to go now.
Found this one on.smbdelete - kudos to emc community http: //www.opensource.apple.com/source/smb/smb-759.40.1/kernel/smbfs/smbfssmb.c (.) These.smbdelete files a OS X's way of deleting files that are still kept 'open' by some process. (.) Simple repro with 2 clients. Take a png or other image file and copy it to an Isilon SMB share from one Mac. Open that file from one Mac (client 1) in Preview.
Open the same file in Preview on your other Mac (client 2). isi smb openfiles list -v should show 2 IDs that have the same file open for read. From client 1 go into the Finder and delete the file. Finder will not complain and the file will be deleted.
On Isilon, you'll see that the file has been renamed to.smbdelete. On client 1 close Preview.
The.smbdelete file stays there. On client 2 close Preview. The.smbdelete file remains. And thus you now have an orphaned.smbdelete file that won't go away.
The.smbdelete file will go away if you close client 2's Preview app before client 1's, but there's no telling how often that will happen in reality. We also had the issue with a Windows 2012 R2 server. When a Mac opens up a a folder on a share on this server via SMB.
Windows server is showing that it is open, under Computer Management, Shared Folders, Open Files, even if the folder is then closed. This prevents users from moving or renaming said folder and being presented with a prompt for an administrators password. The only way to close the open files is to dismount it on the Mac. Has anyone found a solution. Seems like Apple should have thought about this since they killed off AFP. We also had the issue with a Windows 2012 R2 server.
When a Mac opens up a a folder on a share on this server via SMB. Windows server is showing that it is open, under Computer Management, Shared Folders, Open Files, even if the folder is then closed. This prevents users from moving or renaming said folder and being presented with a prompt for an administrators password. The only way to close the open files is to dismount it on the Mac. Has anyone found a solution. Seems like Apple should have thought about this since they killed off AFP. We also have this issue with our Windows 2012 R2 server used for shares.
When a Mac opens up a a folder on a share on this server via SMB. Windows server is showing that a file is open, under Computer Management, Shared Folders, Open Files, even if the folder is then closed. This prevents users from moving or renaming said folder and being presented with a prompt for an administrators password. The only way to close the open files is to dismount it on the Mac. Has anyone found a solution.
Seems like Apple should have thought about this since they killed off AFP. For what it may be worth. Just encountered this and it was rather baffling. Mac wanted admin to rename a folder. Windows said the item was in use, close it and try again. Neither of these was true of course.
Yes looking at open file handles in the MMC on the server showed they were open, but that's innocuous and irrelevant, no files were open, just folders. The REAL issue was an item down in a sub folder of that folder that couldn't be renamed, which also could not be renamed.
In that case, it was due to a corrupt character in the file name (invisible on Mac, bullet dot on Windows). Once a new folder of the same name minus the bad character was made and everything moved, the bad one could be deleted on the server.
Problem solved, all behavior normal at that point up through the parent items. Not saying this is the only cause for this type of behavior, but something to be aware of. My two cents here. I've been using Univention Corporate Server which uses Samba 4.6.x for it's shares and as an AD server.
I've found that on the Linux side of things I needed the VFS objects of Catia and Fruit. You have to enable extended attributes for each share too. It for the most part works on our Yosemite through High Sierra machines. Since enabling these options I've noticed server load go WAY down. I also disabled ACLs so that it's just simple UNIX permissions since we are an all Mac shop. Now if I can just keep the browsers from periodically crashing.
Hey everyone, I solved this issue by following various instructions. First, on the macOS client, issue the commands found in. Then, on the Samba server, use the configuration.
Note that I only used the. global.section from that config. And obviously tailor the config to your own environment. The Samba server I use is a FreeBSD 11.1 machine with Samba installed via the pkg(7) command. The package is samba47-4.7.41.
But any OS should work as long as Samba is properly configured. I use user type Samba security and created the Samba user via this command: sudo pdbedit -a username Ideally use the same username / password as the one from which the macOS client is going to access the Samba share. Note that I did have to reboot the macOS client to make sure it worked properly. Otherwise, the Finder would refuse to unmount the SMB volume or would throw an exception saying that the file(s) were already in use. Which was pure BS.
I am having a lot of problems with Excel and SMB shares on our Windows 2012 R2 Shares server. I am ready to either switch the effected users to PC's or put ExtremeZ-IP on the server. Problems include.
Open Files - Files locked because they show as open on the files server until the user un-mounts the volume.smbdelete file - appearing and causing issue when users try to save xlsx files. Errors - users cant save xlsx files but can save xls files. Ghost folders mutiplying every time a user saves certain excel files. Example 'every time a user saves an excel file called test.
A folder is created test.xls.sb-141gbdb4949-zxlu8w' The next save will create another folder but the charaters after xls.sb- are different. I have to say. Mac SMB and Windows SMB do not play well at all.
I have tried multiple fixes to no avail. Has anyone found 100% success fixing these issues. All my Macs are on High Sierra.
Windows XP Network Places displaying shared Mac folders. Setting up Leopard (OS X 10.5) to share files with a PC running Windows XP is a fairly straightforward process, but like any networking task, it's helpful to understand how the underlying process works. Beginning with Leopard, Apple reconfigured the way Windows file sharing is set up. Instead of having separate Mac file sharing and Windows file sharing control panels, Apple placed all file sharing processes in one system preference, making it easier to set up and configure file sharing. In ‘File Sharing With OS X 10.5: Share Mac Files with Windows XP’ we will take you through the entire process of configuring your Mac to share files with a PC. We'll also describe some of the basic issues you may encounter along the way.
Windows Vista Network displaying shared Mac folders. Setting up Leopard (OS X 10.5) to share files with a PC running Windows Vista is a fairly straightforward process, but like any networking task, it's helpful to understand how the underlying process works. In ‘File Sharing With OS X 10.5: Share Mac Files with Windows Vista’ we will take you through the entire process of configuring your Mac to share files with a PC running Windows Vista in all of its various flavors. We'll also describe some of the basic issues you may encounter along the way.