SOHO250 ISEC VPN can connect to local subnet but

bridges

hello

Im trying to setup SOHO250 IPSEC VPN and I can connect to the VPN and can access the LAN subnet - no issue there.

But I have another two sites which is connected to SOHO250 site to site vpn and can access those two remote subnet over the VPN.

Can someone please let me know what I have to enable/change so when I connect to VPN and I can access all three subnets ?

TY

MustafaA

Hi @bridges

Do you mean that you cannot access those two remote subnets with your statement "But I have another two sites which is connected to SOHO250 site to site vpn and can access those two remote subnet over the VPN."?

MustafaA

Also you are mentioning about IPSec VPN and your post is tagged as "SSLVPN". Can you add clarity please?

bridges

https://community.sonicwall.com/technology-and-support/discussion/comment/19997#Comment_19997

yes that's typo, once I connected to the VPN, I can't access the remote VPN subnet.

bridges

https://community.sonicwall.com/technology-and-support/discussion/comment/19998#Comment_19998

IPsec VPN, Im using the windows build in VPN and can connect to local subnet but can't to remote subnet.

MustafaA

There are two things that you need to keep in mind.

1. "Remote Subnet" needs to be part of the "VPN Access" for the user. The IP addresses or subnets that are under the "VPN Access" are pushed to the client as Client Routes.
2. The Remote VPN IP scope needs to be part of the negotiation if policy based site to site VPN is used. If it is route based site to site VPN then there should be a static route entry that routes the Remote VPN IP scope through the tunnel interfaces.

MitatOnge

Hi @bridges

You should do double nat configurations.

you can find out below link

https://www.sonicwall.com/support/knowledge-base/how-can-i-configure-nat-over-vpn-in-a-site-to-site-vpn/170515155805172/