Does Sonos S2 support SMB V2 V3?

I’ve been tearing my hair out for months trying to get my Sonos system (S2) to connect to my NAS reliably, but I think I might have just sorted it…

• My issue at first was the library index failing part way through so I could only see part of my library.
• Updated the NAS firmware and couldn’t connect at all as SMB1 was disabled.  Enabled it and was back to the partial library issue.
• Months later… checked and the issue is still there.  But I noticed that despite (I thought) needing SMB1, Sonos was connecting via SMB3.  Configured the NAS to allow ONLY SMB1, then updated index.  All tracks seem to be in the Sonos library.
• Back to NAS and reconfigured it to allow SMB2 and SMB3 but not SMB1.  Now listening to NAS music on Sonos via a SMB3 connection, without the SMB1 vulnerability…  Woo!!

So… Sonos S2 supports SMB3 but the library connection/update is flaky.  My workaround is to force a SMB1 connection for the update, then revert to SMB3 for normal use.  I don’t update my library too often so I can probably live with that until Sonos manages to fix the flaky updating.

@apbliv if you’re updating your library every day or week the above will be a pain, but I recommend giving it a go.

Thanks. I will give it a go, but I don’t hold out much hope. Sonos loses my library almost daily - if not hourly. Once it loses the library I have to restart from scratch by deleting the NAS connection in the sonos app.  Trying to reconnect is a pain as the app will then not find my NAS drive until I have had multiple goes both browsing for the NAS or just typing in the path.
There is something seriously wrong with the sonos software implementation of SMB2/3. My NAS works seamlessly on everything else I ask it to do. 

I’m using a Linux box, a Raspberry Pi, as my NAS and it happily sits there and works.

I’m wondering if there isn’t something that a few NAS systems are doing that cause the NAS/Sonos issues.

Samba config is dead simple:

[global]

# enable v2 authentication
min protocol = SMB2
# Do not use protocol, limits S2 to SMB2_10
#protocol = SMB2
[music]                                                                                 
Comment = Pi shared folder                                                              
Path = /mnt/ssd-music                                                                   
Browseable = yes                                                                        
Writeable = Yes                                                                         
only guest = no                                                                         
create mask = 0555                                                                      
directory mask = 0555                                                                   
Public = yes                                                                            
Guest ok = yes 
 

Thanks for all the suggestion.

My music library has stayed up for nearly 24 hours, which is unusual

Maybe the issue is with the Synology NAS? I can’t restrict the NAS to just SMB v3 - min SMB2 and max SMB3.

As it is snowing and my Thursday morning outdoor tennis is cancelled, I decided to try Update my Music Library Now and up pops a message that my Music Library is “no longer available”. The Music Library is gone again.

I deleted my music library, added it again and reconnected at the second attempt. Update Music Files then tells me the Music Library is unavailable, so I am back in that loop. At least streaming the music gives some money to the artists, though I can’t stream all the things I want to listen to.

Sonos Windows App is version 15.1.1 and my Synology NAS is DSM 7.1.1-42962 Update 4 - both the latest versions.

Looking in the NAS logs at how many external users have been trying to connect to my NAS, I don’t want to risk SMB1.

Alan

I have a Synology NAS (DSM7) and set up an account for Sonos Access to the Music folder of that NAS only. Set Sonos as the user name and added a suitably long password. Works a treat.  

BUT

Sometimes when the NAS has gone into Idle it can take 5-10 seconds for Sonos to see the Music folder and throws a few “Can’t find track” errors.  Soon clears though.

Your NAS is exposed to the internet??? That sounds like a terrible idea to me.

Hi bockersjv

I had everything working perfectly before my work admin told me to disable SMB1 (which I am glad they did). Since disabling it, though, I have had nothing but woe with my music library in Sonos.

I can make sure the NAS is not idling by running a sync job with my laptop, and Sonos will still not find the NAS - just tells me it is either switched off or the path has changed. A NAS reboot has made it visible again, and it indexes.

Maybe I just need to schedule a nighttime reboot.

Thanks for the input.

My Synology’s are slow starting. Sometimes as I start a new listening session SONOS will become impatient and throw an error message. Usually, this results in the first track being aborted.

@bockersjv 

Can you elaborate on this please?

I have a Synology NAS (DSM7) too, and my music library has been refusing to play properly. I can see everything listed, but it frequently skips tracks. (Log files show it is trying to connect using SMB1).

Are you saying you have a separate account on your NAS for Sonos only? Why would that make a difference?
Thanks