SAMBA v4.15.5 file server stopped working for Sonos connect:amp

Hi @pisti 

Welcome to the Sonos Community!

We added SMB2/3 support late last year, but on S2 systems only. Thankfully, although your Sonos system is on S1, it is S2 compatible - please update your system to S2 and you will be able to use SMB2/3, though version 4 is still unsupported. To update, please start at our Sonos S2 Overview page.

Once you’ve updated to S2, if you change each “NT1” in your smb.conf file to “SMB2” and restart the SAMBA service, things should work a bit better. You may need to remove your old share from Sonos and add it again, but hopefully not.

I think you’ll be safe to remove the “ntlm auth = ntlmv1-permitted” line, but don’t quote me on that.

I hope this helps.

client min protocol = SMB2

server min protocol = SMB2

follow symlinks = yes

wide links = yes

unix extensions = no

wow, dear Corry, i was very happy to read your reply !

now, unfortunately, it turns that my connect:amp device will not be compatible with S2 as i had bought it way back in 2012, making it belong to the 1st generation SONOS league and hence incompatible with S2, sniff.

i guess, in this case, my only option to make this SAMBA fiesta work is to try re-using an old QNAP NAS and export music files via its QNAP protocols that hopefully still support SMB1 - or, alternatively, get a new Amp, gulp.

i will get back to this audience once successful...

You could always use a NAS to SMB v1 gateway. Here it is running on a Raspberry Pi but it will work on any SMB v1 server.

SMB v1 Gateway  https://stan-miller.livejournal.com/357.html

dear Stanley, thank for your elegant suggestion - though i decided, for time reasons,  to resort to my existing QNAP NAS and use its spinning disks for storage of my music files.  i tried to downgrade SAMBA on my upgraded linux server to v4.6 but the S1 SONOS app and S1 OS on the first generation connect:amp both adamantly refused to connect to the linux samba service.  sadly, because i have SSD drives on that linux server, while i hate to boot those precious 20TB spinning backup disks just for listening a bit of music.   anyway, that’s where we are currently.  i am much more familiar with NFS services, while SAMBA i used and solely use for this SONOS fiesta...

thank-you for your inputs, Corry and Stanley.

I understand time and simplicity issues and the frustrations folks are facing with Sonos and Samba. That is why I built and shared both the SMB v1 gateway and a SMB v1 server.

Build once, never update, just let them run forever tucked out of sight somewhere.

Live Journal: Stan  https://stan-miller.livejournal.com/

I’m using the server today, plugged an old SSD into a SATA-USB converter cable ($10) and it is happily serving my Sonos needs.

At some point I’ll swap over to using the gateway to my main NAS. I do not run Samba on it, any version, so I need to connect to it via NFS and share out a Sonos compatible connection. This will save me about 5 Watts of power and a tiny bit of space so I should do it. It will also save a couple minutes when I (rarely) add a new item to the library.

dear Stanley, you definitely caught my interest, nfs xfs are terms i am familiar with.  i guess a raspberry pi comes with ubuntu or alike OS while i am a hardcore slackware guy - but as long as there are just simple CLI & script moves to do i think i will manage.

same here, i rarely add flac files to the library - though i still have some 600 LPs left to digitize,  while a first round of 200 LPs’ flac files (and gazillion other high-res FLACs) i play already regularly from my venerable SONOS connect:amp and its associated SMB1 server...

The Pi foundation offers several operating systems and versions: 

https://www.raspberrypi.com/software/operating-systems/

Many other distributions have a Pi version too.

https://www.fossmint.com/operating-systems-for-raspberry-pi/

Looking at this list I run BSD on a couple boxes, hoping to find time to try it on one of my Pi. Same for OpenSuse, we use it as our desktops and server so a Pi version might be interesting.

Hi @pisti 

When I first looked up your account, the page I was on told me you had a S2-compatible system, but were on S1.

That page has now apparently changed.  Apologies for the confusion, and for getting your hopes up! I’m not sure what happened there.

Another option for getting your music onto your S1 system would be to install a Plex server on your Linux box, and add the Plex service to your Sonos system. You’ll need to set up an account with Plex, but they have a free tier.

I hope this helps.

wow ! now i suddenly see several options how to overcome my/our SMB1 problem : Raspberry, then Plex, a VM with SMB1, or simply installing an old OS on an old server+SSD+SMB1 - thank you for all your advice, Stanley and Corry.  to me it boils down to choosing an avenue that costs me the least amount of effort (i am bizi enough with other software projects).  so, perhaps PLEX is the easiest way to go as i just found a Slackware 150 compatible repository for PLEX - which i hope will even work as advertised.

soon more... 

well, well - the PLEX avenue was perhaps a bit to good to be true ! 

in order to be able to browse through my 1700 music directories with some 17,000 FLAC files i would need to upgrade to PLEX-Pass which comes with a monthly fee…  their browser-based PLEX software seemed to work otherwise surprisingly flawlessly, but without offering a ‘Folder’ view it renders itself into a somewhat useless tool for music enthusiasts with large music file collections, unfortunately.

so, we continue our SMB1 odyssey - and will try the VirtualBox/oldOS/oldSAMBA/SMB1 route, sigh.

i prefer for now to go with a software solution instead of old/new hardware, that’s why i refrain from using  a Raspberry or an oldServerBox solution.

soon more...