<?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: ASA 7.2 remote access VPN in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773102#M1021721</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi   ..  please check:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.- That your routing is correct. The segment 192.168.14.x should know how to get back to 10.254.14.X. those returned packets need to reach the inside interface of the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.-  You might need to enable NAT-T whiach is not enabled by default. The command is&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;crypto isakmp nat-traversal  20&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps  ..  please rate it if it does !!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&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>Mon, 25 Jun 2007 10:29:28 GMT</pubDate>
    <dc:creator>Fernando_Meza</dc:creator>
    <dc:date>2007-06-25T10:29:28Z</dc:date>
    <item>
      <title>ASA 7.2 remote access VPN</title>
      <link>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773099#M1021718</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I created a remote access VPN on my ASA through ASDM. The internal LAN in 192.168.14.x; the remote access pool uses 10.254.14.x; my vpn client logs in normally, but once in, i am not able to reach 192.168.14.x; any tips?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:34:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773099#M1021718</guid>
      <dc:creator>m-mneimneh</dc:creator>
      <dc:date>2019-03-11T10:34:30Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 7.2 remote access VPN</title>
      <link>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773100#M1021719</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;it can be you have not configured access-list nonat,ex. access-list nonat perm ip 10.254.14.0 255.255.255.0 10.254.14.0 255.255.255.0 &lt;/P&gt;&lt;P&gt;and command nat (inside) 0 access-list nonat&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HtH&lt;/P&gt;&lt;P&gt;                              Zdenek&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jun 2007 09:52:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773100#M1021719</guid>
      <dc:creator>zroth</dc:creator>
      <dc:date>2007-06-25T09:52:51Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 7.2 remote access VPN</title>
      <link>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773101#M1021720</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry fot the mistake,&lt;/P&gt;&lt;P&gt;access-list shall be  access-list nonat perm ip 192.168.14.0 255.255.255.0 10.254.14.0 255.255.255.0&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jun 2007 09:55:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773101#M1021720</guid>
      <dc:creator>zroth</dc:creator>
      <dc:date>2007-06-25T09:55:11Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 7.2 remote access VPN</title>
      <link>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773102#M1021721</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi   ..  please check:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.- That your routing is correct. The segment 192.168.14.x should know how to get back to 10.254.14.X. those returned packets need to reach the inside interface of the ASA.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.-  You might need to enable NAT-T whiach is not enabled by default. The command is&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;crypto isakmp nat-traversal  20&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I hope it helps  ..  please rate it if it does !!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&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>Mon, 25 Jun 2007 10:29:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773102#M1021721</guid>
      <dc:creator>Fernando_Meza</dc:creator>
      <dc:date>2007-06-25T10:29:28Z</dc:date>
    </item>
    <item>
      <title>Re: ASA 7.2 remote access VPN</title>
      <link>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773103#M1021722</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi guys,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it turned out i needed to add the following to the inside access-list:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list inside_acl extended permit ip any 10.254.14.0 255.255.255.0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;when applied, i could get responses from 192.168.14.x machines.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;thank you for your contributions.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 25 Jun 2007 10:35:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-7-2-remote-access-vpn/m-p/773103#M1021722</guid>
      <dc:creator>m-mneimneh</dc:creator>
      <dc:date>2007-06-25T10:35:44Z</dc:date>
    </item>
  </channel>
</rss>

