Renowned Enthusiast I

S1 system connection to library on NAS. I just can't get it working, so any expert advice most welcome.

Forum|Forum|2 years ago
September 21, 2024
18 replies
527 views

I have Android controllers and have been investigating rolling back to S1 in search of stability and the functions I got used to over the years which have now disappeared.

I dug an old P5 and an old Android tablet out of storage and set up the S1 App on the tablet from the App Store and on my Win 10 PC from Sonos’ website. Setup went smooth as silk (I didn't even have to power off my S2 speakers, everything on the same sub-net) and I now have S1 v11.14 build 572150280 on both my PC and the tablet and S1 v11.14 build 572151190 firmware on the P5.

Sonos Radio was there already and I installed Amazon Music, BBC Sounds and the excellent iBroadcast having spent 5 days uploading my library to it non-stop over my pitifully slow broadband connection. All these work perfectly and I thought I was on a roll.

Then I went to hook up to my music library copies of which, for whatever reason, sit on two separate Synology NAS units, both of which are on ethernet connections. My S2 system runs off one of these and, for this exercise, I loaded a portion of the library to it from the second NAS. It connected fine and then I tried switching the SMB service on the second NAS between 1-3, which worked fine, 3 only, also fine, and 1 only which cut off access to that drive as one would expect. So far so good.

Then I tried connecting the S1 app, from both the tablet and the PC, using exactly the same network paths (IP address throughout) and login credentials as on the S2 setup. I tried it on both NAS units, with SMB1 and SMB1-3 running on both, even trying both \\ and // in the share address (the S1 app still shows \\ in the Add New Share screen, although they have finally corrected that in S2.) Nothing, but nothing, on either NAS worked - all I ever got was an "Access Denied...." message.

I have gone as far as I can with this - and am still seriously interested in rolling back to S1 for my entire system - but I just cannot see what I am doing wrong when it comes to connecting to the NAS library. Can it be that this facility has been removed from S1? It certainly worked fine back in the day when S1 was all we had. Incidentally, I tried along the way downloading earlier versions of S1 from APKMirror but they wouldn't open up at all, citing "a bug" in the file.…

Does anybody have a clue where I am going wrong? I really hope this will work, but I've totally run out of ideas (and patience!)

Any suggestions will be very welcome.
Cheers
John

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.

MoPac

Headliner III

Do you have Sonos speakers that only work on S1?

press250

Prodigy III

Hi @jreddaway, as an experiment try setting your NAS to SMBv1 only (disable v2 and v3) and see if your S1 system loads your music library. It’s possible that your ‘tri-lingual’ SMB setup is confusing S1.

J

jreddawayAuthor

Renowned Enthusiast I

Do you have Sonos speakers that only work on S1?

Yes, the P5 which I have got working fine except for the NAS connection, which is what makes it so frustrating. I also have an old connect:amp which I was going to try next after a reset, but am holding off on that for now.

J

jreddawayAuthor

Renowned Enthusiast I

Hi @jreddaway, as an experiment try setting your NAS to SMBv1 only (disable v2 and v3) and see if your S1 system loads your music library. It’s possible that your ‘tri-lingual’ SMB setup is confusing S1.

Yes, press250, I tried this and the S1 setup still couldn't access the folder. The S2 system couldn't read it when just SMBv1 was in play but was fine when v3 was turned back on, even with v1 still active.

It's all very mysterious; the S1 setup just seems to be unable to make the NAS connection, but I can't believe that capability has been deliberately disabled. That's why I'm sure I must be making a mistake somewhere.

MoPac

Headliner III

For sure S1 uses SMBv1. I think press250 has a good idea. Not familiar with S1 on a Windows PC. Does the “add a share” work the same as it does on the S2 Windows app?

J

jreddawayAuthor

Renowned Enthusiast I

For sure S1 uses SMBv1. I think press250 has a good idea. Not familiar with S1 on a Windows PC. Does the “add a share” work the same as it does on the S2 Windows app?

Yes, @mopac, the "add a share" popup card is the same in S1 as in S2, the only difference being that the S2 version has the correct // hints for the path format, unlike S1.

Identical inputs on all 3 lines (path, user name, password) work in S2 but not S1. And BTW I was coming to it through the third wizard or whatever option on the previous screen, the add from a NAS one.

All very frustrating.

MoPac

Headliner III

Have you tried using the “Browse” option to find your NAS share in Music Library Settings / Add? That writes the path automatically. Of course you still have to enter credentials.

J

jreddawayAuthor

Renowned Enthusiast I

Have you tried using the “Browse” option to find your NAS share in Music Library Settings / Add? That writes the path automatically. Of course you still have to enter credentials.

Yes, @MoPac . In S1 it brought up the path with \\ which is wrong anyway and the server name as text, which didn't work even when I corrected \\ to // . Nor did it work with the numerical IP address, with either \\ or // . All with just SMBv1 activated.

You can understand, perhaps, why i am so frustrated. I can't think of any combination I haven't tried...

Ken_Griffiths

Hi @jreddaway, as an experiment try setting your NAS to SMBv1 only (disable v2 and v3) and see if your S1 system loads your music library. It’s possible that your ‘tri-lingual’ SMB setup is confusing S1.

Yes, press250, I tried this and the S1 setup still couldn't access the folder. The S2 system couldn't read it when just SMBv1 was in play but was fine when v3 was turned back on, even with v1 still active.

It's all very mysterious; the S1 setup just seems to be unable to make the NAS connection, but I can't believe that capability has been deliberately disabled. That's why I'm sure I must be making a mistake somewhere.

I have an old S1 system here (App version 11.14) connected to a Netgear NAS library - it’s SMB v1 only. So it definitely should be working for you. I’d perhaps double-check the share permissions and user credentials.

MoPac

Headliner III

That’s weird. You’re right about the forward slashes //. That’s how my paths show. What is the name of your Synology share? I thought it was something like Music or Shared Music. Waking up my Synology to check. My Synology library is not indexed to Sonos because if it was the library would be too large.

At one point were you able to index that Synology share? If so what did the path look like.

I’ll get on the Windows PC to see what the name of the share is on my Synology.

Show more replies

Sign up

Login to the community