Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have 2 SonicWall devices (tz100) in 2 different geographical locations. They are connected to each other using site-to-site vpn connection and this works just great.

Device A network -

Device B network -

When I connect to one device, I can access, from my computer, anything on that specific subnet. However, I am unable to view anything, from my computer, on the other network. Is there a setting somewhere that will forward my requests to the other subnet?

Example - I VPN into Device A, but would like to get to a server which is on the Device B network (

share|improve this question

On the Sonicwall you VPN to, you need to create an address object for the remote subnet, and then under VPN add that as an allowed network the VPN user can access.

share|improve this answer

Most VPN software isn't captive. Meaning if you VPN to a remote network B then it will add a route only for that specific remote subnet. Likely it will also add a virtual IP for that network. So if you do a route print from the command prompt, you'll see a route similar to:

Network Destination: Netmask: Gateway: Interface Where .25 is your VPN virtual IP.

What this means is that any traffic destined for will go through the VPN and everything else (including destination 192.168.1.X) will just go to your default gateway and not reach either remote site. Then your ISP will just drop any packets that have a 192.168.1.X destination.

What you want is for both subnets to route through the VPN. Usually you can change this in the VPN client software (remote networks is the common term). Alternatively you can add a route that will tell your computer to use the VPN for both remote networks.

route add mask

So now all traffic destined for will be sent through the VPN rather than out to the internet. So it should hit your router at site B and then be sent through your site-to-site VPN to site A.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.