Readynas Pro cannot access across subnet

in order for any device to connect to anything outside it's own subnet, it has to go through a gateway (ie a router).

it sounds like either your gateway is not correct, or you need to make the nas subnet mask bigger ie 255.255.0.0 instead of 255.255.255.0

192.168.10.2 (nas) is outside the subnet range assuming its 255.255.255.0 for the domain server @ 192.168.9.101

you need a gateway on the 192.168.10.x network that has a route to the 192.168.9.x network.

or put the nas itself directly on the 9.x network.

Thanks for the reply Tekno.

I setup a route on the Pro to specify traffic for 9.x to go via the router (10.1) but it didnt help, still unable to ping from the 9.x network.

The gateway on the NAS is correct (192.168.10.1) - so should I change the subnet mask on the NAS to be 255.255.0.0 instead of 255.255.255.0 ?

Ok, I changed the subnet mask on the NAS to 255.255.0.0 but it didnt help.

From the 9.x network I can tracert to a PC on the 10.x network ok, but when I try to tracert to the NAS it gets as far as the 10.1 router and then times out. Im sure all the networking is ok I just dont know why the NAS isnt communicating across the subnet. Having the default gateway set on the NAS should take care of everything (ie the router does the VPN connection so it knows how to route between the two networks).

Unfortunately there is no ping type test tool on the NAS to see if it can ping the 9.x network.

Any other suggestions?

Thanks

Ryan

Ok its working!

I changed the subnet on the NAS back to 255.255.255.0

BUT I believe the problem was someone had setup a Bind-IP-to-MAC on the router to reserve the IP for the NAS, like a DHCP reservation, the NAS has a fixed IP so this isnt needed and seemed to break connectivity some how.

Thanks for your help.