Two homes with two NAS. Can I duplicate my iTunes library so I can listen with Sonos at both homes?

Are these Sonos playlists or iTunes playlists, if they're the latter, they're tied to the device that is streamingi was referring to Sonos playlists. It is juzt as well to be aware of the consequences of a fresh setup.

Yup, sounds about right, my playlists are usually on Spotify or saved locally on a device like an iPhone or computer.

Wondering if it's an iTunes authorization block. Granted you used iTunes to rip media off CDs, it shouldn't lock your files with DRM since you own the CDs.

Wondering if it's an iTunes authorization block. Granted you used iTunes to rip media off CDs, it shouldn't lock your files with DRM since you own the CDs.I don't see how it can have anything to do with iTunes permissions. Sonos does not interact with iTunes itself at all. It may use the iTunes library as the place it gets the music files, but it's just another folder as far as Sonos is concerned. In any case, the OP has stated that he can play the same files when stored on his laptop,

That's why I had requested that he attempt to do so in the beginning, to eliminate the possibility that the files are locked with DRM. Some files simply won't play for this reason. He's able to access the share and playback the media through another source which means it's a firewall or permissions problem

That's why I had requested that he attempt to do so in the beginning, to eliminate the possibility that the files are locked with DRM. Some files simply won't play for this reason. He's able to access the share and playback the media through another source which means it's a firewall or permissions problemI agree that is very likely.

Both the RAID server at the primary location and the portable NAS are Buffalo brand products. One thing that I noticed is the primary RAID server has an iTunes server built into the firmware and the portable NAS does not. Well I am about to pack the portable and fly to Jamaica on Friday. I will try the multiple sugestions posted when I get there. I just wanted to be able to re-copy the originals to the portable if I had done something incorrectly. Please keep this topic alive and I will try anything to find a solution. Thank you for your assistance so far...

Have you actually fully reindexed Sonos to the new file location? That is, deleted the share that is your "home" NAS and added the share that is your "vacation" NAS and allowed a full reindex? I wonder if when you say it "sees" the artist information etc, it is actually "seeing" your home NAS info? I have to say that I would expect a "file not found" error in that case rather than a permissions thing though.

I can't help feeling that this is a network or NAS file sharing thing. Worth checking, if your laptop is Windows, that the network is being treated as "Private" rather than "Public", so that network discovery is on (depending on your current settings). Again, I can't really say that this looks iikely on the evidence, but you never know.

If another device is able to see the NAS, access the designated network containing the specified media and in turn, play the media within the vacation house network, only a few variables exist.

Since other devices don't seem to have a problem locating and playing back the media, one can begin to think the Sonos system may be in a bit of a state confusion where it thinks something is present when it really isn't. Reindexing should in theory, fix the problem once the proper steps have been run through as suggested.

Have you actually fully reindexed Sonos to the new file location? That is, deleted the share that is your "home" NAS and added the share that is your "vacation" NAS and allowed a full reindex? I wonder if when you say it "sees" the artist information etc, it is actually "seeing" your home NAS info? I have to say that I would expect a "file not found" error in that case rather than a permissions thing though.

I can't help feeling that this is a network or NAS file sharing thing. Worth checking, if your laptop is Windows, that the network is being treated as "Private" rather than "Public", so that network discovery is on (depending on your current settings). Again, I can't really say that this looks iikely on the evidence, but you never know.

I've seen that on one other occurrence where the files that Sonos thinks exists no longer does. A dialog box pops up momentarily and tells you that it can't play a song because access to it is denied, but in reality, the song was either deleted or moved.

Now, given that the OP cloned his media library and took it to his vacation home in an attempt to stream music, Sonos would have trouble finding the old network since the SSID won't match up with the primary residence and prompt a reconfiguration.

That being said, if there really is an iTunes server function built into the NAS, that essentially is another way of serving media (i.e. DLNA Media Server), it isn't crucial that the setting has to be on for Sonos to pick up your music. I have a Synology NAS and it also possesses that function, though mine is switched off. You'll need to create a network share containing your media that can be accessed by devices on your new network in your vacation home. Basically, you'll need to revisit the Buffalo NAS settings and make sure the credentials you have set in place allow for access into the folder(s) containing your music.

From there, you'll want to set a static IP so any device that connects to your NAS can always find it. Think about it this way, if your home address were to always change without notice, your friends and family would have a hard time getting a hold of you, no? The same applies to the NAS. You could in theory use the name of your NAS and type out the rest of the file path, like so.

\\Azure\Music\Bob Dylan
\\Azure\Music\Mozart

HOWEVER, if you have a device (i.e. computer) with the same name as your NAS, "Azure", Sonos will most likely confuse the two and you'll come across the error we have been exploring because though it may see the files, it can't directly access them since it is mistaking one network device for the other. And so, this is why it is generally recommended to use the static IP because it is assigned to each individual device within your local area network.

After a static IP has been set, you'll want to start anew and reintegrate your library because you are on a different network and you will need to teach the system where all of your media is stored, hence the indexing process.

Private and Public discovery within your network shouldn't really matter because you can map the drive regardless if you know the static IP and login credentials that allow access to the network shares. If they're public, they can being readily accessible by clicking them, but if they require credentials, you'll still need them regardless to access the media contained within. Here's an example to support my theory, routers possess the ability to hide SSIDs/WiFi Connections, but that doesn't necessarily restrict use altogether. It effectively removes it from the generic list that populates when a device scans for wireless networks it can connect to. If you know what you're looking FOR and/or have the information needed, it will always be there, just like a secret passageway or in our case, the static IP.

You can enable or disable that function within the NAS, that is, the ability for others to visibly see a specific network share within your network, but that shouldn't have any impact in connecting directly to the folder.