NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
Windows Access to my NAS with a Orbi - Cable Model setup
Looking for some help in correctly configuring my Orbi to access my NAS from a Windows PC.
My Setup is ISP Cable Modem to my Orbi. My NAS is attached to my Cable modem
I can access my NAS via the web interface.
What I can't do:
- Connect a webcam to the NAS for my security setup
- Map a network drive
- The NAS' admin app on my Windows 10 laptop does not discover my NAS.
If I change my Orbi to AP mode all of the above work. I tried playing with the DHCP setting and the router's IP adress but I get an IP conflict message.
What I'm looking for is the Orbi in Router mode to do all of the above and benefit from all the router's capabilities.
Any help is well appreciated!
> >> IP Address 192.168.0.14, Connection DHCP, IP Subnet Mask
> 255.255.255.0, [...]> >> 192.168.1.1, subnet 255.255.255.0, use router DHCP, starting .2
> ending .254.Ok. Your main (outer) router is using "192.168.0.*" for its LAN, and
the Orbi (inner router) is using "192.168.1.*" for its LAN.> >> found the option to assign a fixed IP.
Did you stick with the ".14" address, or choose something more
memorable? It's your choice. I'll assume ".14" here, but you could
pick another.Now all you need to do is find where/how to specify a static route on
your main router. The static route spec (on the main router) for this
situation should look something like this:
Destination IP Address: 192.168.1.0
IP Subnet Mask: 255.255.255.0
Gateway IP Address: 192.168.0.14You may also need to specify a "Metric". I'd pick "1", but on a
Netgear router, "2" might be as small as it lets you use. (Or your
Selligent, I know nothing.) With one extra route, it may matter little.An equivalent notation for "destination: 192.168.1.0, subnet mask:
255.255.255.0" would be "192.168.1.0/24".What that tells the main router is that a message with a destination
address of "192.168.1.x" (0 <= x <= 255) should be sent to
"192.168.0.14" (the Orbi WAN/Internet interface), instead of to its
usual default destination (your ISP).
The Orbi (inner router) doesn't need any special instruction,
because, by default, it sends anything foreign-looking out its
WAN/Internet interface, which goes to your main router. Your main
router already knows what to do with any destination on its own LAN
("192.168.0.*"), and anything else should be sent to your ISP.What could go wrong?
8 Replies
> My Setup is ISP Cable Modem to my Orbi. My NAS is attached to my Cable
> modemHas your (unspecified) "ISP Cable Modem" a maker and model number?
Is it a simple "Modem", or is it actually a modem+router?Has your (unspecified) "My NAS" a maker and model number?
> I can access my NAS via the web interface.
You can access it from _where_?
> What I can't do: [...]
"can't" is not a useful problem description. It does not say what
you did. It does not say what happened when you did it. As usual,
showing actual actions (commands) with their actual results (error
messages, LED indicators, ...) can be more helpful than vague
descriptions or interpretations.
> If I change my Orbi to AP mode all of the above work. [...]That suggests (strongly) that your (unspecified) "ISP Cable Modem" is
actually a modem+router, and cascading multiple routers can create
multiple LAN subnets, which can cause problems like these. Have you
looked at the IP addresses of your devices in both of those
configurations? Try it. See the difference(s)?> What I'm looking for is the Orbi in Router mode to do all of the above
> and benefit from all the router's capabilities.Then configure your (unspecified) "ISP Cable Modem" as a modem-only
("bridge mode"), and let the Orbi-as-router be your only router.Note, however, that that means that you won't be able to do "My NAS
is attached to my Cable modem". All your client devices will need to be
connected to your (one/only) router, not to your (now) only-a-modem.It's a Siligence TCG300. Modem + router. My NAS is a Synology DS418Play. The Silligence is in my garage, connectivity to the rest of my house is unreliable. Hence the Orbi, connected by cable to my Silligence.
I access my NAS on my Windows 10 laptop's Firefox browser. IP 192.168.0.259.
All my home devices are connected through Wifi on my Orbi, except the NAS. The Orbi sits in my living room and the NAS is to noisy to sit next to the Orbi & be connected to it. I left it in the garage connected by cable to the Silligence.
The other reason I left my NAS in the garage attached to the cable modem is that I use the NAS' Surveillance app and it's iphone app. the mobile app needs external access to my NAS. I tried in the past moving the NAS to my Orbi in Router router, but then the setup with port-forwarding didn't work.
When my ORBI is in Router mode:
- Synology's DS Assistant (Windows 10 app) doesn't find my NAS. Windows Explorer doesn't either. Any of my Windows app can not therefore open or save files from/to my NAS.
- My IP camera is connected to the Orbi Wifi. In router mode, it can not connect to my NAS' Surveillance app anymore
On the other hand, if I set my Orbi in AP mode, DS Assistant finds my NAS, I can map network drives, Windows 10 apps can open or save files to/from my NAS, my IP camera is connected to my NAS Surveillance AP and external access to my NAS works properly. But, I can't use any of the Orbi's built in Router/security features. The Silligence device does not support a lot of security features except some basic firewall capabilities.
Hope that clarifies my challenge and why I'm keen on knowing of there is a way to configure my Orbi in Router mode all the while being able to make the above work properly :-)
The Silligence can not be configured in Bridge mode. I've looked it up in various forums.
My question remains, a) is it possible to change settings on my Orbi, in Router mode, to do what I want and b) if it is, provided I share more specifics of IP adresses & setup detail, can you help pointing out what settings I need to adjust?
Appreciate your time & help.
> The Silligence can not be configured in Bridge mode. I've looked it up
> in various forums.If that's true, then that's unfortunate.
> All my home devices are connected through Wifi on my Orbi, except the
> NAS. [...] I left it in the garage connected by cable to the
> Silligence.As a (modem+)router, the Silligence has its own LAN subnet, and, as a
router, the Orbi has its own LAN subnet, making it difficult to do
everything you want to do.> [...] the mobile app needs external access to my NAS. I tried in the
> past moving the NAS to my Orbi in Router router, but then the setup with
> port-forwarding didn't work.When the NAS is connected to the Silligence, do you configure port
forwarding for it on the Silligence?
I wouldn't bet on it, but, if the Silligence has an option for a DMZ
server, then you might try configuring the Orbi-as-router as that DMZ
server. To make that work, you'd need to fix the WAN/Internet IP
address of the Orbi; either reserve a dynamic address for it on the
Silligence, or manually configure it with a static address (on the
Silligence LAN, outside the Silligence DHCP pool). And connect the NAS
to the Orbi-as-router.Another possibility on which I wouldn't bet would be to configure
the port forwarding on the Silligence to point to the Orbi-as-router,
and configure port forwarding on the Orbi-as-router to point to the NAS.
Again, the Orbi-as-router would need a fixed WAN/Internet IP address,
and the NAS would be connected to the Orbi-as-router).
Another possibility would be to try to live with multiple subnets,
and leave the NAS connected to the Silligence. For that to work, you'd
need to add a static route to the Silligence, which would tell it to use
the Orbi-as-router as a gateway to the LAN subnet of the Orbi-as-router.
Again, the Orbi-as-router would need a fixed WAN/Internet IP address.
You might need to do some extra work to get your Windows system to find
the NAS when it's on the Silligence LAN, because I wouldn't expect the
usual broadcast announcements to make it from one subnet to the other.