IP conflicts with RBR750

---

BulletRouge wrote:

SO, my new AX4200 config (router & 2 nodes) is a mess. Before I set it up, I changed my existing setup to lease IP addresses < 130, and waited for everything to have an IP address in that range before I did anything. Then I updated firmware all around, and did a factory reset before setting it up. Then before I let any devices connect to the Orbi network I changed DHCP to be > 130. then I let everything connect and virtually everything got new IP addresses. Then the problems began...

---

Devices control how they reset their network IP address assignments.  If you change the DHCP settings in your router to use different IP ranges, you may need to restart each device to force it to acquire a new DHCP address.  Old assignments causing IP address conflicts can occur but this is not necessarily an Orbi issue.

Also, why are you changing the IP address range in your Orbi?  Are you also setting up some devices with static IPs?  That is another way to create IP address conflicts unless done carefully and correctly.  My recommendation is to stick with DHCP address reservations for all your devices but configure them in the Orbi to be "reserved" so they are unlikely to change.  For best results, after configuring your Orbi IP address ranges force a reset or reboot of every device so they get a fresh, and current, DHCP address from the Orbi.

---

BulletRouge wrote:

I went to the Netgear admin UI to look at the connected devices and it showed a completely different device on that IP address.

---

Also, the Orbi admin website is usually pretty accurate but I don't trust the app as much as the admin website.  In this case, did you reset/reboot the conflicting device so it gets a fresh IP address?  The problem seems that it was using an older address but should be able to get a new and non-conflicting one.

What Firmware version is currently loaded?
What is the Mfr and model# of the Internet Service Providers modem/ONT the NG router is connected too?

So does the RBR and system work if you don't change the IP address range? 

What range are you using? 192.168.1.2 thru .130? 

I currently use 192.168.0.100 to .150 and don't see DHCP issues. Having ranges on either side of this default DHCP pool size leaves me room for static assigned devices. Everything with in the pool can be reserved IP assigned. 

Be sure that when you set a new pool size, that you reboot ALL ther devices as well after the RBR configuration is applied. Be there are no static assigned IP addressed devices with in your new pool size. 

---

BulletRouge wrote:

SO, my new AX4200 config (router & 2 nodes) is a mess. Before I set it up, I changed my existing setup to lease IP addresses < 130, and waited for everything to have an IP address in that range before I did anything. Then I updated firmware all around, and did a factory reset before setting it up. Then before I let any devices connect to the Orbi network I changed DHCP to be > 130. then I let everything connect and virtually everything got new IP addresses. Then the problems began...

 

My wife yelled that our streaming device was pausing repeatedly. I checked the devie's IP address, and it was new. I rebooted the device for good measure. Same IP address. I went to the Netgear admin UI to look at the connected devices and it showed a completely different device on that IP address.

 

I was having the same issue on another streaming device, and same pattern. The IP address was showed as being assigned to a completely different device.

 

I have no other router or any kind on my network. I've had to swap back to my previous setup and everything is rock solid again...

 

Before I return it, any ideas??

---