But I still haven’t been able to solve the problem. Freed from the concern about SMB1/2/3, I have started looking at the permissions issues. When you speak directly to the phone folks, they have tools at their disposal that will allow them to give you advice specific to your Sonos system and network. There may be information included in the diagnostic that will help Sonos pinpoint the issue and help you find a solution. And, of course, sometimes background updates can actually change sharing permissions.īut second, if that doesn’t work, I’d try to play a song to generate that error, then I’d submit a system diagnostic within 10 minutes, and call Sonos Support to discuss it.
#Ue music library synology software#
Folder permissions can be challenging, especially because many people don’t understand that it’s not the Sonos application on their controller device, but the Sonos software on the speaker that’s reaching out via SMB.
#Ue music library synology update#
It’s entirely possible that an update of some sort changed the permissions on that folder, and the Sonos system is unable to “reach” that location via SMB. it’s the speaker that’s trying to access that data, not your computer. First, I’d make sure that the folder where the data is was set with appropriate permissions. There’s a couple of potential things that I, not an expert, would be looking at. Thanks, knowing you’re using S2 helps, and yes, you should be fine using SMB 2 or SMB3.
If I have to revert to SMB1, that’s also noxious-in addition to potentially being insecure, it looks like I’d have to choose between streaming my music or doing time machine backups to my NAS. I have an extensive lossless iTunes library streaming doesn't cut it for me. Thanks in advance-hopefully I can get this solved. Right now, I’ve reverted to my older settings (SMB2/3) because the protocol changes the techs suggested messed up my Time Machine backups to the NAS. Any advice on the current state of things? Should things work with SMB2/3? Do I have to go back to SMB1 and take some additional steps? But, if that’s the case, is it safe to run with SMB1? Both techs were kind and helpful, but nothing solved. When I said I had done all of that, the tech said they’d call me back because they were having technical difficulties, but then never did. Second tech took my information, looked up case, gave me same advice. Ended call when my library was indexing after being re-added.īut the problem didn’t resolve-same error.Ĭalled again. After two calls, nothing solved, second tech said they’d call me back in five minutes but never did.įirst tech had me change settings to permit SMB1 communications, despite dire warnings from my NAS saying that it was not secure. But then I saw other posts that suggested the problem had been solved.įast forward a few months, and I finally had the time today to call Synology support. I did some initial online research, and saw that there-at least previously-had been issues because Sonos would only work with SMB1. It’s odd, the library indexes, but whenever I try to play a song it says that the file cannot be found. I deleted and re-added the library, but to no avail.
I'm not sure if the problem started with an update to the Synology’s DSM, or something else. I’m dredging up what seems like an older topic, but one with conflicting answers out there-connecting Sonos to an iTunes database on a Sinology NAS.Ī few months ago, my Sonos system stopped connecting to my iTunes database, hosted on a Synology NAS with their latest DSM software.
0 kommentar(er)
