<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: pinging device while vpn'd in in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pinging-device-while-vpn-d-in/m-p/1258083#M834796</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my experience, issues like this usually tie back to a routing problem. I've had similar issues where the echo request reaches the target but it is the reply that cannot find its way back to the VPN client. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest first getting packet captures throughout the topology and find what is being dropped (request or reply) and where it is being dropped. Once you know this, you can look for log or debug messages that explain why the packet is dropped and troubleshoot from there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 17 Jun 2009 14:34:15 GMT</pubDate>
    <dc:creator>robertson.michael</dc:creator>
    <dc:date>2009-06-17T14:34:15Z</dc:date>
    <item>
      <title>pinging device while vpn'd in</title>
      <link>https://community.cisco.com/t5/network-security/pinging-device-while-vpn-d-in/m-p/1258082#M834793</link>
      <description>&lt;P&gt;All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I've noticed that I can't ping a public device (on my block) from the vpn. The vpn is NOT my firewall, but another ASA (5520). The inside interface on the ASA is on my private side. From a host on the lan and not on vpn, I can ping this device. The path the packet would take is from:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;host -&amp;gt; core switch -&amp;gt; asa5550 -&amp;gt; packetshaper -&amp;gt; fatpipe -&amp;gt; device to ping&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above works. The path vpn would take is:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;asa5520_vpn -&amp;gt; core switch -&amp;gt; asa5550 -&amp;gt; packetshaper -&amp;gt; fatpipe -&amp;gt; device&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The above doesn't work. From the vpn, I can ping all the way to the ASA5550 and it works fine, but nothing past it.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks!&lt;/P&gt;&lt;P&gt;John&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 15:42:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-device-while-vpn-d-in/m-p/1258082#M834793</guid>
      <dc:creator>John Blakley</dc:creator>
      <dc:date>2019-03-11T15:42:15Z</dc:date>
    </item>
    <item>
      <title>Re: pinging device while vpn'd in</title>
      <link>https://community.cisco.com/t5/network-security/pinging-device-while-vpn-d-in/m-p/1258083#M834796</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;John,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In my experience, issues like this usually tie back to a routing problem. I've had similar issues where the echo request reaches the target but it is the reply that cannot find its way back to the VPN client. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest first getting packet captures throughout the topology and find what is being dropped (request or reply) and where it is being dropped. Once you know this, you can look for log or debug messages that explain why the packet is dropped and troubleshoot from there.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;-Mike&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 17 Jun 2009 14:34:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pinging-device-while-vpn-d-in/m-p/1258083#M834796</guid>
      <dc:creator>robertson.michael</dc:creator>
      <dc:date>2009-06-17T14:34:15Z</dc:date>
    </item>
  </channel>
</rss>

