I'm on 12.3.1 and updating to 12.4 now. I will let you know if that works!
EDIT: It did not work.
Last edited:
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
SMB broken with Monterey
- Thread starter Agustis
- Start date
- Sort by reaction score
EDIT: It did not work.
That looks a bit complicated, not sure what exactly to do. Can someone help explain? 🙏
EDIT: Tried it but get:
append: Invalid Path
<dscl_cmd> DS Error: -14009 (eDSUnknownNodeName)
Last edited:
I feel like this was almost fixed in 12.3.1, but then it came back with a vengeance in 12.4
I have two SMB servers on my home network. One is a Truenas device and the other is a Machine running Ubuntu that runs as my music server. After creating an authorized SMB user on both of them, connectong to them from my Mac Studio has been painless.
I use both Finder and a program called Forklift.
I use both Finder and a program called Forklift.
Inter alia Time Machine, Finder, VLC, BBEdit, Pixelmator Pro, Preview, LibreOffice
We have just run into this SMB issue on our corporate network. It seems this bug does not discriminate as it is affecting our Intel Macs that were upgraded or clean installed to Mac OS 12; as well as our newer Mac silicon based laptops and Mac Studios. The Mac silicon devices are a major issue as we can't roll these back to OS 10 or 11 – so are now very expensive paper weights!
In our testing so far I think the issue might be with Apples implementation of SMB v2. We have servers from three different vendors (Nexenta, Synology and Infortrend).
We do not seem to be experiencing any issues when accessing the shares that are hosted on either the Synology or Infrotrend servers. The Nexenta shares however are causing the Mac finder to lockup/crash to the point where the only escape is a hard reset/killing the power.
If you run the following command in the terminal with the shares mounted it will show what SMB version is being used:
smbutil statshares -a
In our case the Synology and Infortrend servers are using SMB Version 3.1.1. The Nexenta is using SMB Version 2.1.
If I mount the Nexenta shares using SMB Version 1 the Finder doesn't crash, however the read/write speed is not workable dropping to 60 MB/SEC Read and 3 MB/SEC Write of a 10G connection vs 932/157 under SMB 2.
In case others want to test I found the quickest way to force the connection to SMB v1 was to use cifs:// rather than smb://. I also tried various permutations through the /etc/nsmb.conf option but the results were the same.
I can not rule out that it might be a clash between Nexenta's implementation of SMB 2 and Apples - however I lean more towards it being on Apples side as we do not have this issue with Macs running OS 10 or 11, only 12.
In our testing so far I think the issue might be with Apples implementation of SMB v2. We have servers from three different vendors (Nexenta, Synology and Infortrend).
We do not seem to be experiencing any issues when accessing the shares that are hosted on either the Synology or Infrotrend servers. The Nexenta shares however are causing the Mac finder to lockup/crash to the point where the only escape is a hard reset/killing the power.
If you run the following command in the terminal with the shares mounted it will show what SMB version is being used:
smbutil statshares -a
In our case the Synology and Infortrend servers are using SMB Version 3.1.1. The Nexenta is using SMB Version 2.1.
If I mount the Nexenta shares using SMB Version 1 the Finder doesn't crash, however the read/write speed is not workable dropping to 60 MB/SEC Read and 3 MB/SEC Write of a 10G connection vs 932/157 under SMB 2.
In case others want to test I found the quickest way to force the connection to SMB v1 was to use cifs:// rather than smb://. I also tried various permutations through the /etc/nsmb.conf option but the results were the same.
I can not rule out that it might be a clash between Nexenta's implementation of SMB 2 and Apples - however I lean more towards it being on Apples side as we do not have this issue with Macs running OS 10 or 11, only 12.
Same issues here with both personal Macbook Air and work MacBook Pro, both running Monterey 12.4. I can FTP from them to my D-Link 323 NAS but can't connect via SMB or AFP. I grabbed my wife's ancient MacBook Pro (2009) running El Capitan 10.11.6 and I was able to connect via SMB 1st time. Wi-Fi interface is 802.11n not 11ac so it's slow but I'm connected and can copy files off to new media.
As a test I would be interested to know if you connect using cifs:// rather than smb:// does it let you in without killing the Finder.
Using cifs:// drops it to SMB v1 that is still painfully slow but doesn't kill the finder.
Using cifs:// drops it to SMB v1 that is still painfully slow but doesn't kill the finder.
If anyone is thinking of bailing on their old Time Machine, stick it in the classifieds for $50. People like to put new high capacity HDD's in them and use them as an NAS.
It's a bit irritating that Apple decided against updating them with more capable firmware, and just relegated them to the landfill instead.
It's a bit irritating that Apple decided against updating them with more capable firmware, and just relegated them to the landfill instead.
Last edited:
I can connect via cifs:// as well as smb:// from El Capitan. I don't observe smb killing finder.
Been suffering system hangs, kernel panics and restarts when transferring large amounts of files over SMB for months now on two different M1 systems (M1 Max MBP, M1 Ultra Studio). macOS 12.5 did nothing to help.
The destination/source is a 2013 Mac Pro trashcan running macOS 12.5 as well (generally updated a few weeks after my M1 systems), and hasn't suffered any of the issues.
Currently trying a large transfer over CIFS, definitely slower than SMB over my 2.5G ethernet, but not seeing the big dips and crests in the transfer speeds like I have been with SMB.
What a mess Apple, sort this crap out.
The destination/source is a 2013 Mac Pro trashcan running macOS 12.5 as well (generally updated a few weeks after my M1 systems), and hasn't suffered any of the issues.
Currently trying a large transfer over CIFS, definitely slower than SMB over my 2.5G ethernet, but not seeing the big dips and crests in the transfer speeds like I have been with SMB.
What a mess Apple, sort this crap out.
On a Studio Ultra I've done 100's of SMB transfers to a NAS via CCC with no problems at all.
If you have an anti-virus (at either end) does it make any difference if you turn it off? I did have problems with glacial transfer speeds with Sophos. Worked the issue with them, they rewrote the code (took quite a few months) and now I see speeds that can reach ~500 MB/s over thunderbolt or 10 GbE.
I’ve never used an antivirus program on a Mac.
Turned out to be for naught, as the system ground to a halt them kernel panicked despite using CIFS.
I’ve done hundreds of transfers too, it’s the long super large ones (hundreds of GBs if not a few TBs) that eventually make the system slow and crash.
Turned out to be for naught, as the system ground to a halt them kernel panicked despite using CIFS.
I’ve done hundreds of transfers too, it’s the long super large ones (hundreds of GBs if not a few TBs) that eventually make the system slow and crash.
I’ve worked around it.
The problem is Apple. The same SMB version on Linux works. Whatever Apple did broke it.
It goes to sleep, and looks like it’s still connected, but when you try to access it, the system times out.
On Catalina, the solution was to use AFP, but they removed it since, so it’s no longer possible to create AFP shares. This means you are forced to use their buggy SMB, and as everyone can see from this thread, there’s no fixing it.
My workaround is an AppleScript app I created that touches a null file on the share every 5 minutes. This has completely stopped the share from timing out.
My problem was my media server and my MacMini on my TV. Kodi would just error out, but it should solve the problem for every case. It just prevents the share from going into a sleep state.
5 minutes seems to be the magic number. Any longer, and it will sleep and time out.
I am running my keep alive AppleScript from my Kodi MacMini TV box, not on the server itself.
Until Apple takes bugs seriously, and decides to fix it, this works, but don’t hold your breath. This bug has been around since Catalina. It was just easier to use AFP instead of SMB, but now they decide to remove what worked, and force us to use something that doesn’t. BTW: I’ve tried every other solution here as well as others before coming up with my solution. No other solution has worked. Some seemed to, but later failed. And no, my server doesn’t go to sleep. I get a lot of comments from people thinking I missed something, but I have tried them all. Many people don’t even understand that AFP was removed. Yes, you can connect to an AFP share from an older OS, or NAS, but you cannot create an AFP share from any OS greater than Catalina, it’s been removed.
The problem is Apple. The same SMB version on Linux works. Whatever Apple did broke it.
It goes to sleep, and looks like it’s still connected, but when you try to access it, the system times out.
On Catalina, the solution was to use AFP, but they removed it since, so it’s no longer possible to create AFP shares. This means you are forced to use their buggy SMB, and as everyone can see from this thread, there’s no fixing it.
My workaround is an AppleScript app I created that touches a null file on the share every 5 minutes. This has completely stopped the share from timing out.
My problem was my media server and my MacMini on my TV. Kodi would just error out, but it should solve the problem for every case. It just prevents the share from going into a sleep state.
5 minutes seems to be the magic number. Any longer, and it will sleep and time out.
I am running my keep alive AppleScript from my Kodi MacMini TV box, not on the server itself.
Until Apple takes bugs seriously, and decides to fix it, this works, but don’t hold your breath. This bug has been around since Catalina. It was just easier to use AFP instead of SMB, but now they decide to remove what worked, and force us to use something that doesn’t. BTW: I’ve tried every other solution here as well as others before coming up with my solution. No other solution has worked. Some seemed to, but later failed. And no, my server doesn’t go to sleep. I get a lot of comments from people thinking I missed something, but I have tried them all. Many people don’t even understand that AFP was removed. Yes, you can connect to an AFP share from an older OS, or NAS, but you cannot create an AFP share from any OS greater than Catalina, it’s been removed.
Was on 12.5 and now on 12.6 as of today and smb to my unraid server is slowwwwww. Windows is, as it always has been, as fast as its supposed to be.
The update to 10.6 broke my file-sharing connection to my 2011 mac mini server running High Sierra. I have spent an entire day on it so far and am nowhere near any closer to getting access back. Has anyone had any luck yet?
*edited, it also broke my Time Machine backups and now I have nothing.
*edited, it also broke my Time Machine backups and now I have nothing.