03-09-2023 10:11 PM
Anyconnect is not able to connect to the server error!!
Firewall in BVI mode -
Solved! Go to Solution.
03-16-2023 01:31 AM
The nat rule of anyconnect is wrong. you need to exempt the vpn pool and the local subnet in order to reach the resource behind the Firewall. the rule you have it wont all you to connect the vpn AC behind the firewall.
your nat rule should be in this order. I am writing the ASA code as I dont have FTD so you can work it around.
nat(inside,outside) source static local-network local-network destin static vpn-pool vpn-pool no proxy arp route-lookup.
03-09-2023 10:38 PM
Your failure description is quite vague ...
But at least you have to make sure that the NAT-exemption rule is above the general internet rule. And I would configure this in the same logic as the "normal" NAT rule: From "any" to "outside".
03-09-2023 10:47 PM
03-09-2023 11:06 PM - edited 03-10-2023 04:00 AM
@Karsten Iwen @Sheraz.Salim @Rob Ingram This is what happened when I shift anyconnect nat to the top -
1. I can connect through anyconnect working perfectly but the second nat will stop working (OPEN-DSM).
2. I can't ping my inside network like 10.206.167.111
03-16-2023 01:31 AM
The nat rule of anyconnect is wrong. you need to exempt the vpn pool and the local subnet in order to reach the resource behind the Firewall. the rule you have it wont all you to connect the vpn AC behind the firewall.
your nat rule should be in this order. I am writing the ASA code as I dont have FTD so you can work it around.
nat(inside,outside) source static local-network local-network destin static vpn-pool vpn-pool no proxy arp route-lookup.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide