Yes, we are talking about SMB not NFS... so it has nothing to do with this topic....
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
BIG SUR problems with SMB
- Thread starter lwilliams
- Start date
- Sort by reaction score
The bug is described in the opening post. That seems to be fixed. You are experiencing a different bug.
Well, I went ahead with the .2 beta. Now SMB works properly.
Hopefully, I wont have any "beta" issues. But this is, so far, much better.
Hopefully, I wont have any "beta" issues. But this is, so far, much better.
Ran into the same issue. Searched for a fix and never found one. This happens with "upgrades" to Big Sur. The fix, go to your keychain access and delete old references to the share point and reconnect. Worked perfectly for me,
Hey all,
here is the same SOLUTION it was "keyChain" or in German "Schlüsselbund", just delete the entries for the shares and add new passwords for the connections.
It was strange for me that I could connect from the terminal but not from the finder "connect to server".
Works now!
But annoying upgrading solution: I really want to shift slowly to Linux!
This whole Apple empire is so outdated on all levels.
here is the same SOLUTION it was "keyChain" or in German "Schlüsselbund", just delete the entries for the shares and add new passwords for the connections.
It was strange for me that I could connect from the terminal but not from the finder "connect to server".
Works now!
But annoying upgrading solution: I really want to shift slowly to Linux!
This whole Apple empire is so outdated on all levels.
Keychain issues relate to authentication problems (I think). That is definitely not the issue described in the opening post since Apple has confirmed that all the shares are being successfully returned (authentication satisfied), but the Mac hangs up presenting them for some reason. Apple has confirmed it's their bug and fixed it in a beta.
I'd be interested to hear if the people reporting keychain based solutions were really experiencing the same problem that this thread is about - all shares are accessible if you know the share name. The only problem was listing the available shares. Was that the problem that the "keychain" solution was addressing?
I'd be interested to hear if the people reporting keychain based solutions were really experiencing the same problem that this thread is about - all shares are accessible if you know the share name. The only problem was listing the available shares. Was that the problem that the "keychain" solution was addressing?
Thank you for clarification and bringing us back to the starting point.
Keychain was a different issue about not being able to use established smb connection via "connect to".
The listing of shares, after being connected, worked for me, also in older version
But the "search" button never worked - also not in older versions - as it works in Windows where you can see available shares. I always assumed it is a samba problem where you must name a "leader machine". Sometimes it worked with DHCP but not with dedicated IP addresses.
so back to the start: yes, after being connected I see the shares listed -> macPro(End 2013), BigSur 11.2.2
Keychain was a different issue about not being able to use established smb connection via "connect to".
The listing of shares, after being connected, worked for me, also in older version
But the "search" button never worked - also not in older versions - as it works in Windows where you can see available shares. I always assumed it is a samba problem where you must name a "leader machine". Sometimes it worked with DHCP but not with dedicated IP addresses.
so back to the start: yes, after being connected I see the shares listed -> macPro(End 2013), BigSur 11.2.2
I had this exact issue and had not found this thread. This may be different for you, but the machine this occurred on gets used simply as a Synology NAS bridge machine with 2x NAS server connected via 10GbE to TB3 adapter respectively. The NAS units can do 1gigabyte/sec easily. Its stupid fast. After the update, same issue - could see no shares. I was using 802.1q VLAN configured through a virtual interface to use a special VLAN. Thats really the only system level networking related change. So I blew the machine away and started from scratch and sure enough not putting it on the VLAN fixed it post-update which would normally break it. So somewhere in there, I also discovered that creating a new user resolved the issue. This makes sense with the keychain removal instruction above but I dont know how that would affect it. Just adding my 2c.
I have another issue though, which is that I transfer large folders (400gb-2tb) between the servers, again via 10GbE and the copies have been erroring out with io errors -36 and -8084. This is with both shares mounted and then a drag and drop through the Finder. If I first copy the folder to the desktop of the mac its fine. If i use AFP its fine on the drag and drop between them. Its ONLY when using SMB does it fail anywhere between 10 and 100gb or so. Filed it on bugreport.apple.com but feels like it could use some more juice. Any suggestions on what to do next to get it some attention while they are working on SMB?
I have another issue though, which is that I transfer large folders (400gb-2tb) between the servers, again via 10GbE and the copies have been erroring out with io errors -36 and -8084. This is with both shares mounted and then a drag and drop through the Finder. If I first copy the folder to the desktop of the mac its fine. If i use AFP its fine on the drag and drop between them. Its ONLY when using SMB does it fail anywhere between 10 and 100gb or so. Filed it on bugreport.apple.com but feels like it could use some more juice. Any suggestions on what to do next to get it some attention while they are working on SMB?
Thanks for your help on this issue @rossonero. Much appreciated.
Is the SMB issue still resolved as of Beta #7? EDIT: I installed 11.3 beta #7 and it is indeed fixed. I can browse my EMC/Isilon SMB server's shares again.
Can you share your AppleCare case number so I can reference it, please? I want to follow up with my Apple Enterprise rep on this.
Last edited:
I just wanted to add something for people meandering through this forum looking for SMB solution. I have a WD MyCloud Home NAS drive. There is a public folder, which I've always been able to access using
without any issue. Upgraded to BigSur 11.3 last night and access to the public folder no longer worked. Two hours of random internet searching and found the post here that fixed it. Simply changing to cifs as mentioned above worked instantly.
I hope this helps someone out, somewhere and saves a bit of the hassle I've had this morning.
EDIT: As someone else has pointed out, removing the saved passwords from Keychain Access does the trick. As a small aside, there's a bug in keychain access that means if you search for the entries in question, you can't delete them. Just scroll until you find them, select and delete works.
smb://guest:guest@MyCloud-xxxxxx/Publicwithout any issue. Upgraded to BigSur 11.3 last night and access to the public folder no longer worked. Two hours of random internet searching and found the post here that fixed it. Simply changing to cifs as mentioned above worked instantly.
cifs://guest:guest@MyCloud-xxxxxx/PublicI hope this helps someone out, somewhere and saves a bit of the hassle I've had this morning.
EDIT: As someone else has pointed out, removing the saved passwords from Keychain Access does the trick. As a small aside, there's a bug in keychain access that means if you search for the entries in question, you can't delete them. Just scroll until you find them, select and delete works.
Last edited:
I can confirm, I've just installed stable 11.3 and the issue is fixed, I can access my SMB folders again
Yup, I'm running macOS 11.3 (20E232) - SMB share browsing is working fine here.I can confirm, I've just installed stable 11.3 and the issue is fixed, I can access my SMB folders again
yes we hope this means that somebody took a wrench to the codebase and tightened things up.
Maybe this is slightly off-topic, but what is "better" than SMB for Mac users?
At work I'm basically the only with a Mac. Everyone else is running PC with Win 10.
Everyone, including me, saves everything on a drive that IT is doing backup of. We connect through SMB.
This works flawlessly on the PCs.
However, on my Mac I often have problems with disconnects after being away from my computer a while (even though I've set my iMac to never sleep), it sometimes don't connect when I boot my computer, and sometimes when I try to connect it takes several minutes.
I assume IT don't want to do anything about it since it works perfect for >99% of all employees. But I can still beg and see what happens. But what should I ask them? Is AFP or NFS better? What do IT do at companies where more people have Macs?
At work I'm basically the only with a Mac. Everyone else is running PC with Win 10.
Everyone, including me, saves everything on a drive that IT is doing backup of. We connect through SMB.
This works flawlessly on the PCs.
However, on my Mac I often have problems with disconnects after being away from my computer a while (even though I've set my iMac to never sleep), it sometimes don't connect when I boot my computer, and sometimes when I try to connect it takes several minutes.
I assume IT don't want to do anything about it since it works perfect for >99% of all employees. But I can still beg and see what happens. But what should I ask them? Is AFP or NFS better? What do IT do at companies where more people have Macs?
11.3 did not fix the issue for me.
I connecting to an android tablet running the LAN Drive SMB server, which worked until the Big Sur update. I've been watching this thread and have tried all of the potential fixes mentioned here.
The mac is able to authenticate, but then shows errors
While the error dialog is shown in the mac the tablet's LAN Server interface it shows that the mac is logged in,
but then it disconnects after the error dialog is closed. I also verified that it is authenticating ok by looking through the system logs (so solutions regarding keychain and probably kerberos are not relevant -- though I tried them regardless.
I connecting to an android tablet running the LAN Drive SMB server, which worked until the Big Sur update. I've been watching this thread and have tried all of the potential fixes mentioned here.
The mac is able to authenticate, but then shows errors
Code:
"There was a problem connecting to the server 192.168.1.69"
An error of type -5014 has occurred. (-5014).While the error dialog is shown in the mac the tablet's LAN Server interface it shows that the mac is logged in,
but then it disconnects after the error dialog is closed. I also verified that it is authenticating ok by looking through the system logs (so solutions regarding keychain and probably kerberos are not relevant -- though I tried them regardless.
Jumping in on this thread..
I have a Qnap NAS that can support AFP/NFS/SMB. SMB is the default and recommended. My iMac 10.15 connected via TB3 to 10GigE using SMB and it would disconnect when the network got saturated.. Like when rendering or Converting 444 to DPX, have 40 zip folders with 300gb unzipping.. Anything heavy, network NAS would totally disappear via SMB....
So I tested the same TB3 to 10GigE on my M1 MacBook Pro via SMB, and under heavy load rendering, anything.... Not one disconnect via SMB. M1 MacBook Pro running 11.2.3 using thunderbolt 3 to 10gigE had no issues...
So I upgraded my iMac to 11.2.3 BigSur because I thought Big Sur would fix the SMB problem, but it did not. The SAME EXACT issue, everything disconnected on heavy load..
I switched over everything to AFP as my solution and M1 MacBook Pro and iMac seem to stay connected even though the M1 had no problems with SMB.
I get almost 150mb/s to 200mb/s faster burst performance with the M1 via SMB on TB3 to 10GigE versus AFP. I think there is something a little more complicated with hardware fighting for resources... As my M1 CPU seems unfazed by SMB while my intel iMac is always having more issues. It seems more complicated than just fixing bugs with Apple, but more about allocating resources to deal with heavy network traffic..
I have a Qnap NAS that can support AFP/NFS/SMB. SMB is the default and recommended. My iMac 10.15 connected via TB3 to 10GigE using SMB and it would disconnect when the network got saturated.. Like when rendering or Converting 444 to DPX, have 40 zip folders with 300gb unzipping.. Anything heavy, network NAS would totally disappear via SMB....
So I tested the same TB3 to 10GigE on my M1 MacBook Pro via SMB, and under heavy load rendering, anything.... Not one disconnect via SMB. M1 MacBook Pro running 11.2.3 using thunderbolt 3 to 10gigE had no issues...
So I upgraded my iMac to 11.2.3 BigSur because I thought Big Sur would fix the SMB problem, but it did not. The SAME EXACT issue, everything disconnected on heavy load..
I switched over everything to AFP as my solution and M1 MacBook Pro and iMac seem to stay connected even though the M1 had no problems with SMB.
I get almost 150mb/s to 200mb/s faster burst performance with the M1 via SMB on TB3 to 10GigE versus AFP. I think there is something a little more complicated with hardware fighting for resources... As my M1 CPU seems unfazed by SMB while my intel iMac is always having more issues. It seems more complicated than just fixing bugs with Apple, but more about allocating resources to deal with heavy network traffic..
I have noticed some differences that I can only loosely describe two different CPU platforms. My issues run a little bit in reverse where on an Intel system SMB was fine on huge file copies across 10 gig ethernet (synology to Synology at about 1GB/sec) while on m1 it would error out mid way. Using AFP solves the problem and the speed doesn’t really suffer. I have not tested this but my hunch is that it has to do w how each protocol handles DS_Store files that are “in use” somehow as it got stuck once on AFP and cited that as the reason which had me think SMB simply doesn’t know how to report that and just dies.
Did you disable DS_Store? I was going to do that next, but I am in the middle of job and I didn't want to mess with anything. But supposedly any network guys dealing with MacOS and SMB, that is the first thing they do.
defaults write com.apple.desktopservices DSDontWriteNetworkStores trueit sounds like it cures the mid transfer drops..
Thank you. Yes I was going to do that next. About your last sentence, do you know of people it helped?
Qnap Forum about SMB
This is specific to Qnap, but Synology has similar issues.. It is a whole forum about SMB not working as intended with MacOS. Seems the first thing people do is remove DS_Store
This is specific to Qnap, but Synology has similar issues.. It is a whole forum about SMB not working as intended with MacOS. Seems the first thing people do is remove DS_Store
Hi everyone,
It looks like this Apple SMB "bug fix" of 11.3 broke my SMB finder access and the SMB/NAS drive access for anyone using Big Sur 11.3 with a FritzBox router.
If anyone who was in touch with the Apple engineers could help us out to fix this, that would be greatly appreciated! Everything was working fine for AVM FritzBox users before the 11.3 SMB bug "fix", which I understand helped you guys but broke something for our SMB feature as a result...
See the following links
discussions.apple.com
It looks like this Apple SMB "bug fix" of 11.3 broke my SMB finder access and the SMB/NAS drive access for anyone using Big Sur 11.3 with a FritzBox router.
If anyone who was in touch with the Apple engineers could help us out to fix this, that would be greatly appreciated! Everything was working fine for AVM FritzBox users before the 11.3 SMB bug "fix", which I understand helped you guys but broke something for our SMB feature as a result...
See the following links
problem but with the NAS Fritz BOX update… - Apple Community
Last edited by a moderator: