It's been quite a while since I've posted here. I'm a long time user and huge fan of Sonos. I used to be very active on the forums several years ago but 3 kids and a demanding job have steered me in other directions.
Anyway... I recently made some changes to my network at home and ever since I was having a frustrating and odd problem where my library would work as expected for 24 hour or so and then suddenly stop working (I'd get an error message that it couldn't play a track because it couldn't find the file). If I simply rebooted the server machine everything would resume as expected but within 24 hours (Usually less) the problem would resume.
I put in several calls to Sonos and they were super supportive but we just couldn't figure out what the heck was going on.
Here's what happened. I added a new computer to my network. I did this to replace my old desktop with a newer machine but I still wanted to use the old desktop as a media server. Since this desktop was in my study, I named it "Study". I wanted the new computer to be named "Study" so I renamed the old one "Study-PC" and named the new one "Study-HP". I deleted my old library share in Sonos and readded to make sure it got picked up. Things went fine... for a day. Then my problem started.
Long story short, I read somewhere that special characters can cause some network issues. So I removed the "-" from both computer names, reestablished my library and BAM! Problem solved.
I just wanted to post my saga here in the hopes that it might help someone else down the road. I just happened to stumble onto this solution. I could easily see where I might have spent a long time trying to track this one down...
By the way - this was also causing problems with my XBMC streaming setup as well.
Hope this helps someone.
Anyway... I recently made some changes to my network at home and ever since I was having a frustrating and odd problem where my library would work as expected for 24 hour or so and then suddenly stop working (I'd get an error message that it couldn't play a track because it couldn't find the file). If I simply rebooted the server machine everything would resume as expected but within 24 hours (Usually less) the problem would resume.
I put in several calls to Sonos and they were super supportive but we just couldn't figure out what the heck was going on.
Here's what happened. I added a new computer to my network. I did this to replace my old desktop with a newer machine but I still wanted to use the old desktop as a media server. Since this desktop was in my study, I named it "Study". I wanted the new computer to be named "Study" so I renamed the old one "Study-PC" and named the new one "Study-HP". I deleted my old library share in Sonos and readded to make sure it got picked up. Things went fine... for a day. Then my problem started.
Long story short, I read somewhere that special characters can cause some network issues. So I removed the "-" from both computer names, reestablished my library and BAM! Problem solved.
I just wanted to post my saga here in the hopes that it might help someone else down the road. I just happened to stumble onto this solution. I could easily see where I might have spent a long time trying to track this one down...
By the way - this was also causing problems with my XBMC streaming setup as well.
Hope this helps someone.