NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
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 -> DSL modem -> RBR850 in AP mode) I was able to access the ReadyNAS OK. I suspect I connected the NAS to the DSL modems LAN port and was using the DSL modem for DHCP.
I am now FTTC (NBN Box -> RBR850 in Router mode) and connecting the RN104 to a LAN port on the RBR850. I can see it connected in the devices list with its static IP, and if I switch to the second ethernet port on the NAS I can see it receiving a DHCP address from the RBRB850.
If I reconnect to the old DSL modem I can access the NAS again. Both this modem and the RBR850 are configured the same for their LAN and DHCP settings (so it's not an incorrect IP/subnet issue). Further I can see the RBR850 issuing the NAS a DHCP address on its second port (one configured static IP, the other DHCP).
However, I can't ping, or access the web console, nor the SMB shares on the NAS. What is missing in the RBR850 to allow this connectivity? The RAIDar utility can also see the NAS.
I suspect if I setup NBN Box -> third-party router -> RBR850 in AP mode and connect the RN104 to the third-party router it will work, but I don't want to have an extra device.
Am I missing something obvious?
- 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..
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.
12 Replies
tanyero wrote:
I am now FTTC (NBN Box -> RBR850 in Router mode) and connecting the RN104 to a LAN port on the RBR850. I can see it connected in the devices list with its static IP, and if I switch to the second ethernet port on the NAS I can see it receiving a DHCP address from the RBRB850.
However, I can't ping, or access the web console, nor the SMB shares on the NAS. What is missing in the RBR850 to allow this connectivity? The RAIDar utility can also see the NAS.- Is the NBN box functioning as a router? (No NBNs in the US, so I have no hands-on experience with them).
- Is your client connecting to the RBR850 network? Or is it possibly connecting to the NBN wifi?.
- Did you enable access control in the advanced RBR850 settings? If you did, try turning that off.
FWIW, I double-route (ISP Router -> RBR860 in router mode). The ISP router is set to use 192.168.1.x addresses, the RBR860 is set to use 10.0.0.x. My ReadyNAS are all connected to the RBR860 (including an RN102). They all have reserved addresses in the RBR860, and all just use a single ethernet connection. This is working for me.
Access control isn't enabled - I can also see the RN10400 in the list as 'allowed'. The RBR850 also shows the NAS in connected devices list (wired). If I connect a device (laptop) wired as well, makes no difference, thinking it was a weird wireless to wired device connectivity issue.
The FTTC example below - the RBR850 is in place of the "belong modem".
I could access the NAS fine in an old household which was FTTN (example in link above). Difference was I had the RBR850 connected in AP mode connected to the DSL modem. I'm almost certain I had the DSL modem setup as the DHCP server not the RBR850, as I briefly had the same issue with it being connected to the RBR850. The NAS was connected (LAN) direct to the DSL modem instead... which I had no issues accessing. The RBR850 was providing wifi connectivity (mesh with two RBS850s), and the DSL modem wifi was disabled.
The RAIDar tool can see the NAS as well but any of the options to access the NAS (admin portal, ping) fail.
I do have another modem which I may have to setup as the router + DHCP server, and switch the RBR850 to AP mode. I can then try connecting the NAS to the router, and then back to the RBR850 and see if the issue is still present.
But trying to avoid having three devices (NBN Network Connection Device -> third-party router -> RBR850 in AP mode). When really I should be able to go (NBN network connection device -> RBR850 in router mode). Which does work for internet, IoT, etc.
Essentially the RBR is the router/gateway to access the internet, also providing wifi (mesh) for local LAN, also DHCP service, which is working for all other services except the NAS! I'm stumped!Edit: I should note all other functions appear to be working... for all connected clients (internet access, streaming services, dhcp addressing, wifi connectivity, mesh network).
tanyero wrote:
But trying to avoid having three devices (NBN Network Connection Device -> third-party router -> RBR850 in AP mode). When really I should be able to go (NBN network connection device -> RBR850 in router mode). Which does work for internet, IoT, etc.
Which basically what I am doing.
tanyero wrote:
Essentially the RBR is the router/gateway to access the internet, also providing wifi (mesh) for local LAN, also DHCP service, which is working for all other services except the NAS! I'm stumped!This should certainly be working, at least on the NIC port that is configured for DHCP.
If you have other devices on the network where you have set up static addresses (in the device, not reserved in the Orbi), then you might also want to look for an IP address conflict.
Alternatively, turn off everything but the NAS and one PC, and see if that makes any difference.
One other thing you could try is to set up a direct connect from one of the LAN ports to a PC. Bypassing the router, and setting up static addressing on both the NAS and the PC (using a different subnet from the Orbi LAN).
Then you could connect the PC to the NAS using the direct ethernet connection, and connect the NAS to the Orbi. Don't connect the PC to the Orbi (for instance with WiFi) initially/
That would allow you to do more tests - for example,
- looking at the NAS logs
- pinging other devices on the Orbi network using ssh,
- running tracert to make sure the connection topology is what you expect.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
