NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Accessing Netgear NAS under a different subnet
Hi there,
I need some assistance in seting up in accessing the NAS under a different subnet.
Internet -> Router 1(Primary) -> Router 2 (Secondary)
Router 1 - Linksys 1900ACS (stock firmware, no dd-wrt installed)
IP - 192.168.1.1
Gateway - ISP
DHCP - Enabled
Static IP created for Router 2 - 192.168.1.115
Static route enabled to foward packets from 192.168.1.115 to 192.168.5.0 (Subnet - 255.255.255.0)
Both NAT & Firewall enabled
NAS (readynas 102) is connected under router one, IP - 192.168.1.115
Router 2 - Bipac 7800 VDOX (stock firmware)
IP - 192.168.5.1
WAN IP address - 192.168.1.115
Subnet - 255.255.255.0
WAN gateway IP - 192.168.1.1
DHCP Enabled
Both NAT & Firewall enabled
PC connected under router 2, IP - 192.168.5.2
Now I am able access internet from both subnets. Also able to ping IP address vice versa.
I pinged the NAS from PC (subnet 2) and got the reply. However under windows, window explorer does not show the sharedfolders? I also tried to map the network drive (using both either name and ip address) it failed locate the NAS.
What am I doing wrong here?
Any assistance will be greatly apperciated. I was planning to turn router 2 into a vpn router once i get the file sharing working.
16 Replies
Replies have been turned off for this discussion
NAS IP is 192.168.1.115,
The second route's WAN IP is also 192.168.1.115,
Please check your network settings.
What model NAS do you have? If it has two ethernet ports you can also connect it to both routers, which might be a better approach.
arul999 wrote:
What am I doing wrong here?
Network discovery fails because that uses broadcast LAN protocols, which can't pass through the firewall.
The NAT firewall in router 2 is blocking inbound connections from the NAS, and as far as I can tell you haven't forwarded port 445 in router 2.
FWIW, I cascade two routers (for a different reason), and the inner Netgear router supports OpenVPN (for client connections). All my equipment is connected to the inner router - I am wondering why you aren't doing that.
- Sorry made a mistake, the NAS IP address is 192.168.1.110.
Do I need to create a second route? - Thanks, so the port forwarding is done in router 1 or 2?
Router 2.
The NAT firewalls in the routers protect the "internet"->LAN traffic path. The traffic from the NAS isn't going through the internet connection on router 1, but it is passing through the "internet" connection router 2.
Thanks heaps.
As for the port forward, in the billon router which has incoming and outgoing filter pages. I assuming I need to modify only the incoming page?
I have setup as the following.
Protocol - TCP/UDP
source IP - 192.168.1.110 to ~ 192.168.1.110
Source port - 445
Destination IP - 192.168.5.0 ~ 192.168.5.254
Is this correct? still does not work.
- I have another pc connected to router which I want to access the nas too. Yes same topology when I add vpn, is there a flaw?
you should be able to connect to nas via ip \\192.168.1.110 if router 2 can be setup in ROUTER mode (not gateway mode). ie turn off NAT on router 2.
but the nas wont' show up in your windows networks because it is on a different broadcast domain.
to show up on your network neighborhood the nas needs to be on the same network and your router is separating the networks..
TeknoJnky wrote:
you should be able to connect to nas via ip \\192.168.1.110 if router 2 can be setup in ROUTER mode (not gateway mode). ie turn off NAT on router 2.
If he can turn off NAT, then that of course is an option. But even if NAT is on, he can reach it by IP address if the firewall rules are correctly configured.
But why do this with two routers in the first place?
arul999 wrote:
Yes same topology when I add vpn, is there a flaw?Well, normally this would be done with just one router - or perhaps everything connected to router 2. I don't understand why you are building your network this way.
- Thanks
If the source up is 192.128.1.110 port 445
What about the destination ip? Is this the pc ip or router 2 ip? Port 445?
I can turn off Nat in router 2
arul999 wrote:
Thanks
If the source up is 192.128.1.110 port 445
What about the destination ip? Is this the pc ip or router 2 ip? Port 445?As I said, you are forwarding to a specific PC.
Each packet sent by the NAS to the 192.128.5.x subnet will have a destination IP address of 192.168.1.115 (Router 2's WAN address), and SMB traffic will have a destination port of 445.
You need to tell router 2 what 192.168.5.x address those packets need to be routed to, because it has no way to figure that out on its own.
arul999 wrote:
I can turn off Nat in router 2Frankly, that's a much simpler approach, and it would allow any PC to reach the NAS (and vice versa) without any port forwarding.
You would still need to figure out how to manage the remote device access when you get to the VPN. But since you haven't told us what you are trying to accomplish with the VPN, I don't think we can help much on that. Likely this isn't the right forum for it anyway.
Personally I'd just use one local subnet, and depend on ReadyNAS security features and VPN access control. My own VPN is just intended for me (and immediate family) to access my home network when away. OpenVPN is built into my main router, and I just use that.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
