Menu

Join the Conversation

To sign in, use your existing MySonicWall account. To create a free MySonicWall account click "Register".

Sign In Register

Cannot access connected AWS VPC from SSL VPN clients

ASHWASHW Newbie ✭
in SSL VPN

At the office we have connected the Sonicwall to an AWS VPC where we have a SQL Server. Works great for all computers in the office.

However, traveling users who connect to the office network via Sonicwall SSL VPN cannot access those resources..

I can't figure out why. Would appreciate some guidance here.

Category: SSL VPN
Reply
Tagged:

Best Answer

  • CORRECT ANSWER
    shiprasahu93shiprasahu93 Moderator
    Answer ✓

    @ASHW,

    You can find the 6.5 section if you scroll down a bit. Since this is a route-based VPN, I am guessing the source of the route is set to Any and that includes the SSLVPN IP pool.

    On the AWS end, you would need to add routing for the SSLVPN IP pool as well as you have for your LAN network at the moment.

    Thank you!

    Shipra Sahu

    Technical Support Advisor, Premier Services

Answers

  • shiprasahu93shiprasahu93 Moderator

    Hello @ASHW,

    Welcome to the SonicWall community.

    You need to make sure that SSLVPN IP pool is part of the VPN configured to AWS and the AWS network is added in client routes and VPN access for the SSLVPN client.

    The details are given in the following KB.

    https://www.sonicwall.com/support/knowledge-base/how-can-i-allow-ssl-vpn-user-to-access-the-remote-network-across-site-to-site-vpn/170504855165239/

    Thanks!

    Shipra Sahu

    Technical Support Advisor, Premier Services

  • ASHWASHW Newbie ✭

    Thanks for your reply and link to article. (fyi: I am using SonicOS 6.5)

    I have completed steps 2 and 3 as instructed in the article, but not step 1. My VPN Policies do not contain anything in Destinations, nor do I see any place in the configuration to add Destination(s).

    Snipaste_2021-06-29_12-38-35.png


  • ASHWASHW Newbie ✭

    Yes, I used the 6.5 instructions.

    Bingo! Your last sentence there got me on the right track. I had not added the SSLVPN IP pool to the routing on the AWS side of the VPN connection. Once I did that it all worked. Thanks very much, indeed!!

  • shiprasahu93shiprasahu93 Moderator

    Perfect! Glad that things are working correctly now.

    Have a good one!

    Shipra Sahu

    Technical Support Advisor, Premier Services

  • JackofallJackofall Newbie ✭
    edited March 2022

    Hello,

    I'm in this same situation and was wondering if anyone could provide a couple extra details. I have the SSL VPN Pool set to 192.168.168.100 - 200 on the SonicWall. In AWS under the site to site vpn static routes I added a route for 192.168.168.0/24. I also made sure to add the AWS network to the SSL VPN client routes and to the SSL VPN group. I'm not sure if I'm missing something or have something configured wrong. If anyone has any thoughts I would appreciate it.

Sign In or Register to comment.