<?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: Static NAT VPN Problem in Switching</title>
    <link>https://community.cisco.com/t5/switching/static-nat-vpn-problem/m-p/693436#M12887</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;What is happening is that the PAT on your wan interface is changing the source ports from the VPN client. This is breaking the IKE/IPSEC negotiation. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you probably need to do is use NAT-T which add a UDP header to the IPSEC packets. I've attached a link that explains what it is and how to enable it on a Cisco client (don't know if thats what you are using but all vpn clients should support it ). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/471/cvpn_3k_nat.html#conf_client" target="_blank"&gt;http://www.cisco.com/warp/public/471/cvpn_3k_nat.html#conf_client&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will need to talk to the people who control the remote site VPN device as that device has to have NAT-T enabled as well. &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;Jon &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 26 Jan 2007 16:33:22 GMT</pubDate>
    <dc:creator>Jon Marshall</dc:creator>
    <dc:date>2007-01-26T16:33:22Z</dc:date>
    <item>
      <title>Static NAT VPN Problem</title>
      <link>https://community.cisco.com/t5/switching/static-nat-vpn-problem/m-p/693435#M12886</link>
      <description>&lt;P&gt;Greetings,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am having an issue with my NAT configuration.  I am fairly knowledable on Cisco routers, but by no means an expert.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Configuration:&lt;/P&gt;&lt;P&gt;Cisco 2611 with two Ethernet ports.&lt;/P&gt;&lt;P&gt;E0/0 (WAN) - DHCP address (69.x.x.228) connected to a Time Warner Cable Modem &lt;/P&gt;&lt;P&gt;E0/1 (LAN) - 10.0.0.1 / 24&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;E0/0 is configured for NAT outside&lt;/P&gt;&lt;P&gt;E0/1 is configured for NAT inside&lt;/P&gt;&lt;P&gt;ip nat inside source list 115 interface E0/0 overload&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;10.x.x.x. clients have no issue access the internet and everything thing seems to work fine. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, I have one client on 10.0.0.51 that is used to connect to a remote VPN site.  I cannot connect using VPN.  If I add the following statement:&lt;/P&gt;&lt;P&gt;   ip nat inside source static 10.0.0.51 interface E0/0&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then VPN works just fine? however you can see that it breaks several other things.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have tried to put in a static NAT with a specific port mapping for this address but that does not work either.  Since I only have one "WAN" address I'm not sure how to get around this.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any help would be appreciated. &lt;/P&gt;&lt;P&gt;Tnx,&lt;/P&gt;&lt;P&gt;MJG&lt;/P&gt;&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 05 Mar 2019 22:00:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/static-nat-vpn-problem/m-p/693435#M12886</guid>
      <dc:creator>mgriffin</dc:creator>
      <dc:date>2019-03-05T22:00:50Z</dc:date>
    </item>
    <item>
      <title>Re: Static NAT VPN Problem</title>
      <link>https://community.cisco.com/t5/switching/static-nat-vpn-problem/m-p/693436#M12887</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;What is happening is that the PAT on your wan interface is changing the source ports from the VPN client. This is breaking the IKE/IPSEC negotiation. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What you probably need to do is use NAT-T which add a UDP header to the IPSEC packets. I've attached a link that explains what it is and how to enable it on a Cisco client (don't know if thats what you are using but all vpn clients should support it ). &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://www.cisco.com/warp/public/471/cvpn_3k_nat.html#conf_client" target="_blank"&gt;http://www.cisco.com/warp/public/471/cvpn_3k_nat.html#conf_client&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;You will need to talk to the people who control the remote site VPN device as that device has to have NAT-T enabled as well. &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;Jon &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Jan 2007 16:33:22 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/static-nat-vpn-problem/m-p/693436#M12887</guid>
      <dc:creator>Jon Marshall</dc:creator>
      <dc:date>2007-01-26T16:33:22Z</dc:date>
    </item>
    <item>
      <title>Re: Static NAT VPN Problem</title>
      <link>https://community.cisco.com/t5/switching/static-nat-vpn-problem/m-p/693437#M12888</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the info.  I looked at the document and it refers to a PIX setup.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I also checked with our remote location and they do not support NAT-T nor does the client I am using.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any other throughs on how to get this working?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tnx again.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Jan 2007 16:54:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/static-nat-vpn-problem/m-p/693437#M12888</guid>
      <dc:creator>mgriffin</dc:creator>
      <dc:date>2007-01-26T16:54:50Z</dc:date>
    </item>
    <item>
      <title>Re: Static NAT VPN Problem</title>
      <link>https://community.cisco.com/t5/switching/static-nat-vpn-problem/m-p/693438#M12889</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Jon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I solved my own problem!!! ...although I dont quite understand how/why.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In the end I changed this statement:&lt;/P&gt;&lt;P&gt;  ip nat inside source list 1 interface e0/0 overload&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;to:&lt;/P&gt;&lt;P&gt;  ip nat inside source list 115 interface e0/0 overload.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ACL 1 was: permit 10.0.0.0 0.0.0.255&lt;/P&gt;&lt;P&gt;New ACL 115 is: permit ip 10.0.0.0 0.0.0.255 any&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I'm not sure why using an extended ACL works when a standard one does not... but it works fine now and I can VPN outbound and all other services still work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Tnx,&lt;/P&gt;&lt;P&gt;MJG&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 26 Jan 2007 19:57:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/switching/static-nat-vpn-problem/m-p/693438#M12889</guid>
      <dc:creator>mgriffin</dc:creator>
      <dc:date>2007-01-26T19:57:40Z</dc:date>
    </item>
  </channel>
</rss>

