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.
Have an odd issue my company's helpdesk cannot solve. Figured I'd check here before reimaging, as they are out of ideas. Since my company upgraded webex to the version in subject, i have the following behavior (On windows 10 X64): I install the app...
We have a customer who will be implementing a 2110 FTD appliance at their HQ internet edge with full TMC. They have a non firepower legacy ASA at a branch location. They desire to establish a L2L VPN between the two, and backhaul 100% of the branch ...
We have a customer experiencing brute force attempts to their RDP servers form randomizing source IPs. The have ASA with FP IPS in place. Looking for options to block this. I've suggested restricting access to the RDP farm to VPN, or moving the li...
no I get that part, and we have that working. Azure has a route for 10.0.0.0/8 pointing to the vmx and all the terrestrial branches are tunneled to the VMX and working. Our issue is how to also present these same Azure servers as fixed publc ips n...
I've just deployed my first vmx in Azure and have similar frustrations. I have it working fine in passthrough mode, but my colleague doing the Azure coud config cannot figure out how to present the same Azure servers both on the tunnel and make them...
You have to configure the tunnels and nats/exemptions, crypto sets, match lists, etc on both interfaces of the head end. your remote side peers will need to specify the peer IPs of each outside interface of your headend asa in order of preference.
