NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
router not seeing devices on upstream router
I replaced a failing ancient Cisco wifi in the shed with a RAXE500 Wifi router. It is connected via ethernet to another router in the home which also has a NAS connected to it. Previously, the old wifi router connected to a local router which then connected to the router in the home. Since the RAXE500 has several ethernet ports on it I thought I could eliminate the local router. However when I do I am unable to map the upstream NAS as a network drive. I have internet connection and can connect to the NAS administration interface via the browser through the RAXE500 but I cannot see the volumes on File Explorer or map it as a network drive. If I put the old router back in so the computer connects to the house through that instead it works. I would love to eliminate the extra router. Any idea how to get the RAXE500 to see the upstream NAS? Everything is on the name network (192.168.0.x). I mapped the NAS to port 8080 if that has anything to do with it. Suggestions?
Thank you for your responses. The solution that worked for me was to change the router to AP mode (ADVANCED-->Advanced Setup-->Wireless AP). Just an FYI for anyone else landing here, although it is called "Wireless AP mode" it does appear, in fact, to apply to the wired connections as well.
7 Replies
- Router after router causes often a double NAT situation, where you have 2 LANs that can't talk to each others. It's not clear from your post if you're in this situation. If you are, read the link below how to resolve it.
https://kb.netgear.com/30186/What-is-double-NAT-and-why-is-it-bad
TjckTock wrote:
I replaced a failing ancient Cisco wifi in the shed with a RAXE500 Wifi router. It is connected via ethernet to another router in the home which also has a NAS connected to it.
microchip8 has already pointed to the most probably cause of the symptoms you see.
Then there is the modem, ONT, gateway of whatever connects you to the Internet. These can also be combination devices with their own routers, adding another layer of complexity. So it might help to tell people what that device is on your network.
Thank you for your responses. The solution that worked for me was to change the router to AP mode (ADVANCED-->Advanced Setup-->Wireless AP). Just an FYI for anyone else landing here, although it is called "Wireless AP mode" it does appear, in fact, to apply to the wired connections as well.
TjckTock wrote:
Thank you for your responses. The solution that worked for me was to change the router to AP mode (ADVANCED-->Advanced Setup-->Wireless AP). Just an FYI for anyone else landing here, although it is called "Wireless AP mode" it does appear, in fact, to apply to the wired connections as well.
That's the classic solution to double-NAT conflicts.
It is what Netgear recommends:
What is Double NAT? | Answer | NETGEAR Support
Just an FYI for anyone else landing here, although it is called "Wireless AP mode" it does appear, in fact, to apply to the wired connections as well.Yes. Strange isn't it?
I also thought I'd note a few other things that may help other folk with similar issues:
- Sorry, I lied in the first post. I thought I had everything on the same subnet but the router had switched the local subnet back to 192.168.1.x. This is, no doubt, the fundamental issue since the NAS is on 192.168.0.x. On the previous router I was able to limit the upstream DHCP to IPs .0.x where x is limited to 0-199 and the local DHCP IPs to the same .0.y where y is 200-255 so they shared the same subnet. The RAXE500 seems to have it a hard limitation that the local subnet must be different then the upstream network (you get an "IP address conflicts with WAN subnet" error if you try to force them the same). You can constrain the addresses to a subset of the full 0-255 but it still requires the local subnet to be different.
- In my research I found some posts suggesting AP mode doesn't perform as well as full featured mode. However, it appears to be working great. I got the RAXE500 for the 6G performance to use with an Oculus Quest VR headset in wireless link mode which requires a LOT of bandwidth. My prior 2.4G Cisco was terrible/unusable and I was forced to use the headset wired for desktop games (which is very annoying). However the wireless mode works great with the RAXE500 with no perceivable stutter or performance loss in both AP mode and normal mode.
- The literature I found says you will lose a some features in AP mode including the guest wifi account. However, the guest wifi account is still available.
- I tried the advanced ("old school") method suggested here but only managed to lock up the router forcing a factory reset.
TjckTock wrote:
The literature I found says you will lose a some features in AP mode including the guest wifi account. However, the guest wifi account is still available.
Disabled Features on the Router when set to AP Mode | Answer | NETGEAR Support
