Hi All,
We have a new dev/test Azure subscription setup. We have verified connectivity between this new subscription and the current subscription.
What I'm having a bit of an issue with is getting the vpn connectivity from FG to this new subscription. I've verified peering and thats all set. I've added the SSL VPN subnet as a route in the route table for this new subscription, I've added the static route for this new subscription (/22) in Fortigate.
However, I am still unable to ping test VMs in this new subscription from my laptop when connected to forticlient VPN.
Is there anything that I'm missing here? Or need to modify something?
Any help would be appreciated!
Nominating a forum post submits a request to create a new Knowledge Article based on the forum post topic. Please ensure your nomination includes a solution within the reply.
Do you have the policy on the FortiGate allowing the SSL-VPN traffic into the Azure environment?
Do you have the route to the VPN client IP pool in Azure pointing to the FortiGate?
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1662 | |
1077 | |
752 | |
443 | |
220 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2024 Fortinet, Inc. All Rights Reserved.