<?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 PIX VPN - Access/Routing Issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437230#M1055552</link>
    <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I currently have my pix515 (v.7x) acting as a vpn server.  My client is on a cable connection behind it's own router/firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The client can connect to the PIX vpn server just fine.  It gets it's address from a pool on the pix.  Once connected the client can connect to any server side (inside the pix) host/IP.  It can ping everything server side as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is, nothing on the server side (inside the pix) can ping or access any client host/resource.  I don't understand cause I can connect to my pix vpn via a dial up connection, not behind any kind of router or firewall, and I can ping that host from inside the pix.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this a routing issue or an access issue?  I'm pretty new to split tunneling, but I'm almost positive i've got that setup correctly cause everything works but Server-to-client communications..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any advice is greatly appreciated!!&lt;/P&gt;&lt;P&gt;  -scott&lt;/P&gt;</description>
    <pubDate>Fri, 21 Feb 2020 08:35:35 GMT</pubDate>
    <dc:creator>snooter</dc:creator>
    <dc:date>2020-02-21T08:35:35Z</dc:date>
    <item>
      <title>PIX VPN - Access/Routing Issue</title>
      <link>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437230#M1055552</link>
      <description>&lt;P&gt;Hello&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I currently have my pix515 (v.7x) acting as a vpn server.  My client is on a cable connection behind it's own router/firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The client can connect to the PIX vpn server just fine.  It gets it's address from a pool on the pix.  Once connected the client can connect to any server side (inside the pix) host/IP.  It can ping everything server side as well.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;My problem is, nothing on the server side (inside the pix) can ping or access any client host/resource.  I don't understand cause I can connect to my pix vpn via a dial up connection, not behind any kind of router or firewall, and I can ping that host from inside the pix.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Is this a routing issue or an access issue?  I'm pretty new to split tunneling, but I'm almost positive i've got that setup correctly cause everything works but Server-to-client communications..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any advice is greatly appreciated!!&lt;/P&gt;&lt;P&gt;  -scott&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:35:35 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437230#M1055552</guid>
      <dc:creator>snooter</dc:creator>
      <dc:date>2020-02-21T08:35:35Z</dc:date>
    </item>
    <item>
      <title>Re: PIX VPN - Access/Routing Issue</title>
      <link>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437231#M1055554</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you check whether you have windows firewall enabled in ur host which is using VPN client to get connected to the central location ??&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Dec 2005 09:52:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437231#M1055554</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2005-12-14T09:52:33Z</dc:date>
    </item>
    <item>
      <title>Re: PIX VPN - Access/Routing Issue</title>
      <link>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437232#M1055560</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Windows Firewall is disabled on both ends.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 14 Dec 2005 14:07:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437232#M1055560</guid>
      <dc:creator>snooter</dc:creator>
      <dc:date>2005-12-14T14:07:20Z</dc:date>
    </item>
    <item>
      <title>Re: PIX VPN - Access/Routing Issue</title>
      <link>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437233#M1055563</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Reminds me of a NAT traversal problem but you said client to server communications work OK.&lt;/P&gt;&lt;P&gt;Not familiar with v7 yet but I had to add "isakmp nat-traversal 20" to my config to allow access from behind a firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can you post a scrubbed config for a look-see?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Dec 2005 04:52:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437233#M1055563</guid>
      <dc:creator>kevinglong</dc:creator>
      <dc:date>2005-12-15T04:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: PIX VPN - Access/Routing Issue</title>
      <link>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437234#M1055568</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Kevin, that did it!  adding the "isakmp nat-traversal 20" free'd it right up.  How hard would it be for cisco to put that in the documentation???  I probably went through 30 different pages pertaining to this in cisco kb, not once did I see this command mentioned.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;  thanks man!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Dec 2005 14:55:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437234#M1055568</guid>
      <dc:creator>snooter</dc:creator>
      <dc:date>2005-12-15T14:55:47Z</dc:date>
    </item>
    <item>
      <title>Re: PIX VPN - Access/Routing Issue</title>
      <link>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437235#M1055571</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I suffered with the inability to tunnel back to the house for months from the office with my PIX501.  Finally found the command via Google so it sticks in my mind.&lt;/P&gt;&lt;P&gt;The command is listed in the docs but my fresh CCNA certificate at the time didn't help me one bit as I didn't know exactly what the problem was nor where to look.  Wish it was on by default.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Glad I could help.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Kevin L&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 15 Dec 2005 22:02:10 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/pix-vpn-access-routing-issue/m-p/437235#M1055571</guid>
      <dc:creator>kevinglong</dc:creator>
      <dc:date>2005-12-15T22:02:10Z</dc:date>
    </item>
  </channel>
</rss>

