

But Sonos cannot detect the nas under the Network part of the tree.ĭoes any of this prompt any ideas or is this one which we need to sit and wait for a following firmware update? When adding the library, as noted above, there is a “browse” option for finding the media folder. I am assuming that what is being browsed is a copy of the library tree and not the live library.


In the sonos App, as others have noticed, it is possible to browse folders, but when navigating to a song, it can’t be found. \\10.0.1.7\Multimedia the music import looks successful for about 10 seconds, media library starts updating, then I get “\\10.0.1.7\Multimedia is no longer available.” Yet its clearly available via explorer windows, FTP, browser etc by network name or IP address. But when attempting the NAS IP address e.g. When adding the media folder using the nas network name and path \\NASQ\Multimedia I am presented with an instant error “Error adding music….check path, user name password….The computer NASQ cannot be found”. Observation: Sonos no longer recognises the NAS network name \\NASQ (which I have been using for years). None of my other laptops have issue connecting to the library. Itunes is still accessing the library quite happily from another PC. This NAS library is where my iTunes library goes. Same speakers, same nas, same router, same switch, same setup with one speaker physically wired to my local network. I have removed the library and attempted both the desktop Sonos App and the iOS app to add the multimedia library. Nothing physical has changed in the setup. I have attempted enabling absolutely all supported protocols on the NAS. There is no 2 factor authentication on the account Sonos uses to access the NAS. I have tried all SMB settings on the NAS. I have been running Sonos and and various NAS since 2009, (currently QNAP TS453D fully up-to-date) I have done some reading on similar posts. The Problem: For months now, Sonos no longer accesses the music library and Sonos alarms now default to the Sonos Chime.Įnvironment: I have S2 app and current supported devices Play 1, 3 and a few others. But going to ask the question anyway as I have noticed a quirk that someone might see as a clue. It looks like this is still a current unresolved issue.
