Can't connect AGAIN!

If it was just a duplicate IP it would be easy for Sonos to do a fix, the Linux base they use includes the arping command with the “-D” option to detect that. The proper response to finding a duplicate is another arping command with the “-w” option to update others on the LAN, then issuing another DHCP request by the Sonos.

From my many hours of testing, network monitoring and router-DHCP log reading I did not see any issues with the addresses handed out by my DHCP server or in the Sonos requests sent to it. I tested several routers as well as a bare DHCP server with the same result.

Access to the internal Sonos data would probably show the issue but we can’t get that. I’d lean to Sonos using an older version of the DHCP client, doing something slightly out of the usual in a configuration file, or a boot timing issue where Sonos and the DHCP server get out of sync.

I believe, Sonos, that you are missing the point.

Any decent system designer knows that simple connectivity for users who want to “listen”, not be a techie, is critical.

the systems are sold as seamless to install and use … anywhere .., along with delivering high quality sound.

rather than spending countless hours and frustrating more customers, just find a solution that doesn’t involve users being embroiled in this pointless debate

personally, I’m just about ready to ditch my system … I’ve had mine for years and at least twice a year, I have to tear it down completely and restart … after suffering thro painful lack of connectivity one day to experiencing audio bliss the next … it’s just not reliable and I won’t sink anymore if my time or money into a system, that by its architecture, is destined to fail

Unfortunately “Just fix it!” isn’t a plan, and anybody who lacks the level of “techie” ability needed to reserve IP addresses (which is just slightly above the knowledge it takes to change a Wi-Fi password), shouldn’t be giving a critique of any “architecture”, be it a music system or the house down the street. 

The old adage of “Stay in your lane” applies. 

@PoppaK,

This just has to be a bit of a wind-up, what do you mean by …

“…at least twice a year, I have to tear it down completely and restart … after suffering thro painful lack of connectivity"

That’s If you are trying to claim that you factory reset all your Sonos devices and start again from ‘scratch’, twice, every year? … and you’ve only just joined this community forum today, for the first time?

Anyhow, I’m struggling to think of a valid reason to ever do those ‘tear down’ steps (not even once, never mind twice a year) and then start over with a new Sonos Household again.🤷

If that’s true, then you’re really not understanding how Sonos works. You could just simply switch off any one (or two) speaker(s) and keep your Sonos Household safe, until you sort out the network connectivity issues.

I can’t personally recall ever doing a full system reset for my Home Sonos system and I’ve probably changed my Home router-wired/wireless networks at least four times in the past seven+ years or so …and not ever considered taking such a drastic step.

I’m sorry, but it sounds like it’s actually you that’s missing the point here.

“tear it down completely and restart”?

Never, in 16+ years.

Along the way I have obviously resolved the odd wireless issue and, to avoid transient glitches, reserved fixed IP addresses for my kit.

15 years, not once.  Even through multiple router changes and a move from one home to another.

exactly why I stay away from these forums … a bunch of trolls bashing folks that aren’t like them.

just so you know, I hired tech geeks to address my wireless/network issues eons ago and it runs seamlessly. … and I’ve gone thro multiple network/router changes/upgrades … I’m smart enough to know when I’ve passed the limits of my technical competence and hire experts.  

I only judge products based on performance per the promises of sales people.

So … rather than sit and slag folks on boards, take the time to read what they actually say … and recognize that the rest of the world is not like your simple little bubble

… and btw … I faithfully go through the steps that sonos prescribes to resolve connectivity issues from simple off and on to full reset to complete restart.  Until you sit in my house with my system, and understand my circumstance, i believe it would be prudent for you to either withhold comment or seek ways to positively engage …

to confirm, yes, this is why I haven’t engaged in this forum for years … seldom do you get constructive help or insights … just comments from people seeking ways to make themselves feel better at someone else’ expense

Hmm… over the last 15 years I’ve helped literally thousands of people. But believe what you will.  

as have I … as a part of my professional career … sadly you believe that you’re helping by trashing others when they don’t conform to your bubble … so … “believe what you will”

If “conform[ing] to [one’s] bubble” means having a sound network then yes that’s necessary for Sonos to work reliably. It depends entirely on good intra-subnet communications, unlike devices which simply need to connect out to the internet.