Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

alembic

macrumors regular
Original poster
Oct 13, 2005
185
40
Last week my Mac Studio on Sonoma 14.4.1 lost access to all network shares hosted on a Synology NAS running DSM 6.2. I suspect it was caused by a security update which brought my system to 14.7.3 although I can't be 100% sure about that. Anyway, I do think the issue rests with the Mac Studio because my older laptops running pre-Ventura have no problem accessing SMB shares. Also a Raspberry Pi can still access NFS shares on the NAS. Oddly, the Mac Studio can access the NFS share on the Pi. All devices are on the same LAN subnet.

I've been using the Finder command-K feature, Forklift, NFS Manager, and CyberDuck to debug the issue. These applications can connect to the NAS, my credentials are accepted (confirmed in Synology logs), and where applicable, a root directory list of the share is displayed. But when I try to open a file or navigate into one of the folders, I get the Loading... cursor until the request times out (or I unmount the share manually to avoid a force-quit).

Essentially the Mac Studio can no longer access NAS share files using NFS/SMB/AFP/SFTP.

I've tried:
  • upgrading the Mac Studio to 14.8.3
  • logging in as another user
  • restarting in safe mode
  • installing Sequoia on a separate volume and logging in as a new user
  • CLI mounts which lead to the same spinning cursor in Finder
Updating the Synology NAS to DSM 7 is my last option but since other devices aren't experiencing this issue, I'd like to avoid it unless absolutely necessary.

I'm stumped. Any suggestions greatly welcomed!
 
It's a PITA but try testing specific SMB versions one-by-one

You can also try deleting the SMB share credentials from your KeyChain so you have reauthenticate when mounting the share.
 
Thanks Bigwaff. The first thing I did was remove all Keychain entries related to NAS logins to rule out authentication as a factor.

I didn't mention that I have 3 Bluesound devices that are using SMB2 to play FLAC files. The NAS also offers SMB3 so I've kept that option as well.

I considered a firewall problem but it's disabled on the Studio. And to have 4 file protocols go south at the same time on one machine leads me to believe something was tightened down in Sonoma/Sequoia, but I have yet to find a workaround. One share has only 50 to 60 files, all log or script files, so it's not a directory volume issue.

From my research, it appears SMB has been a mess for macOS over the years so I'm focusing more on regaining access to my NFS shares.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.