NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
tanyero
Sep 04, 2024Aspirant
Unable to access NAS 104 connected to Orbi RBR850
I am unable to access the web console, SMB shares, nor ping my ReadyNAS 104 when my Orbi RBR850 is in Router mode, either via static or DHCP assigned IP. In previous setup - which was FTTN (ISP -...
- Sep 07, 2024So it turns out the Orbi doesn't like 172.16.10.x. When you click Apply the router restarts with no warning or message and it switches back to 172.168.10.x. This is likely where my troubles began and I didn't notice it; too busy focusing on the NAS..
Opted to choose another private IP addressing range which the Orbi accepted. Updated the NAS and all connectivity restored.
Cause: RBR850 didn't like 172.16.10.X for its IP and DHCP scope. Defaulted to 172.168.10.X. Changed to another private IP addressing.
tanyero
Sep 06, 2024Aspirant
You would be correct! They directed me to post here 🙂 Will hopefully try those options tonight.
For all those playing at home I am in GMT+8:00 timezone.
tanyero
Sep 06, 2024Aspirant
So, it turns out I was having a big dumb-dumb moment. It pays to walk away from a problem and look at it again with fresh eyes.
I found a typo in the NAS IP address allocation. 172.16.10.X when the DHCP and router scope is 172.168.10.X. This will explain why the NAS was appearing in the connected device list and briefly dropping off again.
I suspect the DHCP address was correct, and I was just trying to PING the incorrect address range of 172.16.10.X.
Had two options, configure the RBR850 to 172.16.10.0/24 to match the NAS, or connect the NAS eth1, log in via it's DHCP assigned port, and correct the static IP on eth0 to 172.168.10.0/24. I chose the latter.
As you'd expect, device connectivity restored and can see it in the Orbi app.
Clearly, I need a holiday.
- StephenBSep 06, 2024Guru - Experienced User
tanyero wrote:
Had two options, configure the RBR850 to 172.16.10.0/24 to match the NAS, or connect the NAS eth1, log in via it's DHCP assigned port, and correct the static IP on eth0 to 172.168.10.0/24. I chose the latter.
.
You took the wrong path. 172.16.0.0–172.31.255.255 (172.16.0.0/12) is reserved for private IP addressing. So it is not routable over the public internet, and there are no publicly assigned IP addresses in that range.
172.168.10.x is currently assigned to Microsoft's Azure Cloud, and if you use that on your LAN then you will end up not being able to connect to anything in their cloud that uses these addresses. That could potentially bite you later on.
Normally Orbi will default to a subnet that is reserved for private addressing, so I think you must have manually entered that subnet when you set up the Orbi.
Also, I'd use DHCP with an IP address reservation in the Orbi, instead of configuring a static IP on the NAS. There are several reasons why.
- One is that if you had done that before, you wouldn't have lost connectivity to the NAS when you changed the router setup. You would have lost the IP address assignment, but that is easier to fix than losing connectivity
- Another is that it puts all your assigned addresses in one place. That makes it much easier to make sure there are no address conflicts, and it also ensures that you can easily see all the assigned addresses.
- tanyeroSep 06, 2024AspirantApologies - I did mean the former (original intended 172.16.10.X).
- tanyeroSep 07, 2024AspirantSo it turns out the Orbi doesn't like 172.16.10.x. When you click Apply the router restarts with no warning or message and it switches back to 172.168.10.x. This is likely where my troubles began and I didn't notice it; too busy focusing on the NAS..
Opted to choose another private IP addressing range which the Orbi accepted. Updated the NAS and all connectivity restored.
Cause: RBR850 didn't like 172.16.10.X for its IP and DHCP scope. Defaulted to 172.168.10.X. Changed to another private IP addressing. - StephenBSep 07, 2024Guru - Experienced User
tanyero wrote:
So it turns out the Orbi doesn't like 172.16.10.x. When you click Apply the router restarts with no warning or message and it switches back to 172.168.10.x. This is likely where my troubles began and I didn't notice it; too busy focusing on the NAS..Was 172.16.10.x used by the upstream router?
If not, then this should be reported in the Orbi forum.
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!