After upgrading to Big Sur 11.3 i cannot connect to my SMB Public Share on my NAS anymore

Connecting via cifs solved the problem for me. But I also found instructions for forcing the system to use SMB2 vs SMB3-- this also appears to have solved the problem introduced in 11.3. Here are the instructions for that workaround:

Enter the following in Terminal:

echo "[default]" | sudo tee -a /etc/nsmb.conf

echo "protocol_vers_map=2" | sudo tee -a /etc/nsmb.conf

Source (in german): https://stadt-bremerhaven.de/macos-big-sur-probleme-mit-smb-und-der-avm-fritzbox-beheben/)

I'm having the same issue.

When I connect with smb://mycloud-vvc5ht/Public it won't allow guest access it seems to reject the user. But connecting via cifs://mycloud-vvc5ht/Public it works fine.

However my wife's computer running 11.2.3 connects fine.

Here's her result from smbutil statshares -a

Jennifer-Mullens-MacBook:~ Jarn$ smbutil statshares -a

=============================

SHARE             ATTRIBUTE TYPE        VALUE

=============================

Public             

               SERVER_NAME          MYCLOUD-VVC5HT

               USER_ID            501

               SMB_NEGOTIATE         SMBV_NEG_SMB1_ENABLED

               SMB_NEGOTIATE         SMBV_NEG_SMB2_ENABLED

               SMB_NEGOTIATE         SMBV_NEG_SMB3_ENABLED

               SMB_VERSION          SMB_3.02

               SMB_SHARE_TYPE        DISK

               SIGNING_SUPPORTED       TRUE

               EXTENDED_SECURITY_SUPPORTED  TRUE

               LARGE_FILE_SUPPORTED     TRUE

               FILE_IDS_SUPPORTED      TRUE

               DFS_SUPPORTED         TRUE

               FILE_LEASING_SUPPORTED    TRUE

               MULTI_CREDIT_SUPPORTED    TRUE

--------------------------------------------------------------------------------------------------

and this is my result ising CIFS

=============================

SHARE             ATTRIBUTE TYPE        VALUE

=============================

Public             

               SERVER_NAME          mycloud-vvc5ht

               USER_ID            501

               SMB_NEGOTIATE         SMBV_NEG_SMB1_ENABLED

               SMB_VERSION          SMB_1

               SMB_SHARE_TYPE        UNKNOWN

               EXTENDED_SECURITY_SUPPORTED  TRUE

               LARGE_FILE_SUPPORTED     TRUE

--------------------------------------------------------------------------------------------------

My issue is that CIFS is SMBv1 and I'd prefer using SMBv2/3 the transfer rates are much faster.

Hey Mini,

I did the same thing and used CIFS to connect but I don't consider this as being a solution. CIFS is SMB version 1. SMB version 2 and 3 don't work.

You'll find that your transfer rates have slowed by half using SMBv1 instead SMBv2. CIFS/SMB is fine for small files but not for today's file sizes.

SMBv2 was designed to solve all the faults with SMB/CIFS and it was released in 2006! Apple can't properly implement a protocol that's been in use for 15 years.

That's not the worst. SMBv3 was released in 2012 to fix issues issues with v2 and Apple can't get that right either.

At this rate Apple will likely finally get a v2 implementation that actually works just after v4 will be released.

Thank you for letting us know.

To continue troubleshooting, we recommend reaching out to Apple Support directly. You can reach out to Apple Support by following the link we've provided below.

Get Support

Best wishes!

Hi Mini_Solaris,

Thank you for posting in the Apple Support Communities. It sounds like you're having some trouble sharing using SMB since upgrading to Big Sur, correct? If so, we would love to help see if we can get the issue resolved for you. Let's go ahead and follow the troubleshooting steps we've linked for you below.

Share Mac files with Windows users

Adjust SMB browsing behavior in macOS

You may need to disable, then try again.

Set the protocol for file sharing on Mac

If your Mac can’t connect to another computer

Please let us know if you have any additional questions. We're always happy to help.

Cheers!

Thanks so much for your solution. I was having the same problem and it worked for me.