ping remote host behind asa 5505 across vpn tunnel

I have a site to site vpn setup between my pix515 (corporate) and an ASA5505 (remote office). From the ASA side I can ping hosts at my corporate office, but from the pix side (corporate office) I am unable to ping any hosts behind the ASA.

Corporate network behind the PIX -

network behind the ASA -

Who is Participating?
lrmooreConnect With a Mentor Commented:
Looks like the host has a firewall enabled because the firewall is doing exactly what is expected.
This is probably a problem with an access-list, or lack there-off...

If you connect to the ASDM  at the HOME tab you will find logging at the bottom of the page. I prefer setting it to log warnings to avoid getting to much "jitter" and then try a ping. If it gets blocked you should get a pretty good idea of what is blocking the traffic.
dtadminAuthor Commented:
I don't have ASDM installed on the pix. Below is my nonat access list

access-list nonat-vpn line 1 extended permit ip any
access-list nonat-vpn line 2 extended permit ip
access-list nonat-vpn line 3 extended permit ip
access-list nonat-vpn line 4 extended permit ip  
access-list nonat-vpn line 5 extended permit ip
access-list nonat-vpn line 6 extended permit ip
access-list nonat-vpn line 7 extended permit ip
The Lifecycle Approach to Managing Security Policy

Managing application connectivity and security policies can be achieved more effectively when following a framework that automates repeatable processes and ensures that the right activities are performed in the right order.

Are you using EasyVPN, or straight vpn tunnel?
If the PIX is a easyvpn client and nem is not enabled, the we see the exact symptoms you experience because the pix actually is natting.
dtadminAuthor Commented:
straight site to site VPN tunnel.
I'd probably have to see both complete configs to spot anything.
Do you have any access-lists applied to the inside interface of either the asa or the pix?
Perhaps you have icmp echo blocked at the asa, or the echo-reply blocked at the PIX?
Pinging one way validates routing and encryption.
One way ping usually indicates an access rule or software firewall on the pc you are trying to ping.
Some things enable a firewall that you would not expect. Cisco VPN client, for example, can enable a firewall whether you are using it or not.
dtadminAuthor Commented:
here is what the asdm logging on the asa is seeing:

6      Oct 02 2008      08:18:17      302020       Built outbound ICMP connection for faddr gaddr laddr

6      Oct 02 2008      08:18:17      302021       Teardown ICMP connection for faddr gaddr laddr

looks like the asa is seeing the ping from my pc behind my corporate firewall, but it's not letting it through to the inside hosts.
dtadminAuthor Commented:
nevermind that was the wrong log....standby
dtadminAuthor Commented:
6      Oct 02 2008      08:18:17      302020       Built inbound ICMP connection for faddr gaddr laddr

6      Oct 02 2008      08:22:49      302021       Teardown ICMP connection for faddr gaddr laddr

here we ip is and the host behind the asa that I'm unable to ping is
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.