NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

boojiboy71's avatar
boojiboy71
Aspirant
Jun 01, 2022

IP conflicts with my Sonos system

Hello,

Whenever my network reboots for whatever reason, it re-allocates the IP addresses and every time 1 of my 5 Sonos devices will end up on 192.168.1.32 which is a static IP for my security system. The manual way that I can resolve this is to unplug which ever Sonos device ended up on that IP, and then reboot my system. And then plug my Sonos device back in after the reboot is complete.

I don't know why this is happening, Sonos tech support seems to think that the mesh system is confusing the Sonos devices and every time I reboot the Sonos devices see the router and the 2 satellites all as separate access points.  Here's the transcript from part of my Sonos tech support chat:

 

"Sonos 5" connects to an AP on WiFi channel 44.  "Sonos Move" connects to another AP on the same WiFi channel, 44.

The rest all connect to a third AP on WiFi channel 2.  I see the same SSID name. I'll make an educated guess to say the passwords are all the same across all three. With an IP lease time of 24 hours, every 24 hours they'll cycle and try to get a new IP. Given they look for SSID/password matches instead of RSSI strength, they will connect to whichever comes "first" so to say.

 

In the meantime, is there a way to just release the IP from the network administration so that my static device can reclaim it? In other words, is there a quick and easy way from the network administration access to fix this every time it happens?

 

 

2 Replies

    • boojiboy71's avatar
      boojiboy71
      Aspirant
      Jun 01, 2022

      Thank you. Previously I had tried doing something like this in network administration and for what ever reason, my router began blocking IP addresses on my network seemingly randomly. I couldn't fix it, and had to set my entire system settings back to factory default.

      I don't know why that happened, but am a bit hesitant to try it again at this point.