Skip to main content

I have Play 3 (x2) and Play 1 working just fine. They access Synology NAS for my music folder. I added a Connect:Amp (ZP120) which feeds 2 outdoor speakers, but it’s access to the music folder is denied. Radio and Spotify work fine, just access to the NAS folders is the problem.

I have rebooted the NAS (I have SMB1 and NTLMv1 checked), removed and readded the path to the NAS folders in the S1 app.

I tried altering the config file (smb? via SSH and PuTTY) but when I typed in cd/etd/samba it said that the file could not be found.

I can play the outside speakers from the NAS file, but I have to group it to either the Play 3 or the Play 1.

I cannot figure out if it is the Sonos unit or the NAS.

Any ideas?

Glenn

I’m not sure I understand. All of these speakers are part of the same S1 system, yet some can’t reach the NAS running SMB v1?

The only thing that pops to mind is that these devices are on different subnets, but then they shouldn’t all be showing up in the controller at the same time. But then I don’t understand how the speakers can all show up in your controller to operate. 

I think your best bet may be to run a diagnostic both after successfully playing something on the NAS from one speaker, and another after trying to play on one of the speakers that isn’t connecting, then call Sonos Support directly to discuss it.


Yes, all part of the same S1 system. It is just the Connect:Amp that cannot access the NAS. Yes, NAS is SMBv1. They all show in the controller. I can play Spotify to the Connect:Amp and that works fine.

I will run some diagnostics and talk to SSupport.


One thing I noticed with the new Connect:Amp is that it has a OTP, whereas all the other units have none:

Connect:Amp: Alfresco
Serial Number: 00-0E-58-DC-6F-06:0
Sonos OS: S1
Version: 11.12 (build 571946310)
Hardware Version: 1.16.3.1-2.0
Series ID: P100
IP Address: 192.168.0.7
WM: 0
OTP: 1.1.1(1-16-3-0.9)

Could this have anything to do with access to the Synology NAS being denied?

Tks...