Skip to main content

Does anyone else spend more time trying to get their Sonos (insert product name here) to work rather than actually being able to listen to it? 
 

Does anyone else spend more time trying to get their Sonos (insert product name here) to work rather than actually being able to listen to it? 
 

No, not me: my system is stable and functional. 


Does anyone else spend more time trying to get their Sonos (insert product name here) to work rather than actually being able to listen to it? 
 

Yes. 


Nope, same as ​@nik9669a , no issues. 


Once I set static/reserved IP addresses, a long time ago, I’m in the stable group.

Before doing that, not so good.


I did the same thing as ​@Stanley_4, (static IPs) along with other configurations that Sonos needs to work inside a network with managed switches. I replaced a few speakers during the summer last year with no issues.

 


The vast majority of people that are enjoying their Sonos system, wont be reading this thread. There will be a few exceptions, myself included.


Once I set static/reserved IP addresses, a long time ago, I’m in the stable group.

Before doing that, not so good.

I’ll check into setting that up- never heard of it; thx 


I’ll check into setting that up- never heard of it; thx 

 

List your router make/model and we can probably give you a link to instructions on how to reserve IP addresses.


While setting the reserved addresses take a moment to give each Sonos a decent name too, it can come in handy later.

 


Another here with reserved ip addresses. Maybe I should have said in my earlier reply. It does seem to make a difference on the reliability and stability of systems - including mine. 


Reply