Then from the VPN Client, try to see if you can ping the ASA inside interface (126.96.36.199).
If you can, then that's good.
You would need to check the host that you are trying to ping to see if the default gateway is the ASA inside interface (188.8.131.52) and also there is no personal firewall, etc on the host that might be preventing inbound access.
I have a similar problem. I have 1 user able to log in to the ipsec-ra VPN using the cisco VPN client and access the servers, but another user is not able to access the servers. Did you manage to solve the problem ? If yes, what did you do ?
Listen: https://smarturl.it/CCRS8E47 Follow us: twitter.com/ciscochampions
Ransomware, fileless malware, and zero-day attacks continue to target organizations around the world. In response, organizations have resorted to deploying a variety of d...
This is a general information page for Cisco Threat Centric (TC-NAC) with ISE
Threat Centric Network Access Control (TC-NAC) feature enables you to create authorization policies based on the threat and vulnerability attributes received from the th...
The 2021 IT Blog Awards, hosted by Cisco, is now open for submissions. Submit your blog, vlog or podcast today. For more information, including category details, the process, past winners and FAQs, check out: https://www.cisco.com/c/en/us/t...
Cisco Secure Endpoint (formerly AMP for Endpoints) will decommission legacy cloud servers, which results in Legacy Windows Connector Versions 3.x/4.x and Mac Connector Version 1.0.x ceasing to ...
IntroductionRequirementsWhat problem does CSDAC solve?CSDAC ComponentsConfiguration CSDAC Login Connector AdaptersCSDAC WorkflowFMC Policy Configuration with Dynamic ObjectsUse Case: Blocking IP address using dynamic object without a policy push