<?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 ASA Failover-VPN Issues in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/asa-failover-vpn-issues/m-p/1062031#M894380</link>
    <description>&lt;P&gt;Our ASA5510's recently failed over, and now I have a handful of VPN clients that can connect, but not route anywhere in our network.  I'm not sure the configs have been properly synced, but I do not know how to confirm.&lt;/P&gt;</description>
    <pubDate>Mon, 11 Mar 2019 14:04:24 GMT</pubDate>
    <dc:creator>jgorman1977</dc:creator>
    <dc:date>2019-03-11T14:04:24Z</dc:date>
    <item>
      <title>ASA Failover-VPN Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-vpn-issues/m-p/1062031#M894380</link>
      <description>&lt;P&gt;Our ASA5510's recently failed over, and now I have a handful of VPN clients that can connect, but not route anywhere in our network.  I'm not sure the configs have been properly synced, but I do not know how to confirm.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 14:04:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-vpn-issues/m-p/1062031#M894380</guid>
      <dc:creator>jgorman1977</dc:creator>
      <dc:date>2019-03-11T14:04:24Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover-VPN Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-vpn-issues/m-p/1062032#M894384</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Silly question, but do the routes from your 'internal' network to the remote VPN clients point to the old 'failed' ASA or to the new ASA? Try checking this first &lt;span class="lia-unicode-emoji" title=":slightly_smiling_face:"&gt;🙂&lt;/span&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;P&gt;Darren&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Oct 2008 23:06:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-vpn-issues/m-p/1062032#M894384</guid>
      <dc:creator>darrenj</dc:creator>
      <dc:date>2008-10-28T23:06:15Z</dc:date>
    </item>
    <item>
      <title>Re: ASA Failover-VPN Issues</title>
      <link>https://community.cisco.com/t5/network-security/asa-failover-vpn-issues/m-p/1062033#M894385</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Darren,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;They point to the virtual ip address, so that doesn't change on failover.  It's only happened to half a dozen people or so.  They can connect, but when I monitor the traffic, nothing is being passed.  Very strange.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 28 Oct 2008 23:39:12 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/asa-failover-vpn-issues/m-p/1062033#M894385</guid>
      <dc:creator>jgorman1977</dc:creator>
      <dc:date>2008-10-28T23:39:12Z</dc:date>
    </item>
  </channel>
</rss>

