What about a 3rd party Finder alternative, such as Pathfinder? It was the same on all previous versions. If this happens disconnecting and reconnecting back to the share seems to clear it, but its a pain in the ass. Go to the  Apple menu and choose ‘System Preferences‘ from the drop down menu. Can you share details about your Synology RAID? It can help solve lots of macOS Big Sur issues by boosting your Mac’s capabilities. If you do not want that we track your visist to our site you can disable tracking in your browser here: We also use different external services like Google Webfonts, Google Maps and external Video providers. Apple’s timeline for addressing its SMB problem is completely unacceptable. It can help solve lots of macOS Big Sur issues by boosting your Mac’s capabilities. I removed all ACLs and disabled NT ACLs from the home folders which seemed to work for the file locking issue. We’ll need to know the model number, configuration and current firmware version of the Synology box. We are moving toward all endpoints to be 10.14.3 (or latest). We didn’t test against Synology, but a Microsoft Server 2012r2 and Qumulo which is a scale-out NAS http://qumulo.com/. I tried it several times. I am encountering this same issue on High Sierra (10.13). Have observed through windows open file utility that when a user traverses into a directory the directory is considered locked but when they back out it indeed unlocks right away. Companies that use macOS file sharing had to resort to rolling back their OS or using AFP. Eventually we were able to narrow it down enough to be able to consistently duplicate what they were seeing. By default, Apple has disabled NetBIOS in MacOS 10.5 to speed up SMB operations like mounting, browsing & connecting to an SMB share. Most of them say “switch to AFP and the problem goes away.” That’s nice but I specifically use SMB because I have a share that’s accessed by Linux, Mac, and Windows - and so SMB is the right solution to keep file naming consistent. (To push recursively the ACL settings), Then the ACL looks like this. This fix also applies to Mac OS X 10.11 El Capitan. We also see some files that are opened with Write + Read access – this is to be expected when people are working off the server. We have a similar setup using mercurial, and this is causing us problems too. – therealmarv Nov 24 at 16:50 @therealmarv It's vfs_fruit you're talking about, and that won't make SMB fly on Macs on 10gigE or faster network. Thank you! • Apply permissions to groups with Read Only or Modify access sudo tcpdump -i BSDname -s 0 -B 524288 -w ~/Desktop/100290794256.moverename.pcap. I had bound the server to an AD, and unbound it later. Copyright © 2012-2020 - miapple.me™ - Tech.Blog, Now you need to use a separate password for your local Mac account. So if you won’t need them to fix macOS problems (which we hope you won’t), you’ll need them for lots of other jobs. Otherwise, stay tuned. Some Mac users have reported a variety of problems with MacOS Catalina, ranging from installations getting stuck or taking abnormally long, to problems with some apps not working, to issues with certain printers or accessories no longer working, App Store difficulties, iCloud and Apple ID issues, amongst other nuisances. https://swissmacuser.ch/workaround-connecting-smb-fileshare-in-macos-mojave/#.W5lVvi0UVE4. In Yosemite (macOS 10.10) and later, connecting in the Finder by select Go > Connect to Server and entering smb:// plus the IP address or full name of the server. We couldn’t replicate the issue. If you are on MacAdmin slack, can you send me a direct message. We will test too and post back to the blog with details. I’m more than happy to gather additional information as required. Many of the Mac administrators we reached out to for confirmation claimed they didn’t see it, until they followed our steps. I couldn’t reproduce this on a Synology share, so perhaps it is Microsoft Window Share specific. Please be aware that this might heavily reduce the functionality and appearance of our site. You cannot activate SMB Windows file sharing because the user is grayed-out. I thought this setting looked fine, since I saw others on the web using same ACL. But you can make adjustments to optimize SMB browsing in enterprise environments. We are moving all endpoints to be macOS 10.14.3 (or latest). Seitdem gibt es vor allem beim Zugriff auf SMB2-Freigaben unterschiedliche Probleme. Not the ideal solution, but it does work. echo “notify_off=yes” >> /etc/nsmb.conf. Then if I go into the file and modify it, save it. Nor can you do anything to any folder directly above this file (e.g. Then unmount and remount any SMB shares. Fixing SMB Windows file sharing not working_cannot connect to iCloud. If so, you can directly contact me on MacAdmin slack and send me the files. Companies that use macOS file sharing had to resort to rolling back their OS or using AFP. • Flat permissions across the entire share 192.168.0.61. Also having permissions issues saving Photoshop documents (and in other apps too). 4. https://macadmins.slack.com/team/U09H7JPPE, Connecting an SMB fileshare in macOS Mojave is not working? On an SMB1 server, enabling signing can affect performance. Search on how to activate "fruity" on your Samba configuration and deactivate signing required on SMB on macOS. For SMB windows file sharing, you need to select a user for activation. The last major holdout is files themselves are held once opened and closed for ~20 minutes. Mac Bug Connecting to Non-Apple SMB Shares, https://apple.lib.utah.edu/wp-content/uploads/sites/9/2016/02/bug_demo_720p.mp4, https://openradar.appspot.com/radar?id=6119440361979904, https://helpx.adobe.com/photoshop/kb/networks-removable-media-photoshop.html, https://macadmins.slack.com/team/U09H7JPPE, https://swissmacuser.ch/workaround-connecting-smb-fileshare-in-macos-mojave/#.W5lVvi0UVE4, https://www.ixsystems.com/community/threads/smb-deleting-large-folders-fails-from-macos-finder.74832/, Marriott Library - Apple ITS | Google Chrome for Kiosks Posted to GitHub, Episode 158: Bradley Chambers and Apple @ Work – Mac Admins Podcast, Mac Managers Meeting – Directions – 1705A, Episode 157: Justin Esgar and ACEs – Mac Admins Podcast, Simple Certificate Enrollment Protocol (SCEP). To recap – I saw this issue on a SMB share on an FreeNAS server set up for a dataset with the permissions type Windows, meaning that Samba ACL were set for all directories and files under the share. Are you seeing this issue with applications that officially support opening/saving to network shares? I had a few questions regarding the behavior on 10.13: 1. Thanks for the feedback. Great, glad to hear it. Do you have the Apple Case # so that we can also run this up the chain via our Apple Engineer? Mamdoh -------------- Hi everyone, I’m having a problem with SMB shares on MacOS Sierra. We use cookies to let us know when you visit our websites, how you interact with us, to enrich your user experience, and to customize your relationship with our website. I will let you know what additional data they request. In macOS High Sierra 10.13 and later, the default settings for browsing network folders such as Server Message Block (SMB) shares are ideal for most organizations and users. However, I have seen issues like this before, which are usually linked to Windows permissions. But, if you post details of your Synology model and SMB configuration I can add it onto the AppleCare Enterprise problem ticket. Other users in my workplace suffer the same frustration. I deleted “com.apple.frameworks.diskimages.diuiagent.plist”, restarted, and the problem has gone away. It appears the SMB client in Mac OS X (10.11, 10.12 and possibly others) is overly aggressive with file locks. You can block or delete them by changing your browser settings and force blocking all cookies on this website. Earlier this year we received a number of reports from users that were unable to delete, move or rename documents on a new SMB file share. If anyone out there has seen client side adjustments or workarounds would be great to hear what those are. getfacl /mnt/MyShare Under macOS Mojave, High Sierra, Sierra, El Capitan or Yosemite, users should use SMB 2 or SMB 3 as protocols to connect to the server. Issue still exist… with also High Sierra/Sierra/El Capitan installed, latest version, but no luck… printf “[default]\nsigning_required=no\n” | sudo tee /etc/nsmb.conf >/dev/null We’ve notified Apple and Microsoft about the issue. SMB1 scheint zwar weniger betroffen zu sein, ganz problemfrei ist es scheinbar ebenfalls nicht. Would save it as a hidden file. Earlier this year we received a number of reports from users that were unable to delete, move or rename documents on a new SMB file share. sudo rm /etc/nsmb.conf Turning on/off Finder previews has no effect. https://openradar.appspot.com/radar?id=6119440361979904. Hi, I am an end user (not IT guy) using Catalina and accessing files on a server at my Uni via smb and have what I think is the same frustrating issue with renaming folders, including the test case (A, B, C). I would recommend checking the accounts/groups permissions that were used to create the files. The real cause of this problem is that you most probably use the same password for accessing your Mac and as your iCloud password. I do have this same issue on my Synology RAID! We are finding Mojva and Catalina Shares and file permissions access changing by themselves . If this does not resolve the issue, please send me what steps you take to reproduce this and the behavior seen on the second client with the locked files. Here's what that looks like in … These files opened in Read only mode are not an issue on a server running a Unix-type operating system. I have previously set the server to ignore execute bit permissions, with a similar create mask. We may request cookies to be set on your device. After that, whether or not I change the name during that first chance, clicking twice or right clicking on the same folder does nothing, and “Rename” in the Finder menu is grayed out. For enabling SMB windows file sharing, you need to change the password of your local account on your Mac and NOT the iCloud password: Fixing SMB Windows file sharing not working_user not grayed-out anymore. Open iCloud preferences to fix this problem.‘ The fix for this is the same as for SMB Windows file sharing. These cookies collect information that is used either in aggregate form to help us understand how our website is being used or how effective our marketing campaigns are, or to help us customize our website and application for you in order to enhance your experience. If you haven’t found your problem on the list, we encourage you to try a system clean up anyways. Hi Daniel, where did your find the locations for “com.apple.frameworks.diskimages.diuiagent.plist” please? If the fix is causing other issues or lack of SMB connectivity, and you need to reverse it – simply delete the /etc/nsmb.conf file with this command. Eventually we were able to narrow it down enough to be able to consistently duplicate what they were seeing. Due to security reasons, you cannot use the same password for both your Mac and iCloud anymore. It gets to the point we have to create a new folder and drag everything into the properly named new folder…then delete the unwanted version. The issue were only seen on clients that were native Mojave or Catalina. Changes will take effect once you reload the page. It’s irritating. Discover new features for Maps and Messages. It only resolved the problem in one directory somehow…. Here is a movie of the bug in action. Seit OS X 10.9 Mavericks verwendet Apple statt Samba eine eigene Implementierung des SMB-Protokolls. Was also having issues save as from Adobe. I experienced no issues on my own Mac which runs Mojave client (upgraded from Sierra to High Sierra and then to Mojave) and therefore I were not suspicious at first. If you want to add an existing user for SMB file sharing open ‘Options…‘ for selecting and activating the user. disable column view preview window as the server considers the preview file an open file so it locks the file when a user has it simply highlighted…fairly easy solve although it takes away functionality somewhat. This should not be a problem if your NAS is less than 5-6 years old, because SMB 3.0 was introduced in 2012. I’d like some more info as well, if this has fixed the problem for you. Original rename issue appears resolved! Thanks for the feedback & best practices advice, but the issue was confirmed by Apple and supposedly fixed in macOS High Sierra. Open up a terminal and enter this command. Here are the release dates: 10.14.5 – May 13, 2019 10.14.6 – July 22, 2019. Thanks Richard – it’s frustrating that Apple are pretty much EOLing macOS Server (basically turning it into Profile Manager.app) and yet we have so many issues working with 3rd party server platforms. I am still waiting on AppleCare Enterprise. Let me forward that information to our AppleCare Enterprise problem ticket and I will let you know what Apple responds. SMB was disconnecting from file shares too frequent and virtually unusable. Have you tried contacting Synology technical support about it? Click to enable/disable Google Analytics tracking. Packet signing for SMB 2 or SMB 3 connections turns on automatically when needed if the server offers it. I cannot replicate the issue using macOS 10.2.6 with a Windows 2008 R2 SMB share. The key is to set your NAS to use SMB 3.0 or later. The directories and files had following ACL seen by running ‘getfacl /mnt/MyShare’: # owner: root Like model/make and configuration. Thanks for the reply, yes if you can following the folder operations creating folder A/B/C, etc) needs to be done in Finder as this is a primarily a Finder bug. Let us know if this works around the issue in High Sierra. If you still are seeing the issue, please comment back with details on your SMB server configuration.