WebJun 16, 2010 · In response to salwayasalam. 06-23-2010 07:18 AM. Like Andrew said, you can't ping a far side interface on an ASA. It will fail everytime. (inside->dmz, inside->outside) We're talking about the actual interface on the ASA, not what's on the other side. WebNov 12, 2024 · While it might seem logical to assume that the safest practice is to not enable DNS requests on the outside interface you should be aware that some functions on ASA require DNS: Some ASA features require use of a DNS server to access external servers by domain name; for example, the Botnet Traffic Filter feature requires a DNS server to …
unable to ping outside interface of ASA - Cisco
WebOct 21, 2024 · So you are actually pinging from outside/external network to inside/internal, not the other way around. Obviously this is a packet tracer lab and not a production network, but is 172.16.1.0 network routable from the outside? Does the next hop of 204.0.1.0 know how to reach 172.16.1.0 network (are there routes define on each hop)? WebThe thing that won't work in ASA is pinging the outside interface ip address from any host in the inside network. Example: ASA outside ip: 1.1.1.1/24 ASA inside ip: 2.2.2.2/24 If you try to ping the ip address 1.1.1.1 from any of your inside hosts in the network 2.2.2.0/24 it won't work, and that is one of those default behavior of ASA. common bond of australia
unable to ping outside interface of ASA from inside network - Cisco
WebAug 3, 2024 · The ASA only responds to ICMP traffic sent to the interface that traffic comes in on; you cannot send ICMP traffic through an interface (outside) to a far interface … WebOct 8, 2024 · FMC has to manage the FTD device via a dedicated management interface. The outside data path interface cannot do dual-duty in that respect. Most people end up using one of two options: 1. Stage the device at your main site with the policies necessary to translate the management address or carry it via site-site VPN when deployed remotely, … WebAssuming that you are already able to ping ASA g0/1 interface from the R2 sourcing from R2 192.168.1.2 interface, I would think about some routing issue on ASA unless you applied some access lists on ASA inside interface that allows only the traffic coming from 192.168.1.2 ip address, so please post the output of the following commands for review: common bond nyc