<?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: Remote VPN client - Pix, cant ping inside network in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/remote-vpn-client-pix-cant-ping-inside-network/m-p/703378#M1023963</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Problem solved with "isakmp nat-traversal"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Tue, 06 Mar 2007 11:34:56 GMT</pubDate>
    <dc:creator>lamin.sonko</dc:creator>
    <dc:date>2007-03-06T11:34:56Z</dc:date>
    <item>
      <title>Remote VPN client - Pix, cant ping inside network</title>
      <link>https://community.cisco.com/t5/network-security/remote-vpn-client-pix-cant-ping-inside-network/m-p/703377#M1023962</link>
      <description>&lt;P&gt;I have a VPN client try to connect to a PIX 515. I can connect from all sites, but can only ping internal devices from some locations. In both cases I get an ip address, GW, DNS. Both of the locations I'm trying use  NAT/PAT (behind some firewall). I have looked in some other forum notes, there they recommed  "isakmp nat-traversal". Is this a possible solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Config:&lt;/P&gt;&lt;P&gt;access-list VPN permit ip 172.16.16.0 255.255.255.0 192.168.40.0 255.255.255.0&lt;/P&gt;&lt;P&gt;ip address inside 172.16.16.2 255.255.255.0&lt;/P&gt;&lt;P&gt;ip local pool VPNKLIENTER 192.168.40.100-192.168.40.150&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;nat (inside) 0 access-list VPN&lt;/P&gt;&lt;P&gt;nat (inside) 1 172.16.0.0 255.255.0.0 0 0&lt;/P&gt;&lt;P&gt;sysopt connection permit-ipsec&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;isakmp enable outside&lt;/P&gt;&lt;P&gt;isakmp key xxxxx&lt;/P&gt;&lt;P&gt;isakmp identity address&lt;/P&gt;&lt;P&gt;isakmp policy 9 authentication pre-share&lt;/P&gt;&lt;P&gt;isakmp policy 9 encryption des&lt;/P&gt;&lt;P&gt;isakmp policy 9 hash md5&lt;/P&gt;&lt;P&gt;isakmp policy 9 group 1&lt;/P&gt;&lt;P&gt;isakmp policy 9 lifetime 1000&lt;/P&gt;&lt;P&gt;isakmp policy 10 authentication rsa-sig&lt;/P&gt;&lt;P&gt;isakmp policy 10 encryption des&lt;/P&gt;&lt;P&gt;isakmp policy 10 hash sha&lt;/P&gt;&lt;P&gt;isakmp policy 10 group 1&lt;/P&gt;&lt;P&gt;isakmp policy 10 lifetime 86400&lt;/P&gt;&lt;P&gt;isakmp policy 20 authentication pre-share&lt;/P&gt;&lt;P&gt;isakmp policy 20 encryption des&lt;/P&gt;&lt;P&gt;isakmp policy 20 hash md5&lt;/P&gt;&lt;P&gt;isakmp policy 20 group 2&lt;/P&gt;&lt;P&gt;isakmp policy 20 lifetime 86400&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;vpngroup vpnklienter address-pool VPNKLIENTER&lt;/P&gt;&lt;P&gt;vpngroup vpnklienter dns-server  172.16.16.22&lt;/P&gt;&lt;P&gt;vpngroup vpnklienter wins-server martin5 172.16.16.2&lt;/P&gt;&lt;P&gt;vpngroup vpnklienter idle-time 86400&lt;/P&gt;&lt;P&gt;vpngroup vpnklienter password xxx&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 09:42:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/remote-vpn-client-pix-cant-ping-inside-network/m-p/703377#M1023962</guid>
      <dc:creator>lamin.sonko</dc:creator>
      <dc:date>2019-03-11T09:42:20Z</dc:date>
    </item>
    <item>
      <title>Re: Remote VPN client - Pix, cant ping inside network</title>
      <link>https://community.cisco.com/t5/network-security/remote-vpn-client-pix-cant-ping-inside-network/m-p/703378#M1023963</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Problem solved with "isakmp nat-traversal"&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 06 Mar 2007 11:34:56 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/remote-vpn-client-pix-cant-ping-inside-network/m-p/703378#M1023963</guid>
      <dc:creator>lamin.sonko</dc:creator>
      <dc:date>2007-03-06T11:34:56Z</dc:date>
    </item>
  </channel>
</rss>

