<?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: IPsec client connection in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/ipsec-client-connection/m-p/849240#M955987</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I tried removing it, and the behaviour changes slightly, without the management-access statement the ssh session closes immediately, with it the session hangs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 30 Jan 2008 17:35:27 GMT</pubDate>
    <dc:creator>mark.j.hodge</dc:creator>
    <dc:date>2008-01-30T17:35:27Z</dc:date>
    <item>
      <title>IPsec client connection</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-client-connection/m-p/849237#M955979</link>
      <description>&lt;P&gt;I have setup a IPsec VPN Client connection to a PIX515 Firewall pair. It works as expected in most respects, I can gain access to all devices on the internel network, except the active firewall.  I can ping the inside address, but not telnet,ssh or asdm.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The PIX is running 8.0(3) software, I have checked the nat0 access list and it looks fine.  I have confirmed that "management-access inside" has been configured.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;When I try and connect (ssh) I get the following error messages (sanitised), but cannot find any information on NP Identity.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Jan 30 2008 16:46:16: %PIX-6-302013: Built inbound TCP connection 760 for outside:10.20.1.226/2800 (10.20.1.226/2800) to NP Identity Ifc:10.20.1.253/22 (10.20.1.253/22) (userid)&lt;/P&gt;&lt;P&gt;Jan 30 2008 16:46:16: %PIX-6-302014: Teardown TCP connection 760 for outside:10.20.1.226/2800 to NP Identity Ifc:10.20.1.253/22 duration 0:00:00 bytes 0 Flow terminated by TCP Intercept (userid)&lt;/P&gt;&lt;P&gt;Jan 30 2008 16:46:16: %PIX-6-302013: Built inbound TCP connection 761 for outside:10.20.1.226/2800 (10.20.1.226/2800) to NP Identity Ifc:10.20.1.253/22 (10.20.1.253/22) (userid)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10.20.1.226 is the pool allocated VPN address.&lt;/P&gt;&lt;P&gt;10.20.1.253 is the inside address of the firewall.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have recently setup a very similar configuration, on an ASA device, running the same software versions and it works fine.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Suggestions appreciated.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 11:56:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-client-connection/m-p/849237#M955979</guid>
      <dc:creator>mark.j.hodge</dc:creator>
      <dc:date>2019-03-11T11:56:03Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec client connection</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-client-connection/m-p/849238#M955981</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Mark, Â¨&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;try adding statement &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;management-access inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;it should provide for firewall management over IPsec tunnel, see if that helps.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/m.html#wp1863771" target="_blank"&gt;http://www.cisco.com/en/US/docs/security/asa/asa80/command/reference/m.html#wp1863771&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rgds&lt;/P&gt;&lt;P&gt;Jorge&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2008 16:50:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-client-connection/m-p/849238#M955981</guid>
      <dc:creator>JORGE RODRIGUEZ</dc:creator>
      <dc:date>2008-01-30T16:50:20Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec client connection</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-client-connection/m-p/849239#M955984</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jorge,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;statement is already there..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Mark&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2008 16:53:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-client-connection/m-p/849239#M955984</guid>
      <dc:creator>mark.j.hodge</dc:creator>
      <dc:date>2008-01-30T16:53:24Z</dc:date>
    </item>
    <item>
      <title>Re: IPsec client connection</title>
      <link>https://community.cisco.com/t5/network-security/ipsec-client-connection/m-p/849240#M955987</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I tried removing it, and the behaviour changes slightly, without the management-access statement the ssh session closes immediately, with it the session hangs.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 30 Jan 2008 17:35:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/ipsec-client-connection/m-p/849240#M955987</guid>
      <dc:creator>mark.j.hodge</dc:creator>
      <dc:date>2008-01-30T17:35:27Z</dc:date>
    </item>
  </channel>
</rss>

