Sonicwall SSL vpn multiple sites.

Hello, currently have two different sites at opposite ends of the country. They have a site to site VPN setup so it works fine in the office, but the SSL client having a few issues with.

Site A: hosts their exchange and other programs

Site B: Uses site A: for everything except their documents.

Site A: address is 192.9.200.*
Site B: address is 192.168.40.*

Basically the SSL vpn assigns a address ranging from 192.9.200.50 - 80.

What I need to know is how do I set it up so the Site b: users can access their server on the 192.168.40 network.


Many thanks.

grizz3210Asked:
Who is Participating?
 
digitapConnect With a Mentor Commented:
that's just the subnet mask. is 192.9.200.0/24 and 192.168.40.0/24 the only subnets allowed over the vpn? what ip address do your ssl-vpn users get? if THAT ip address isn't added to the vpn policy between site A and site B, then your site B users are NOT going to be able to access their servers from the ssl-vpn connection. even if you add that to the policy of the local group on the ssl-vpn appliance.

when site B users try to access their subnet from the ssl-vpn, they'll hit the site A sonicwall which will look at the IP address their coming from. it will then look at the vpn policy. if it doesn't say that ssl-vpn users on that subnet are allowed over the vpn, then access will stop.
0
 
digitapCommented:
so, you want Site B users to connect to the ssl-vpn to site A, then access their documents on Site B servers over the vpn that's established between site A and site B?
0
 
grizz3210Author Commented:
Site B users can connect to the SSL vpn and access all of site A: (crm, email etc as this is where it is hosted), but they need to be able to access their own server for their documents which is on a different IP range.
0
Protect Your Employees from Wi-Fi Threats

As Wi-Fi growth and popularity continues to climb, not everyone understands the risks that come with connecting to public Wi-Fi or even offering Wi-Fi to employees, visitors and guests. Download the resource kit to make sure your safe wherever business takes you!

 
digitapCommented:
OK...i understand. there are two parts to this.

first, you'll need to make sure that your site to site vpn includes the subnet that your ssl-vpn users are on, if it's different from the site A LAN.

second, you'll need to add site B subnet to the ssl-vpn group Site B users are a member of. you should have a Local Group on the ssl-vpn, default or otherwise, that your Local Users are a member of. on the policies tab of the local group, you see where to Site B subnet.
0
 
grizz3210Author Commented:
The site to site vpns are fine. When they are in the office they can both access each others servers with no problems.

The SSL vpn client comes from Sonicwall site A: Site B: sonicwall is just used for the site to site vpn, not the SSL one, so when all users login be it site a or site b, they all get assigned an address from site a: consisting of 192.9.200.50-80

They can then all access everything from site A: which is fine. What I need is for them to be able to access site b: documents on the 192.168.40.0 scope when connected to the SSL vpn.

I've made sure what you said is correct, but still cannot ping the server address of site b unfortunately.

0
 
digitapCommented:
what subnets are defined to go over the vpn between site a and site b?
0
 
grizz3210Author Commented:
They both use 255.255.255.0 so not sure if that is causing the issue.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.