Trending Lyricist I

Answered

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

27 replies
1512 views

once i upgraded the OS of my linux box its SAMBA service is not recognized anymore by my Sonos connect:amp device - while the same setup worked just fine for years. no browsing in the directory tree, no music library update, no playing of any music files, nor mp3 nor flac…

the crucial difference i assume is in the SAMBA version, now at 4.15.5 which does not come anymore with the ancient SMB1/NT1 protocol the connect:amp relies on. is there anybody out there that got the connect:amp work with a modern SAMBA version > 4.11 ?

here a few elements in my smb.conf file that helped in the past to make this work :

client min protocol = NT1
server min protocol = NT1
ntlm auth = ntlmv1-permitted
follow symlinks = yes
wide links = yes
unix extensions = no

any help is greatly appreciated !

This topic has been closed for further comments. You can use the search bar to find a similar topic, or create a new one by clicking Create Topic at the top of the page.

P

pistiAnswer

Trending Lyricist I

to everybody who tried to help me here with my SMB1/SONOS problem. i somehow got this issue resolved, it’s now QNAP that speaks to my connect:amp - see here under LinuxQuestions - so, i took the easy route, for the moment at least…

thank you for your efforts and time !

Show previous replies

Corry P

Sonos Staff

Hi @pisti

Sorry to hear that - I thought we were on to something.

i am wondering how to get hold of a *complete* example smb.conf file, best for passwordless access of a directory tree with NT1/SMB1, that proven works with SONOS ?

As far as I am aware, if you delete the smb.conf file, a new default one will be generated by the SAMBA service upon restart. An uninstall/delete/reinstall would certainly do it. You’d need to add the share paths to the conf again, of course.

I’d give you my own conf file if I actually had a S1 system and knew it would work for you, but I think regenerating it and adding only the shares, the min/max values and ntlm would do the trick. Edit: A helpful colleague of mine with S1 just tested this and found it to work! His [Global] section looks like this:

log file = /var/log/samba/%m.log
   log level = 10
   unix extensions = no
   follow symlinks = yes

# Security
   client max protocol = SMB3
   client min protocol = NT1
   server max protocol = SMB3
   server min protocol = NT1
   ntlm auth = yes

#======================= Share Definitions =======================

[example1]
writeable = no
path = /mnt

Edit: It seems to be important to have “unix extensions = no” included

then the instructions what ownership & permission settings to apply to the directory tree in question.

Sonos requires read access, so the user you pick to be the SMB user in the conf needs those permissions on the parent shared folder and all children. I tend to use the permission octal of 775, for non-Sonos-related access. The SMB user configured in the conf file needs to be in the same group as the main user ID that is used to put the files there in the first place, or to be the same actual user.

last i would like to see the corresponding three lines that need to be entered in the SONOS S1 App under Settings-System-Music Library-Music Library Setup-Add Shared Music Folder such as //IP/PATH;username(empty?);pswd(empy?)

The first would be //server/share (if IP is static it is probably more reliable than NETBIOS name)

User and password are needed if you set up your SMB server to require them - this is probably for the best.

as said, i used my SONOS connect:amp for the last 10 years with music libraries stored on Slackware linux or on the QNAP NAS, and things worked fine - though each upgrade brought its own SAMBA quirks.

a last avenue for me before starting to play with Raspberries and other old-OS linux boxes, could be to install a 1TB SSD in my QNAP NAS and use its inelegant GUI and associated services to serve my 17K music files...

If that’s something you already have, it’s better than spending more money, I guess. I’d try it.

I hope this helps.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein

P

pistiAuthorAnswer

Trending Lyricist I

to everybody who tried to help me here with my SMB1/SONOS problem. i somehow got this issue resolved, it’s now QNAP that speaks to my connect:amp - see here under LinuxQuestions - so, i took the easy route, for the moment at least…

thank you for your efforts and time !

Corry P

Sonos Staff

Hi @pisti

That’s great to hear - thanks for updating the thread!

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein

P

pini

Lyricist I

Please SONOS consider upgrading SONOS S1 firmware to support SMB2 protocol.

I can’t use my Play 5 anymore : it can’t access my music library while any other device can.

Corry P

Sonos Staff

Hi @pini

Please SONOS consider upgrading SONOS S1 firmware to support SMB2 protocol.

This isn’t technically possible as SMB2/3 support requires a build of the Linux kernel that our legacy devices simply do not have enough resources to run - this is one reason why models have been revised over the years. For your Play:5 (Gen1) to be able to access your network share, the share must be SMBv1.

I hope this helps.

"Common sense is the collection of prejudices acquired by age eighteen." - Albert Einstein

P

pini

Lyricist I

I finally resurrected my library using samba inside a Debian buster docker image.

E

echidna

Lyricist I

I ended up building the samba gateway as described by Stan Miller. It took a little while to get started but once I had the Raspberry Pi up and running, the changes were pretty minimal. Works like a charm and I would definitely recommend it to anyone with SMB V1 problems.

https://stan-miller.livejournal.com/357.html

Sign up

Login to the community