<?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: VPN Issue in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572220#M1055159</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not sure what logs I need to turn on - can you help me to turn the correct ones on please?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 10 May 2006 15:01:27 GMT</pubDate>
    <dc:creator>neilwheatcroft</dc:creator>
    <dc:date>2006-05-10T15:01:27Z</dc:date>
    <item>
      <title>VPN Issue</title>
      <link>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572218#M1055154</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm very new to cisco equipment and was hoping someone could help me with this issue I have. I am trying to set up a VPN from a cisco 837 router that I have to another company, which I think is using a PIX. After some tweaking I managed to set the same VPN up from another site we have, which uses a 3000 concentator. However after using cisco SDM and using as many commands as I know how I cannot get the VPN tunnel to come up. Essentailly I want &amp;lt;server1&amp;gt; and &amp;lt;server2&amp;gt; (as shown in the attached show run) to be able to access 192.168.0.100 that is off of my 837 router. Any help would be very gratefully received.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 08:53:19 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572218#M1055154</guid>
      <dc:creator>neilwheatcroft</dc:creator>
      <dc:date>2020-02-21T08:53:19Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Issue</title>
      <link>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572219#M1055157</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 revert whether you are seeing any error logs in your Cisco 837 router related to this VPN establishment ?&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, 10 May 2006 10:40:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572219#M1055157</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2006-05-10T10:40:24Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Issue</title>
      <link>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572220#M1055159</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I'm not sure what logs I need to turn on - can you help me to turn the correct ones on please?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 10 May 2006 15:01:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572220#M1055159</guid>
      <dc:creator>neilwheatcroft</dc:creator>
      <dc:date>2006-05-10T15:01:27Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Issue</title>
      <link>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572221#M1055161</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;do refer this link ...&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/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a008030c760.html#wp1001168" target="_blank"&gt;http://www.cisco.com/en/US/products/sw/iosswrel/ps1835/products_configuration_guide_chapter09186a008030c760.html#wp1001168&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regds&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 11 May 2006 06:23:31 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572221#M1055161</guid>
      <dc:creator>spremkumar</dc:creator>
      <dc:date>2006-05-11T06:23:31Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Issue</title>
      <link>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572222#M1055162</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I feel your problem is here&lt;/P&gt;&lt;P&gt;ip access-list extended Mick                           &lt;/P&gt;&lt;P&gt; permit ip host 192.168.0.100 host &lt;SERVER1&gt;                                              &lt;/SERVER1&gt;&lt;/P&gt;&lt;P&gt; permit ip host 192.168.0.100 host &lt;SERVER2&gt;                                             &lt;/SERVER2&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Try to make sure your peer (The PIX) has the same IPSEC SAs.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also, you can issue the command debug crypto isakmp and debug crypto ipsec &lt;/P&gt;&lt;P&gt;Try to send us the log or trace it to know where is the problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 04 Aug 2006 22:08:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572222#M1055162</guid>
      <dc:creator>m-haddad</dc:creator>
      <dc:date>2006-08-04T22:08:17Z</dc:date>
    </item>
    <item>
      <title>Re: VPN Issue</title>
      <link>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572223#M1055163</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Neil&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I do not know if you have this sorted out yet or not. But assuming that it is not (since there is no update to the forum about it) I will make a guess at the problem and possible solutions. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am guessing that the VPN that you set up from the other site had fixed IP addresses on both ends. In what you are trying to set up here the dialer interface has address negotiated. And since you do not specify the source address for IPSec it will default to using the address of the outbound interface which is dialer 0 which gets assigned dynamically. I am guessing that the PIX is not set up for a dynamic address on its peer.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;One way to make this work would be to have the PIX configured with a dynamic crypto map which will allow the PIX to establish IPSec with devices whose addresses it does not know ahead of time. If the administrators of the PIX are willing to do this it could be a solution to your problem.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Another possible solution to the problem would be to specify the source address using an interface that the PIX can get to. Since the traffic should be reaching 192.168.0.100 can we assume that interface Ethernet 0 is reachable from the PIX? If so then try adding this to the config:&lt;/P&gt;&lt;P&gt;crypto map SDM_CMAP_1 local-address Ethernet0&lt;/P&gt;&lt;P&gt;This will get IPSec to use the Ethernet 0 as the source address and the PIX would have a fixed address to use as its peer address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Do you know how they have configured the PIX for this IPSec connection? Knowing this might make it easier to pick the best solution.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;HTH&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Rick&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 13 Aug 2006 23:50:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/vpn-issue/m-p/572223#M1055163</guid>
      <dc:creator>Richard Burts</dc:creator>
      <dc:date>2006-08-13T23:50:39Z</dc:date>
    </item>
  </channel>
</rss>

