Skip to main content

Hi

I mainly have used my Sonos system to listen to my own music, which is stored on a Buffalo LS-WXLF5D NAS.

I had it set up and working fine on the S2 app.

Since the up-heavel with the app, I have been without this function. I now see that Manage library is back. I have gone to Add Folder / Enter Share info….given my PC path name and the NAS mapped folder - //192.168.1.10/Z

But, I just get Access is denied. I’ve tried with and without the NAS’s username and password, but same result. Have also tried turning off my Firewall, but same result.

Am I doing something stupid? As I say, it previously worked.

Thanks!

Damien

If you have not been able to use your NAS since May, that could be because Sonos has dropped support for SMB v1 around the same time they released the new app.

You will need to enable SMB v2 or 3 on your NAS to gain access again. 

Search how to do this for your Buffalo device.


Ahh, okay….looks like my NAS is too old, according to Buffalo, to support V2 or 3.

So, you reckon it’s a non-starter?

Thanks for your help.


Ahh, okay….looks like my NAS is too old, according to Buffalo, to support V2 or 3.

So, you reckon it’s a non-starter?

Thanks for your help.

Might the things mentioned in the below link perhaps work for you…?

https://gist.github.com/f00f/b58f1789dc5fb6f28f467fb0cfa1a522


Thanks Ken….shall give it a go and report back!


 The path should not involve the PC.  When in the Sonos PC app on the Sonos Library Settings screen, where you can choose from three options, choose the third one and browse to the music folder in the Buffalo NAS… that is provided that NAS is SMB2-3 capable.


 The path should not involve the PC.  When in the Sonos PC app on the Sonos Library Settings screen, where you can choose from three options, choose the third one and browse to the music folder in the Buffalo NAS… that is provided that NAS is SMB2-3 capable.

You do need to state either the PC netbios name, or its IP address, in the path to the library share from the new Sonos App. I would always recommend adding the shared folder via the (mobile) Sonos App, just so that there’s no mistake made in trying to (wrongly) setup an HTTP share, as those type of shares are no longer supported by Sonos aswell. A HTTP share is not possible via the new Sonos App.

Note a netbios name for the PC should not be longer than 15 characters and should not include:

period (.)
backslash (\)
forward slash (/)
colon (:)
asterisk (*)
question mark (?)
quotation mark (“)
less than sign (<)
greater than sign (>)
vertical bar (|)

Note too that PC Hostnames are used by DNS Servers for name resolution on the Internet and on the LAN and for that avoid using these characters in the PC Name too…

comma (,)
tilde (~)
colon (:)
exclamation point (!)
at sign (@)
number sign (#)
dollar sign ($)
percent (%)
caret (^)
ampersand (&)
apostrophe (‘)
period (.)
parentheses (())
braces ({})
underscore (_)
white space (blank)

So just to be sure things will work, I suggest the PC name does not include any of these characters, although some of the PC Hostname characters may work over the LAN as part of the Netbios name.

So a working example might be something like //MY-SERVER/MUSIC 

Where MUSIC is the name of the shared folder.

If using the IP address instead, like this (example only): //192.168.1.120/MUSIC …then I would make the IP address static (usually in the routers DHCP reservation table, but there are other methods to do that too).

The username and password assigned for access to the shared library folder needs to be a user on the PC that has read-only (ideally) permission on the MUSIC share - check the folder properties on the PC to see which user(s) and what permission they may have to access the share and its sub folders and files.


Ahh, okay….looks like my NAS is too old, according to Buffalo, to support V2 or 3.

So, you reckon it’s a non-starter?

Hi @Damesy, I’d say your old Buffalo NAS is a non-starter. Pretty much any NAS you purchase today will support SMBv2, especially if you go with one of the ‘big’ names like Synology or QNAP or Asustor.

You could also move your music library to your Windows PC, so long as you are copacetic leaving it on all the time.


Ken_Griffiths:

 I use a SonicTransporter NAS for my music share so the path is //SONICTRANSPORT/storage.  No PC name involved.  I browsed to that folder using the Sonos app on my Windows PC.


Thanks all for your feedback. I’m thinking the time is right to upgrade. Interim, I could move the music folder to my PC (it’s left on).

I’ve been looking at the Brennan B3+ as well. Pricey, but apparently integrates well into the Sonos world now...and looks good! Am aware it would require re-ripping all my CDs. Anybody got any thoughts / experience with the Brennan products?


You should check with Brennan. I think that you’ll be able to copy your files to the B3+.


https://brennan.co.uk/pages/how-to-load-music-1#:~:text=The%20upload%20function%20allows%20you,iTunes%20or%20Amazon%20MP3%20folder.
 

 I think this explains the process of loading your music files into the B3.  Don’t own one but if I did I would hope it could be seen as a network drive on a PC/Mac.


Track artwork could be an issue unless it’s is embedded in each track. In the SONOS library a file named “folder.jpg, “folder.png”, etc., will be associated with all tracks in the folder. I don’t know if Brennan supports this.

Edit: file names typo corrected. (Thanks @sigh)


Track artwork could be an issue unless it’s is embedded in each track. In the SONOS library a file named “folder.flac”, “folder.mpg”, etc., will be associated with all tracks in the folder. I don’t know if Brennan supports this.

Do you mean “folder.jpg” or “cover.jpg” ?

Naming an image with an audio file extension doesn’t sound right and is likely to cause issues with applications and operating systems as they will try and examine/read it as audio data, not an image.


Been too long and I’ve forgotten much on this but I have folder.jpg and .folder.jpg files in each album directory here.


Reply