NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Devices are assigned strange IP addresses and fail to connect to wifi
Hi,
Occasionally, iPhones and iPads in my wifi network start getting strange IP addresses in the range 169.255.x.x or 169.254.x.x and fail to connect to wifi. These IP addresses belong to South Africa far away from were I am (Sweden). I see that the device is trying to connect to wifi with no success (saying "no internet access") but I see that those strange addresses are assigned to the device. If I leave the device for few minutes (up to an hour sometimes) then the device will eventually connect to wifi by itself. I tried "forgetting" the wifi network and connecting again but that does not work.
This is a really irritating fault that can make devices unusable for long time!
I saw another post with the same issue as mine (https://community.netgear.com/t5/Orbi/Self-Assigned-IP-Address/m-p/1367194#M13328), but I do not have 4 satellites as in that post. I only have 1 router and 2 satellites.
Is this a fault in the Orbi's DHCP? Please advise!
Thank you,
I found out the the issue was caused by my wired mesh speakers (connected to the Satellite). Once I disconnected those speakers (connected wirelessly now), all issues disappeared.
Do you have any wired Sonos connected to Orbi?
31 Replies
- Please see attached snapshot from orbilogin
What FW is currently loaded?
What is the Mfr and model# of the ISP modem the NG router is connected too?No those addresses are not located in Aftrica, those are self assigned IP addresses to devices in which if the device didn't get a correct IP address, 192.168.x.x from the router, the device will generate it's own IP address.
Turn OFF the satellites and just connect the devices to the router. Do they connect then with a correct IP address? If so, I would set up IP address reservations for each device ON the router so that everytime they connect they get an IP address and it's the same each time they connect.
What channels are you using? Auto? Try setting manual channel 1, 6 or 11 on 2.4Ghz and any unused channel on 5Ghz.
Any Wifi Neighbors near by? If so, how many?
Try disabling the following and see:
MIMO, Daisy Chain, Fast Roaming, IPv6 and Set 20/40Mhz Coexistence to 40Mhz only. Save settings and reboot the router and satellite(s).Apple wireless issues:
Advanced Wireless Settings both 2.4GHz and 5GHz changed CTS/RTS Threshold to 2307.
https://community.netgear.com/t5/Orbi/Orbi-RBR40-RBS40-V2-1-4-16-mesh-network-drops-connection-to/m-p/1601598/highlight/true#M35230
I changed the CTR/RTS threshold values for both 2.4 GHz and 5 GHz (2341 and 2345 respectively), changed preamble modes to long preamble, and Set 20/40Mhz Coexistence to 40Mhz only.Thanks for the reply.
One thing to note is that the issue does not happen all the time, I noticed that it happens mostly after a satellite goes down. It seems like a roaming defect. somehow the router and the other satellite still think that the device is already connected to the "dead" satellite and refuse to assign an IP address to it.
Now to your questions:
- Latest FW is loaded: v2.2.0.68 in router and v2.1.4.16 for the satellites
- I have a fibre modem that I got from the ISP that has no model number but the name of the ISP
- I use fixed wifi channels: 11 and 48
- I have now tried the following changes:
- CTS/RTS Threshold set to 2307 for both 2.4 GHz and 5 GHz
- MTU size changed to 1492
- Disabled Fast Roaming and Daisy-Chain Topology
- Disabled 20/40 MHz Coexistence
I'll monitor the devices and see if this will help!
Thank you,What is the distance between the router and satellite(s)? 30 feet is recommended in between them to begin with depending upon building materials.
Was a factory reset performed on the newer FW on the router after it was loaded? Something to try if this happens again.
Ok, let us now how it goes.
What FW version are you using now?
