Sonos S1 will no longer connect with a Samba share on latest Xigmanas

11 replies
547 views
Translate All

I have a “Five” speaker that needs the S1 controller app - it was all working beautifully untill a recent update of Xigmanas to v13.3.

Play:5: Bedroom
Serial Number: 00-0E-58-5B-8C-7E:3
Sonos OS: S1
Version: 11.14 (build 572151190)
Hardware Version: 1.16.4.1-2.0
Series ID: P100
IP Address: 192.168.2.26
WM: 1
OTP: 1.1.1(1-16-4-zp5s-0.5)

This included an upgrade to the latest version of Samba.

Samba have now dropped support for SMBv1 which is the cause of the problem :

Question asked on Xigmanas forum :-

What has changed between 13.2 and 13.3 ???

Samba is upgraded to 4.19.7 so it refuses SMBv1 connection attempts.
You'll either have to upgrade your Sonos device or keep your xigmanas at 13.2

Is there any chance of S1 being udated to use a higher version of Samba ???? Otherwise it renders my ”Five” useless as I must keep the NAS up to date.

Dave

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.

Stanley_4Answer

Grand Maestro

You can use an SMB gateway to provide V1 to your Sonos. That let's you run any protocol on your NAS while the gateway shares the data onwards in SMB V1. I did that using a Raspberry Pi but any computer that supports V1 will do..

Show previous replies

sigh

Prodigy II

Nice idea but the NAS SMB is already set to that - it has no effect for Xigmanas 13.3.

Dave

I have RPi sitting here doing nothing so I’ll have a go at SMB Gateway

Thanks for the clue guys :-)

Dave

I’ll risk the wait for moderation again, but that is odd and is the only change I made to connect from my laptop to server. All the other settings on that page are just clean install defaults. 🤷🏼

If I then set Server Min. Protocol back to default I get a no SMB1 error as expected because the default is v2

Hope you have better luck with SMB Gateway.

Translate

Sign up

Login to the community