SMB broken with Monterey

[Agustis]

I have a public Azure Files Share. After upgrading to Monterey I can no longer access the share. I have tried with another laptop on my network running Big Sur and it works fine, so I know it is not my network or firewall. The error I get just says it can’t find the IP or the server is down. I use the exact command I run on Big Sur so I know it’s using the right connection string. Any help is greatly appreciated.

**Update**
I also just noticed that my Time Machine also doesn't work which is also using SMB

 

[titan4]

I have a public Azure Files Share. After upgrading to Monterey I can no longer access the share. I have tried with another laptop on my network running Big Sur and it works fine, so I know it is not my network or firewall. The error I get just says it can’t find the IP or the server is down. I use the exact command I run on Big Sur so I know it’s using the right connection string. Any help is greatly appreciated.

**Update**
I also just noticed that my Time Machine also doesn't work which is also using SMB

I know this is bit of a late answer, but I had similar issues with SMB after upgrading to Monterey. Not sure if your problem is the same but trying won't hurt.

After going through logs and wiresharking the connection and seeing handshake issues I went through some config and found out that the problem was that SMB1 is enabled by default and somehow was causing issues with handshake. So I changed supported protocols to only allow SMB2/3 and it started working again.

If you want to try, you can edit ~/Library/Preferences/nsmb.conf (only for a user) or /etc/nsmb.conf (for all users, but you will need to use sudo) and add:
[default]
protocol_vers_map=6

 

[Love-hate 🍏 relationship]

I know this is bit of a late answer, but I had similar issues with SMB after upgrading to Monterey. Not sure if your problem is the same but trying won't hurt.

After going through logs and wiresharking the connection and seeing handshake issues I went through some config and found out that the problem was that SMB1 is enabled by default and somehow was causing issues with handshake. So I changed supported protocols to only allow SMB2/3 and it started working again.

If you want to try, you can edit ~/Library/Preferences/nsmb.conf (only for a user) or /etc/nsmb.conf (for all users, but you will need to use sudo) and add:
[default]
protocol_vers_map=6

I don't get it ,can u enable both 2/3 or do I have to pick between the two ?

So you have to CD to /library/préférences/etc/nsmb.conf and enter the command "sudo protocol_vers_map=6?

 

[titan4]

I don't get it ,can u enable both 2/3 or do I have to pick between the two ?

So you have to CD to /library/préférences/etc/nsmb.conf and enter the command "sudo protocol_vers_map=6?

No. 6 means both SMB2 and 3. There are basically 5 possible settings:
7 SMB 1/2/3 enabled (default)
6 SMB 2/3 enabled
4 only SMB 3 enabled
2 only SMB 2 enabled
1 only SMB 1 enabled

You need to add the text into a file nsmb.conf.
Either for a single user in the users's Library - ~/Library/Preferences = /Users/<username>/Library/Preferences (not the system Library like you said, the ~ denotes user's home directory) or in /etc for all users.
Also note that the [default] header has to be there. By default the file does not exist so you need to create it (unless you already have it for some reason). So if you create a new file it should look like this:

[default]
protocol_vers_map=6

You can also try following these instructions from Apple: https://support.apple.com/en-us/HT211927 if you are not sure what you are doing. They disable NetBIOS in addition but that's not a bad thing and is supported by SMB1 only anyway.

 

[white7561]

I have a public Azure Files Share. After upgrading to Monterey I can no longer access the share. I have tried with another laptop on my network running Big Sur and it works fine, so I know it is not my network or firewall. The error I get just says it can’t find the IP or the server is down. I use the exact command I run on Big Sur so I know it’s using the right connection string. Any help is greatly appreciated.

**Update**
I also just noticed that my Time Machine also doesn't work which is also using SMB

I'm on Monterey and I'm using SMB daily on my laptop and it's fine . The smb server is hosted by my raspberry pi 4. Which is probably using the smb 3 if that helps

 

[dialekt]

I was just getting ready to make another thread but found this one....

I've got a QNAP TVS-872XT NAS that I've set up but it's been a headache trying to do creative work on it. Constantly trying to mount the drives. I've had a few crashes to my computer on MAC OS Monterey using the latest Final Cut Pro. I've also had server interrupted connection issues. Some people say to disable SMB signing but for some reason all the terminal commands suggested don't seem to take when it comes to Monterey. Anyone else ever had this same issue? Really want to have a stable mounted server/nertwork drive that I can access all my media and edit from. I've referenced a few threads as well but nothing has been resolved - https://forums.macrumors.com/threads/catalina-smb-crash-with-final-cut-pro.2224843/. (this seems to have made performance a little worse for me.

I've followed these terminal steps suggested by apple but nothing seems to take upon checking with the command smbutil statshares -a (still says TRUE on signing supported) - just wondering what I'm doing wrong. M1 MacBook Pro 13

 

[titan4]

I was just getting ready to make another thread but found this one....

I've got a QNAP TVS-872XT NAS that I've set up but it's been a headache trying to do creative work on it. Constantly trying to mount the drives. I've had a few crashes to my computer on MAC OS Monterey using the latest Final Cut Pro. I've also had server interrupted connection issues. Some people say to disable SMB signing but for some reason all the terminal commands suggested don't seem to take when it comes to Monterey. Anyone else ever had this same issue? Really want to have a stable mounted server/nertwork drive that I can access all my media and edit from. I've referenced a few threads as well but nothing has been resolved - https://forums.macrumors.com/threads/catalina-smb-crash-with-final-cut-pro.2224843/. (this seems to have made performance a little worse for me.

I've followed these terminal steps suggested by apple but nothing seems to take upon checking with the command smbutil statshares -a (still says TRUE on signing supported) - just wondering what I'm doing wrong. M1 MacBook Pro 13

Try adding this to the same config file:
signing_required=no

 

[phloo]

I am having the same problem after switching from Mojave to Monterey (plus from Late 2016 MBP t M1)
Did you find a solution? TM shows me the old backups on the SMB connected folder. Finder can mount the server easily. But I get the same error message when I try to connect TM with the SMB folder. (how can it see it but not be able to connect?)

edit:

After trying several suggestions from different forums and sites, I removed the password from the keychain and rebooted the machine and nas. First it didn't find the drive, so I checked it via finder and connected it with the credentials. Result was fine. So then I added the drive again in Time Machine, it asked for username and password and voila: it restarted to back up again after it asked to re-use the old backup or create a new one.

What a weird behaviour.

 

[Lilibu]

The origInal Monterey (12.0) was fine. The 12.0.1. security update made this. And it is still a problem at 12..2.1. NO FILE SHARING AT ALL

 

[ispcolohost]

Just wanted to +1 this. I just upgraded my iMac 27 2019 x86 to Monterey 12.2.1 from Catalina. I use a Synology DS1019+ running latest DSM for holding Vmware Fusion VMDK's for my various Windows VM's. The config is SMB2+Jumbo minimum and SMB3 max on the Synology. On the Mac side I'd not yet disabled signing required as it had never been an issue previously.

The VM's seemed sluggish immediately after upgrading and within a few days one had corrupted itself in a way that no longer lets it boot. Vmware Fusion tools could not repair. Windows DVD could not repair. I copy the VM to local storage using rsync over ssh to the synology since I'm not trusting SMB at this point. That at least let me install a new Windows over top to recover my files from Windows.old where it moves the prior OS install.

I start tinkering with settings, did some disk benchmarking, the performance is way off. My config uses the onboard gigE, but with jumbo frames and vlan virtual interfaces so my computer can be on my normal network plus a non-routed storage network where the Synology lives. The MTU is 9000 on the ethernet interface, 1500 on the primary vlan, 9000 on the storage vlan.

Tried to install a fresh Windows 10 VM, it fails at random parts in the process with disk I/O errors. The share will also go inaccessible at times. Tried the SMB signing thing, no change.

I connect a Thunderbolt to Ethernet adapter I had lying around and cable it into the second ethernet on my Synology, then go back to non-jumbo, and since it's dedicated, no vlan interfaces on top of the ethernet interface. The disk benchmarking tools return to normal performance in this configuration over SMB, but still seem to disconnect the share at times. I also still can't make it through a Windows install to an end product that ultimately boots, although it runs much quicker.

So it seems Monterey has tinkered with virtual interfaces in a performance impacting way, and SMB seems somewhat broken as well, to the point that file corruption results. Am continuing to play with it to see if I can find a working config, may reach out to Synology support. Am also going to do some more testing with other tools outside of vmware fusion to see if I can reproduce the corruption issue definitively.

 

[Xerxes004]

I just wanted to chime in on this thread because I've been posting in another thread that has eerily similar issues.

Time Machine error: The backup disk image xxx.sparsebundle could not be accessed (error 16)

Same issue here on both a MacBook and a Mac mini. I suspect it is something with the WD Firmware. It seems to have stopped after the latest update. I did a reboot of the NAS and now it seems to be working on both

forums.macrumors.com

 

[Xerxes004]

Nothing I tried anywhere seemed to work at all. I just gave up and created a new data pool and SMB share. Initial backup is happening now. Luckily I only have like 400GB of stuff.

 

[ispcolohost]

I just wanted to chime in on this thread because I've been posting in another thread that has eerily similar issues.

Time Machine error: The backup disk image xxx.sparsebundle could not be accessed (error 16)

Same issue here on both a MacBook and a Mac mini. I suspect it is something with the WD Firmware. It seems to have stopped after the latest update. I did a reboot of the NAS and now it seems to be working on both

forums.macrumors.com

I gave up on TimeMachine to SMB shares a while back. It would always for for me for a few weeks or even a few months, but ultimately hit a non-recoverable issue rending the entire backup set unusable. It became too much of a liability. Losing one hour or day fine, but when you don't know from one day to the next if the entire backup will break, I could no longer trust it. I have a thread on here related to that.

I don't know if it's specifically TimeMachine to SMB or my use case of many terabytes, but I gave up. I use Retrospect on the Mac side now to do point in time file-based backups to the Synology and then snapshots + replication on it to another array.

 

[Xerxes004]

I gave up on TimeMachine to SMB shares a while back. It would always for for me for a few weeks or even a few months, but ultimately hit a non-recoverable issue rending the entire backup set unusable. It became too much of a liability. Losing one hour or day fine, but when you don't know from one day to the next if the entire backup will break, I could no longer trust it. I have a thread on here related to that.

I don't know if it's specifically TimeMachine to SMB or my use case of many terabytes, but I gave up. I use Retrospect on the Mac side now to do point in time file-based backups to the Synology and then snapshots + replication on it to another array.

Yeah, I get the sentiment. I built my NAS a couple years ago and had zero problems until December. I backed up automatically every day and restored my new Macbook from that time machine with zero issues. I think I got lucky and timed the Apple software release cycle just right.

One of my strategies is to never just have one backup, so I use Backblaze for my "real" backups offsite; Time Machine is just EZ and convenient when it Just Works™. If I lose data I can recover it within minutes, usually. Luckily APFS has this feature now, so I might just ditch Time Machine altogether for a bit.

I'm going to try one final solution by upgrading my Freenas 11.4 machine to TrueNAS 12.

 

[Xerxes004]

...

I'm going to try one final solution by upgrading my Freenas 11.4 machine to TrueNAS 12.

Didn't work. Goodbye, old Time Machine!

 

[harriska2]

I had to switch to CCC so I could get regularly scheduled backups once a day on my external spinner. My work arounds for TM weren’t working on Monterey.

 

[brilliantthings]

I thought I’d add to this too. I recently bought a Synology DS220j and my MBA M1 could not TimeMachine backup to it at all. I instead starting using Carbon Copy Cloner again, but found that my MBA would restart in the middle of CCC backups. Mike from CCC gave incredible tech support explaining that in Monterey there is a critical memory leak when using SMB. He showed me how to change my CCC settings to AFP and he made some adjustments to the new version (then beta) of CCC. Now everything is working again.

I just thought I’d share here because there are such fundamental problems with Monterey that don’t seem to get much air time. It rendered Synology unusable.

I should also mention that Synology support had no idea what was going on when I asked them.

 

[dialekt]

I thought I’d add to this too. I recently bought a Synology DS220j and my MBA M1 could not TimeMachine backup to it at all. I instead starting using Carbon Copy Cloner again, but found that my MBA would restart in the middle of CCC backups. Mike from CCC gave incredible tech support explaining that in Monterey there is a critical memory leak when using SMB. He showed me how to change my CCC settings to AFP and he made some adjustments to the new version (then beta) of CCC. Now everything is working again.

I just thought I’d share here because there are such fundamental problems with Monterey that don’t seem to get much air time. It rendered Synology unusable.

I should also mention that Synology support had no idea what was going on when I asked them.

Interesting that you mention mike. I recently found a post about my EXACT problems. Like everything precisely describing the issues I was having -

https://bombich.com/kb/ccc6/macos-monterey-known-issues

i tried reaching out and the last that was said that 12.3 was coming out (which I’ve updated to) - I have not tested SMB3 with this version of MacOS. Has anyone tried to get it working with this? Also what were your technical settings that got everything working on your NAS

 

[brilliantthings]

I’ll get back to you with the settings but basically it was to allow the NAS to use AFP and to option click on the NAS selected in CCC and change from SMB to AFP. Must be latest version of CCC.

 

[emura]

I thought I’d add to this too. I recently bought a Synology DS220j and my MBA M1 could not TimeMachine backup to it at all. I instead starting using Carbon Copy Cloner again, but found that my MBA would restart in the middle of CCC backups. Mike from CCC gave incredible tech support explaining that in Monterey there is a critical memory leak when using SMB. He showed me how to change my CCC settings to AFP and he made some adjustments to the new version (then beta) of CCC. Now everything is working again.

I just thought I’d share here because there are such fundamental problems with Monterey that don’t seem to get much air time. It rendered Synology unusable.

I should also mention that Synology support had no idea what was going on when I asked them.

"I just thought I’d share here because there are such fundamental problems with Monterey that don’t seem to get much air time. It rendered Synology unusable.

I should also mention that Synology support had no idea what was going on when I asked them."

This. It's depressing to have to depend on AFP - which is on life support - to keep using my Synology-based NAS boxes (DS1621xs+ 6 bay and DS1821+ 8 bay) with my M1 Monterey box.

For those lucky enough to only experience minor annoyances - this goes way beyond authentication and access problems for a bunch of us - I'm talking about full blown system lockups or instability to the point where other seemingly unrelated subsystems get confused ("your account is being used by another Mac" style warnings on my iPhone and other iCloud devices).

Anyone have the radarID(s) tracking this/these problems?

https://www.reddit.com/r/Arqbackup/comments/qmqbt5

(Problems can be reproduced without ARQ. This is just the context that hits me the hardest with my NAS vs. DAS boxes.)

 

[brilliantthings]

"I just thought I’d share here because there are such fundamental problems with Monterey that don’t seem to get much air time. It rendered Synology unusable.

I should also mention that Synology support had no idea what was going on when I asked them."

This. It's depressing to have to depend on AFP - which is on life support - to keep using my Synology-based NAS boxes (DS1621xs+ 6 bay and DS1821+ 8 bay) with my M1 Monterey box.

For those lucky enough to only experience minor annoyances - this goes way beyond authentication and access problems for a bunch of us - I'm talking about full blown system lockups or instability to the point where other seemingly unrelated subsystems get confused ("your account is being used by another Mac" style warnings on my iPhone and other iCloud devices).

Anyone have the radarID(s) tracking this/these problems?

https://www.reddit.com/r/Arqbackup/comments/qmqbt5

(Problems can be reproduced without ARQ. This is just the context that hits me the hardest with my NAS vs. DAS boxes.)

I haven't had exactly that problem but I feel your pain.

 

[madonnaragu]

Same issue here. Nothing works.

 

[ortwingentz]

You might want to check the SMB ACL: https://apple.stackexchange.com/a/441234/1931

 

[dialekt]

You might want to check the SMB ACL: https://apple.stackexchange.com/a/441234/1931

First off has anyone tried 12.3 & higher Monterrey? I was able to successfully finally use my NAS after a 6 month nightmare. I didn't realize 12.4 was released but I'm terrified of what it may or may not break. Using QNAP TVS series NAS. 12.3.1 has been working well for me so far. But I always love any sort of improvements with updates but it can be risky. For the above I haven't needed to do any of that once I updated to Mac OS 12.3 & higher

 

[emura]

I wish it were as trivial or simple as an ACL problem. To the point about trying 12.3 or higher, I still need to carve out some time to try to reproduce this with something a bit more simple and which takes less time. Figure it would involve a lot of parallel metadata load plus a few streams moving big data.