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

BIG SUR problems with SMB

ElPutoGrande said:
On Windows machine go to Turn Windows features on or off.

check-->SMB1.0/CIFS File Sharing Support. check-->SMB1.0/CIFS Client

Works on all our Bigsure machines so far.


This has been happening to a lot of our clients who foolishly upgraded to Bigsur toooooooooooo early.
Click to expand...

​

I don't recommend this.​


SMB 1.0 cannot be encrypted and is a known vector for ransomware attacks.

I'd recommend telling people to hold off until 11.3 or rolling people back to a version that supports SMB3 and Encryption.

Never trade your safety for convenience, then when your safety is threatened it all becomes terribly inconvenient.

I'm more hopeful that Apple realizes what a BIG FRIGGIN' DEAL this is for people in hybrid environments and releases a patch that takes care of this, versus waiting ANOTHER 2 months for a dot revision. Why this wasn't corrected in 11.2 is beyond me, but I guess quality control is too much to ask sometimes.

But don't revert to using unsafe methods of transfer "just because it seems to work". That's unsafe at best and terrible IT at worst.
 
svenmany said:
Sounds like your issue deserves a new thread. It seem unrelated to what this thread is about. This thread is only about the inability to list available shares offered by a Windows computer.
Click to expand...

Then I think the title needs to be changed since it isn't specific.

I found this forum posting because I'm having issues with SMB across the board on Big Sur, both linux and windows.

The title is just SMB & Big Sur, and I think it's a larger issues with SMB, not just how it interacts with Windows machines.
 
  • Like
Reactions: Slowdown_first
jyhash said:
Then I think the title needs to be changed since it isn't specific.

I found this forum posting because I'm having issues with SMB across the board on Big Sur, both linux and windows.

The title is just SMB & Big Sur, and I think it's a larger issues with SMB, not just how it interacts with Windows machines.
Click to expand...

Yeah, the title should change to be more specific. Titles are often vague and people count on the opening post to specify the topic thoroughly.

The issue being discussed has been identified by Apple as a bug and they say a fix will be coming soon. Once that happens, active participation in this thread could dwindle. Because of that, the other issue mentioned could get better visibility in a new thread.
 
I tried it. Nothing changed. I still got troubles when using SMB to connect the Synology NAS shares. SMB 1 ist disabled in the Synology. AFP works fine. TimeMachine also works with AFP.
 
Looks like I found a workaround; at least it works for me: On a whim, I tried the old, supposedly deprecated, cifs://x.x.x.x instead of smb://x.x.x.x

This worked immediately, with what seems like full access to Server 2012 R2 shares, as before. I will hopefully return here with news if I find anything not working.

No other changes of any kind with Mac or target server/firewall/LAN. Simply replaced one protocol name with the other.
 
Last edited:
Peter Jay said:
Looks like I found a workaround; at least it works for me: On a whim, I tried the old, supposedly deprecated, cifs://x.x.x.x instead of smb://x.x.x.x

This worked immediately, with what seems like full access to Server 2012 R2 shares, as before. I will hopefully return here with news if I find anything not working.

No other changes of any kind with Mac or target server/firewall/LAN. Simply replaced one protocol name with the other.
Click to expand...

Did you make that change recommended a bit earlier to enable CIFS and SMB1 on the windows machine? I don't think my windows machine supports CIFS - at least it's not offered during protocol negotiation.
 
I didn't change anything on the Windows Server side to make that happen today. CIFS must have either been enabled by default on that server, or enabled previously by me, but as I recall, it's something like the "generic" version of SMB1. And on an older Intel Mac, not too long ago, my entering cifs://x.x.x.x was automatically changed to smb:// when I tried to access that same Windows server using that. I don't have time right now to check how the server is set up, but if I remember, I'll check it later. In this case, however, cifs:// did not magically change to something else on the Big Sur Mac.
 
  • Like
Reactions: svenmany
Follow-up. Yes, SMB1/CIFS file sharing support had already been enabled on the Windows server. I now see it's considered a vulnerabilty, but I suppose I'll leave it there until there's a fix for Big Sur. We do have good border security and active antivirus (etc.) on the server and client computers, so it's a chance I'm willing to take.
 
Peter Jay said:
Follow-up. Yes, SMB1/CIFS file sharing support had already been enabled on the Windows server. I now see it's considered a vulnerabilty, but I suppose I'll leave it there until there's a fix for Big Sur. We do have good border security and active antivirus (etc.) on the server and client computers, so it's a chance I'm willing to take.
Click to expand...
Thanks for checking.
 
Does still not work on 11.3 beta - bit surprised it still doesn´t work, but have rapported it back. SMB1 is legacy and a no go - at least if security is something that matters
 
cifs://x.x.x.x is working for me, with the full share list. Though it seems slower than SMB. But, at least, it works. Good find!
 
don´t think any will use cifs in enterprise - and yes very slow. I will do new log files and send to apple as they requested today - incl. a recording from my screen
 
Update - from apple
I was mistaken that the fix was included in this beta release, Product Engineering team informed me that the testable fix will be in the next beta when it is available. I will let you know once the fix will be addressed in the next beta, then we can test it.
 
rossonero said:
Update - from apple
I was mistaken that the fix was included in this beta release, Product Engineering team informed me that the testable fix will be in the next beta when it is available. I will let you know once the fix will be addressed in the next beta, then we can test it.
Click to expand...
I can confirm that the beta that just came out does not fix the problem. 11.3 Beta (20E5172i)
 
try this in terminal

  • Type sudo /usr/libexec/configureLocalKDC and press Return.
 
karos said:
try this in terminal

  • Type sudo /usr/libexec/configureLocalKDC and press Return.
Click to expand...

What does this do exactly and how do you undo it if it doesn't help?

Kerberos seems to be unrelated to the problem since the authentication is working fine; the Windows server does return the list of shares. It's just that the Mac fails to display them.
 
moetiker said:
I can confirm that the beta that just came out does not fix the problem. 11.3 Beta (20E5172i)
Click to expand...
Big News! 11.3 Beta (20E5186d) Beta 2 looks good in my Case all SMB drives get listed... Well DONE... thanks for finally fixing the SMB Bug
 
moetiker said:
Big News! 11.3 Beta (20E5186d) Beta 2 looks good in my Case all SMB drives get listed... Well DONE... thanks for finally fixing the SMB Bug
Click to expand...
Is that SMB 3.0? I can't use NFS with my Xiaomi Mi Box S 4K because KODI is not root and I can't modify plist because f restrictions in BigSur.

Not related but this is what I need to edit in plist for NFS to work. Do you think it's a good idea to ask DEVS to do this?

1. To allow regular (non-root) users to connect to your NFS shared folders, you'll need to edit the "/System/Library/LaunchDaemons/com.apple.nfsd.plist" file. Open it and add the option "-N" to the startup parameters as follows:

<array>
<string>/sbin/nfsd</string>
<string>-N</string>
</array>
 
moetiker said:
Big News! 11.3 Beta (20E5186d) Beta 2 looks good in my Case all SMB drives get listed... Well DONE... thanks for finally fixing the SMB Bug
Click to expand...
There are still problems transferring multiple files from or to a Synology DiskStation using SMB3 or 2. AFP still works. There are no problems with Windows 10 or Debian Buster. Perhaps the bug is not finally fixed?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back