Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hi All
Anyconnect users in our organization can no longer access the gateway and getting the following error " Connection attempt has failed due to server communication errors .Please retry the connection ."
This has started happening with no appa...
We have a Multi context FTD3105 running ASA code version 9.22 and trying to build a site to site VPN with Azure . Can you please provide advice on the following ?
1 ) While trying to build a ROUTE based site to site vpn I was unable to create t...
Hi All,
I have a multi context FTD running ASA code and would like to peer one of the contexts to our Azure environment using a route based site to site VPN . I have created a new context solely dedicated to the VPN tunnel and configured resource...
Good Afternoon all ,
I am looking to configure my ASA in such a way that it allows some public IP ranges from the internet to access a private server residing within our internal network ( port 443 ). I would also like the the destination NAT mappi...
Hi All,I would to allow traffic from a client on the LAN ( 192.168.1.10) to google.com through an ASA version 9.22 . Considering that by default , the ASAs are set to allow traffic from Inside ( High Security Level - 100 ) to the outside / Inter...
@Rob Ingram . Thanks for the confirmation . We have implemented multi context in the past in order to meet certain requirements . Now we would like to ensure that Azure traffic can reach the networks behind those contexts . For that I have create...
@Rob Ingram The packet-tracer command is confirming that traffic is being allowed when using The NAT IP as destination . Will let test from the Internet and let you know .
Thank you for all the assistance
Do you suggest that the NAT rule I have configured nat (inside,outside) static NATIP service tcp 443 is being overshadowed by nat (inside,outside) source dynamic SERVERS interface.
ftd3105# packet-tracer input outside tcp 1.1.1.1 12345 192.168.1.1...
I have implemented the policy but it looks like it is now failing the rfp check . Does that mean that the return traffic is not using the same interface the original packets arrived on ? Please see below
Phase: 7Type: NATSubtype: rpf-checkResult: DR...