5 months after the May update, invested many fruitless hours with first tier Sonos techs, finally elevated to a level of expertise resulting in renewed access to my music library( Mac laptop) and playlists in their entirety. Happy finally regaining that which never should have been made inaccessible. Seemingly avoidable debacle.

Seems to me that you didn’t perhaps understand the issue. Way back in 2019 Microsoft and others were suggesting that no one use the SMBv1 ‘sharing’ protocol, as security vulnerabilities had been discovered - the Sonos Desktop Apps catered for bypassing SMBv1 by using the HTTP protocol instead and that was introduced around the time of the S1/S2 split in late 2020.

The vulnerabilities of SMBv1 were widely discussed in this community and elsewhere online and many users (myself included) persisted with SMBv1 for a while, relying on the security of the local network - but it wasn’t ideal. A lot went for HTTP sharing and I eventually upgraded my NAS to support SMBv2 and v3.

HTTP was eventually found to be vulnerable too, so in the new Sonos App, launched in May this year, support was dropped for HTTP (and of course there was no support for SMBv1 either). That meant all of us users sharing local libraries needed to switch the library sharing protocol to use SMBv2, or higher.

There are several guides in this community and in the Sonos Support pages of what needs to be done to setup such a share. Sonos even warned us about these things prior to the May App update. See attached.

There’s only so much hand-holding Sonos can do with the switchover to SMBv2 etc. I’m surprised that people had so much difficulty with this, as a lot of other companies like Microsoft, Apple, Amazon, Google etc. stopped supporting SMBv1 long ago and certainly much earlier than Sonos dropped their support for it. 

Anyhow, the advice to any Sonos user is, if you can’t figure out how to switch your local library share to use SMBv2 or higher, having read the information available online (including the YouTube videos etc.)  then it’s perhaps best to contact Sonos Support. Here is the link to do that…

https://support.sonos.com/s/contact

Here’s some initial links too, if anyone wants to read more on this topic on how to setup an SMBv2 (or higher) share to use with Sonos…

• https://en.community.sonos.com/controllers%2Dand%2Dmusic%2Dservices%2D229131/adding%2Da%2Dwindows%2Dsmb%2Dshare%2Dstep%2Dby%2Dstep%2D6892060
• https://support.sonos.com/en-us/article/add-your-music-library-to-sonos
• https://youtu.be/kjhKhDuvgDY

Well, how patronising is that …… especially the “there’s only so much hand-holding Sonos can do”. Maybe if Sonos hadn’t enforced a new half-baked app on everyone with its plethora of changes whereby it became impossible for anyone (not especially) tech savvy to discern what was happening and why, user wouldn’t need their ‘hands held’ to get their hundreds (thousands?) of pounds of audiotech back working again!?

As I’ve said before Ken, that is not correct, SMB1 is supported but not enabled by default in Windows/MacOS. What Sonos should have done was by all means use SMB2/3 but also keep support for SMB1 for older NAS devices which cannot be upgraded to the new SMB version(s). They could have included a disclaimer and pointed to security issues if the user selects SMB1. But they didn’t. Instead many Sonos users with perfectly working NAS units until now have to buy a new one that supports SMB2/3 (if they can’t upgrade the software), which seems an excessive and unnecessary expense. 

It’s a new App - there is no way that any company would deliberately incorporate a vulnerability in their new software, or hardware. I can’t even find an App in the Apple App Store that supports SMBv1 - most developers have updated their Apps to support SMBv2 or higher and manufacturers like Netgear no longer support their SMBv1 NAS boxes. Also SMBv1 is not available for Windows 11 users.

Windows 11 can still use it, it’s just no longer installed by default as it was in Windows 10 and previous versions.

https://learn.microsoft.com/en-us/windows-server/storage/file-server/troubleshoot/detect-enable-and-disable-smbv1-v2-v3?tabs=server

In the corporate world SMBv1 is clearly a really bad place to keep vital data, at home, for music files, the lack of security matters much less. If you want to steal music, there will be much easier ways than hacking private NAS drives. 

… and allow remote code execution.

https://learn.microsoft.com/en-us/security-updates/SecurityBulletins/2017/ms17-010

… or ransomeware attack.

https://cybersecuritythreats.org/ms17-010-cve-understanding-the-windows-smb-vulnerability/

As I said, and as you choose to ignore, at home you are perfectly at liberty to assess the risk and deem it not high, especially if all you have on your old (perfectly functional) NAS drive is your music. If I had an old SMB1 NAS, and someone held me to ransom over my music, I’d stick two fingers up at them, wipe it and reload it. 

The point is that even though the likes of Microsoft, Apple etc. will not encourage the use of SMB1 for obvious reasons, they don’t stop you, the user, from deciding otherwise, as contrary to your assertion, they DO allow you to install/configure SMB1. 

Sonos could do the same, but instead chose not to, and just to confuse the out of their users, left the old HTTP helper setup wizards in place as they were too lazy to remove them. (Under the excuse of we’re going to deprecate the desktop controllers, even though we’ve released an update since May 7th, or we’re too busy fixing stuff to change it. Take your pick.)

@Ian_S,

The Desktop controllers have been in ‘maintenance’ mode for some years and I’m guessing the first two library http share options in those ‘old’ Apps can still be used by those on S2 (16.1) or older setup. So maybe that’s why they left those two options in situ. Ideally those using SMBv2, or higher, will just use the new Sonos mobile App anyway to setup their share.

I’m not sure how many Sonos users who use a shared local library, also have a NAS that’s so old that their manufacturer has not upgraded it with a software update to support SMBv2 (or higher)  but I suspect it’s very few and perhaps those users can ask their NAS manufacturer to develop/release an update to upgrade their NAS instead to make it more secure. That sounds a much better option to me than asking Sonos to add the old SMBv1 insecure protocol to their brand new App.

I have not updated Sonos since before the May update, and my NAS music library access & functionality is great (as it has been before & after moving my personal music files to a new Synology NAS in 2021).

Please do not let folks convolute the faulty update issues with finger pointing at you and your network configs. Sonos used to be intuitive/simple enough to require little to no technical acumen. That’s why as an IT professional I recommended it to everyone.

Please continue to request Sonos reinstitute basic, simple functionality we had before the May update (or when we 1st purchased devices; for me 2006). Until then don’t buy or recommend Sonos.

Since last app update the library is back ……… for a few minutes, and then it’s gone again. To get it on I need to power down my Sonos system and after the power it’s back I can see the library for a very short while. All functionality seems to be returned but unfortunately it’s not stable. 

Does the library re-indexing work okay? Have you tried turning off older devices like Playbar/Playbase/Play:3 etc. which maybe low on memory - also perhaps see what happens if you ‘temporarily’ half the size of the library tracks and re-index.

I have 12000 tracks. Can try going down but I want them all . I’ll check the older devices. But would also hate to buy new ones just because Sonos f’d it up. 
thanks for the tip though

Yes me too, I would want all tracks in a library to work aswell and no reason why it shouldn’t work.. I was just suggesting a few things to try temporarily first, just to see if it resolved the issue - if it does, then there are other things you can perhaps go onto try afterwards.

I had the same problem. I fixed it. Here’s what I did…
Can't connect to my music library - solved | Sonos Community

I’ve been trying for over an hour to do what was for a long time very easy, but that Sonos has made absurdly complicated, and is about to lose my business as a result: play music from my music library.

I’ve followed all the instructions to add the library on my MacBook, even changed the name of my MacBook to be no more than 16 characters. Still no luck. The chat customer service rep was a jerk and not helpful, phone customer service was a 35 minute wait and when I missed the call back because I ran to the bathroom, had to start all over again.

Aside from never buying another Sonos product ever again, and replacing my system (what do you all recommend as the best replacement product for a Sonos system now that the company is horribly failing its customers), anything else you can recommend?  Any way we can get our money back? (the chat agent said not if we purchased our system more than 45 days ago, without a hint of apology for the company’s fail on this)

Any advice aside from replace this now worthless speaker system? Talk about an EpicFail by Sonos!

For me, my music library is in OneDrive and accessed through a custom service. Will these services every be accessible on iOS or Android again? Currently, I have to use Mac OS app to play any of my music.

I very much doubt they will. This was a Microsoft and Google decision NOT Sonos this time!

Don’t get me wrong, I expect MS and Google will not make it easy but I still have the custom service added, it just isn’t visible in the new mobile apps. Desktop is working fine. It is a similar situation to another thread. I tried rolling back but as the Sonos devices were updated, the old mobile apps say they are not compatible . In the mobile app I can control volume, pause skip etc, just not find and add tracks to play