<?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: Ping Problems through Pix in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ping-problems-through-pix/m-p/423913#M533882</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I forgot to attach the config. Here it is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 25 Aug 2005 18:42:16 GMT</pubDate>
    <dc:creator>aceadmin</dc:creator>
    <dc:date>2005-08-25T18:42:16Z</dc:date>
    <item>
      <title>Ping Problems through Pix</title>
      <link>https://community.cisco.com/t5/network-security/ping-problems-through-pix/m-p/423912#M533881</link>
      <description>&lt;P&gt;We want to enable some customers that are NATed off te inside 10.0.0.0 network to be able to ping and traceroute to destinations outside the Pix. They can traverse the Pix for all other traffic, such as web and email. Customers on the public networs, like 1.1.1.0 and 2.2.2.2 are able to ping and traceroute fine. After searching the forums, I was not able to find a solution. I would greatly appreciate any advice or help you can give!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:21:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ping-problems-through-pix/m-p/423912#M533881</guid>
      <dc:creator>aceadmin</dc:creator>
      <dc:date>2020-02-21T08:21:08Z</dc:date>
    </item>
    <item>
      <title>Re: Ping Problems through Pix</title>
      <link>https://community.cisco.com/t5/network-security/ping-problems-through-pix/m-p/423913#M533882</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I forgot to attach the config. Here it is.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Brian&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 25 Aug 2005 18:42:16 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ping-problems-through-pix/m-p/423913#M533882</guid>
      <dc:creator>aceadmin</dc:creator>
      <dc:date>2005-08-25T18:42:16Z</dc:date>
    </item>
    <item>
      <title>Re: Ping Problems through Pix</title>
      <link>https://community.cisco.com/t5/network-security/ping-problems-through-pix/m-p/423914#M533885</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;have you try the command "deb icmp t"? it's easier to read through the config. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;the result of the debug should help as it outlines whether the request has been received from the pix and whether the response has been received. also the xlate will be indicated.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Aug 2005 05:52:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ping-problems-through-pix/m-p/423914#M533885</guid>
      <dc:creator>jackko</dc:creator>
      <dc:date>2005-08-26T05:52:47Z</dc:date>
    </item>
  </channel>
</rss>

