SMB and Big Sur

After updating to Big Sur, I'm no longer able to use SMB to access a windows server. Is there a fix for this?
I have a similar problem, but I can get a limited connection to my windows server 2012. I can access the server and copy files from it, but when I try to copy files to the server, it hangs and then eventually disconnects from the server. Once disconnected, I lose ability to do anything on the network, Internet access is gone, even though the network still says it is connected. I have to shut down and restart to get internet access back.
Does not seem to care if transferring from the server, only when trying to write to the server.

Still looking for a solution.
smbfs support in macOS has gotten worse and worse with every new release.

For years, I couldn't reconnect a share using the recent servers menu while Mail was the frontmost app. They fixed it for a brief time, then broke it altogether since 10.15.2, which forced me to use the Cmd K route instead.

With Big Sur, mounting a share via cmd k still works for me, but it's become much slower than before. Also, using git on a mounted share is quite dangerous when there are many pending changes: git blocks (probably because the underlying smbfs blocks) and macOS panics when trying to shutdown/reboot the machine.

I've always reported these bugs to Apple via Feedback Assistant, but apparently no one cares. Or perhaps I'm the only one who sends them bug reports about samba and they're waiting for someone else to submit reports too, before acting on them... try submitting a feedback report :-)
I have exactly the same problem as dminn. Anyone have a solution?

I have the same problem too. Uploading data can break in the middle of process. My mapped drives (smb shares) disconnect from the server (2012 r2) after 2 hours mysteriously.

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 this I am worried that nobody is taking this seriously or it's a nasty edge case that isn't even on the dev radar. I hate to say it but I'm glad it's happening to/with Bombich CCC so maybe it might get some attention.

SMB and Big Sur
 
 
Q