smb big sur

11,037 results found

Post not yet marked as solved
5 Replies
2.0k Views
After updating to Big Sur, I'm no longer able to use SMB to access a windows server. Is there a fix for this?
Posted
by
Post not yet marked as solved
20 Replies
11k Views
Has anyone tested SMB based time machine backups in any of the various revisions of Big Sur? Direct change from Catalina to BS result in permissions issues generated by time machine. If you force the folders to inherit permissions, time machine will complain about missing features. Either way, time machine is completely non-functional. I've reported feedback and seen that others have the same issue, but no one I know has worked around it yet. Samba 4.11.6 from ubuntu 20.04 standard options in smb.conf like fruit:aapl = yes and fruit:timemachine = yes, as well as the proper vfs etc. It is configured properly, worked great in Catalina and all previous revisions.
Posted
by
Post not yet marked as solved
1 Replies
2.4k Views
Has anyone else been having problems with accessing Mac SMB shares with lots of subfolders from Windows 10 (Fast Track Developer Release) on Big Sur Beta 11.x. The problem appears to relate either to the number of folders/files in the share - it seems to occur with large shared folders only. I get a situation where the Mac server does not appear in Network in File Explorer on Windows, but I can connect to the server using servername in the File Explorer address bar and get an immediate connection and can browse contents of small shared folder trees. However, with large folder trees, after a few seconds the shares become inaccessible and I can no longer browse or access their contents. The same things happens if I create an explicit mapped drive connection using net.exe in command or powershell. I can see the server and shares using NET VIEW SERVERNAME and can map a drive using NET USE Drive: SERVERNAMESHARENAME and the drive appears in File Explorer under This PC, but if I try to na
Posted
by
Post not yet marked as solved
0 Replies
358 Views
Big Sur version 11.1 seems to have problems connecting to a server via VPN. Im using the Connect to Server option in the Go menu to connect but it just refuses to connect. I've seen multiple threads about this topic and found the terminal command sudo kextload /System/Library/Extensions/smbfs.kext This did not fix the issue.
Post not yet marked as solved
2 Replies
1.1k Views
Hello, Have issues with connecting workplace cloud, based on linux with SMB version 3.1.1. Devices on MacOS 10.15.4 and 11.0 can't connect through Finder -> Go -> Connect to server (Cmd+K) with error: URLs with the type “smb:” are not supported.
Posted
by
Post not yet marked as solved
0 Replies
656 Views
After upgrading to Big Suf, i am not able to connect to my company's shared drive. It used to work by connecting to smb server...sorry I am not a tech person but what i used to do is to go to Finder -> cmd+K -> smb:(the server name). It used to work but not now after upgrading to Big Suf. Any way i can fix that? thanks.
Posted
by
Post not yet marked as solved
4 Replies
1.5k Views
I use Samba 4.11.6 with ubuntu 20.04 & Mac os Big Sur 11.0.1. I connected my macbook and server (intel nuc) via thunderbolt 3. It works fast, speeds around 800MB/s. I can easily transfer multiple files or 1 large file, but when I try to transfer any web project with a lot of files and subfolders, the finder freezes and only hard reset helps. I tried transferring files via finder and via cp -av ..., the result is the same - the terminal freezes and control + c does not work. Several files with a total size of a couple of KB are transferred and nothing else. The problem is similar to this jamf.com/jamf-nation/discussions/26464/macos-high-sierra-10-13-2-finder-issues-when-copying-files-in-mounted-shares. I tried changing nsmb.conf to this [default] signing_required=no dir_cache_off=yes But it didn't help at all :( When I don't connect via thunderbolt 3, but when i connected via wifi, I can transfer my project to the smb folder.
Posted
by
Post marked as solved
47 Replies
13k Views
After the upgrade from Beta 6 to Beta 7 I am not able to connect to any smb-shares any more. I tried it with a Windows Server, Synology DriveStation and a Debian implementation. I'm directly getting the message Error with connection.
Posted
by
Post not yet marked as solved
8 Replies
The problem persists on Monterey 12.2.1, which makes SMB connection unavailable between Big sur & Monterey
Post not yet marked as solved
47 Replies
Terminal cmd line also does not work to mount an SMB share unfortunately. Big Sur Dev Beta 6.
Post not yet marked as solved
47 Replies
Even i too had the same issue with my SMB CIFS share running in my raspberry pi. I had added my SMB share as part of user login process. and also having a file share discoverable by my mac time machine for backup. After Mac Big sur update it fails saying cannot connect. But i had a different workaround, on time machine if i initiate a backup then trying to connect to SMB works for me. but again this goes away after restart. is the Mac Big sure team working on to fix this issue? i had sent a feed back too.
Post not yet marked as solved
12 Replies
The SMB share works for a few hours and then after that, you can see the shared Mac but none of the folders show up. If I toggle the File Sharing off and on, the shares come back but then a few hours later, they stop working again. Does anyone have a fix for this with Big Sur? Everything worked fine in Catalina. This is from a clean install of Big Sur too.
Post not yet marked as solved
47 Replies
The commands are not working for me. I have 2 other MACS that are using ElCapitan, and Catalina, and they both are able to connect to SMB Synology share CDMSNAS but the Macbook Air with Big Sur 11.1 does not see CDMSNAS on the network, but if I do the Go to Server and enter the smb://IP address, it sees it fine. When is this going to be fixed. I am very disappointed in this release so far, entirely too many problems.
Post not yet marked as solved
5 Replies
I've had several system freezes (goes from sluggish to frozen within just a minute or two and panics) related to copying large files or large numbers of smaller files to and from SMB-mounted shares. It doesn't seem to matter whether I CMD-K or add them to automount(my preference). I ran with this configuration with multiple SMB share mounts on Intel and pre-Big Sur versions without this problem for the better part of 10 years. It's definitely new. Unfortunately I don't have another Big Sur-capable system to rule out either M1 or Big Sur. I have an M1 mini on Big Sur and my watchdog panics/crashes with smbfs.kext are perfectly described on the bottom of this page: https://bombich.com/kb/ccc6/macos-big-sur-known-issues On that page see: Apple's SMB filesystem client causes system stalls, leads to kernel panics and mouse-over the watchdog panic. Based on how few other search results I get about th