![]() The folders that the disk are mounted on are inaccessible from finder, but the user still has permissions to access the folder.Īccessing the contents of the folder works in terminal, but when I try to open it in finder, this happens:r, this happens: SMB Server showing connected disk as inaccessible even though the user has permissions to view the folder I have a SMB server running on a raspberry pi with a bunch of connected disks mounted in a folder on the device. Does anyone have any suggestion as to how this can be fixed - or is it a fault with the new MacBook Pro? I do not use FileVault so this is not the issue. I have tried smb//*.* and the same thing happens - I access the full MacPro disk, I can access the root folders, but it will not provide access to the Desktop files. I therefore assume that the issue is the new M1 MacBook Pro as it is the only Mac that will not allow others to access the files in the desktop folder. The Pro will successfully access all files on both the Air and the Mini. When selecting and opening the Desktop file, nothing appears - it will not access the required files. ![]() I can access the Pro from both the Air and Mini Finder Go menu, sign on as Administrator, and see the root folders including Desktop. Since getting the replacement M1 Pro, I have found that Sharing does not work. I also have an Intel MacMini on Monterey which also had no issue accessing all the files on the old 2013 Pro. When it is in use I use an M1 MacBook Air on Monterey and work on the master files using Sharing. M1 MacBook Pro on Monterey will not share files I have just replaced a 2013 Pro with a MacBook M1 14" Pro. This connection ONLY drops during a copy and this is all on a wired connection. One last thing I tried was copying the files directly from the Mac to the Shared folder/drive via Microsoft Remote Desktop on the Mac and getting the server to copy the files, but while copying the connecting keeps dropping to the server. ![]() The only workaround so far is copying the files to an ancient Seagate NAS then copying the files to the right place via either a Windows virtual machine or Microsoft Remote Desktop on my Mac or another machine. This all worked fine before the 'upgrade' and my MacBook Pro which is still on Catalina still works fine. I remember this was an issue with 10.6 and the workaround was changing something in the smb.conf file. ![]() Attempting to copy a file to a shared drive/folder results in the error " The operation can’t be completed because you don’t have permission to access some of the items.". I have several NAS drives (Qnap and Drobo) and a Windows 2016 server to which I can't copy files since upgrading to Monterey 12.1. Getting a sense of deja vu with SMB mounts. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |