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. 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.DS_Store file that stores metadata for all files that are opened. What happens with the network share it that the.DS_Store file is recognizing that the file is in use. How to Back Up a Mac. This wikiHow teaches you how to back up the data and files on your Mac to an external hard drive and/or Apple's cloud-based storage service, iCloud. Solution: Prevent Finder from creating.DS_Store 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.
0 Комментарии
Оставить ответ. |
АвторНапишите что-нибудь о себе. Не надо ничего особенного, просто общие данные. Архивы
Март 2019
Категории |