<?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 Webserver and NAT (can access from outside, not inside) in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/webserver-and-nat-can-access-from-outside-not-inside/m-p/2195295#M358924</link>
    <description>&lt;P&gt;I have a 5515-X ASA and we are working on setting up a webserver that whould be accessible from the outside as weel as the inside.&lt;/P&gt;&lt;P&gt;The NAT rule allowing the webserver that is located on an internal LAN to be successful when accessing from the outside.&lt;/P&gt;&lt;P&gt;Now when I try to access the server from a system on the internal LAN i am unable to do so unless i use the internal address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not the end of the world right now as we are only in production, but it would be nice to only have to worry about the public IP as it is registered with DNS so. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here is the nat rule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; nat (outside,inside) 1 source static any any destination static Webserver-Public Webserver-Private service https https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any assistance.&lt;/P&gt;</description>
    <pubDate>Tue, 12 Mar 2019 01:23:40 GMT</pubDate>
    <dc:creator>James Sheridan</dc:creator>
    <dc:date>2019-03-12T01:23:40Z</dc:date>
    <item>
      <title>Webserver and NAT (can access from outside, not inside)</title>
      <link>https://community.cisco.com/t5/network-security/webserver-and-nat-can-access-from-outside-not-inside/m-p/2195295#M358924</link>
      <description>&lt;P&gt;I have a 5515-X ASA and we are working on setting up a webserver that whould be accessible from the outside as weel as the inside.&lt;/P&gt;&lt;P&gt;The NAT rule allowing the webserver that is located on an internal LAN to be successful when accessing from the outside.&lt;/P&gt;&lt;P&gt;Now when I try to access the server from a system on the internal LAN i am unable to do so unless i use the internal address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Not the end of the world right now as we are only in production, but it would be nice to only have to worry about the public IP as it is registered with DNS so. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;here is the nat rule&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp; nat (outside,inside) 1 source static any any destination static Webserver-Public Webserver-Private service https https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for any assistance.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 01:23:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/webserver-and-nat-can-access-from-outside-not-inside/m-p/2195295#M358924</guid>
      <dc:creator>James Sheridan</dc:creator>
      <dc:date>2019-03-12T01:23:40Z</dc:date>
    </item>
    <item>
      <title>Re: Webserver and NAT (can access from outside, not inside)</title>
      <link>https://community.cisco.com/t5/network-security/webserver-and-nat-can-access-from-outside-not-inside/m-p/2195296#M358925</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;If you want both &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Static NAT the Server local IP to a Public IP&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;AND&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;NAT the Server so that it can be reached from the LAN with the public IP address&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Then you could use the following types of configurations&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;SPAN style="text-decoration: underline;"&gt;&lt;EM&gt;Static NAT from LAN to WAN&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object network SERVER-STATIC&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; host 10.0.0.200&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; nat (LAN,WAN) static 1.2.3.4&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;10.0.0.200 = Server local IP address&lt;/LI&gt;&lt;LI&gt;1.2.3.4 = Public IP address dedicated for this server&lt;/LI&gt;&lt;LI&gt;LAN and WAN = Inside and Outside interfaces&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;EM&gt;Dynamic Policy PAT coupled with the Static NAT (Twice NAT) for the Server for LAN users&lt;/EM&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object network LAN&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; subnet 10.0.0.0 255.255.255.0&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object network SERVER-LOCAL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; host 10.0.0.200&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;object network SERVER-GLOBAL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt; host 1.2.3.4&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;nat (LAN,LAN) source dynamic LAN interface destination static SERVER-GLOBAL SERVER-LOCAL&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Where&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;10.0.0.0/24 = Is the LAN network&lt;/LI&gt;&lt;LI&gt;10.0.0.200 = Is the server local IP address&lt;/LI&gt;&lt;LI&gt;1.2.3.4 = Is the server public IP address&lt;/LI&gt;&lt;/UL&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;The first NAT configuration is a simple Static NAT using "Network Object NAT" and its only purpose is to NAT the server local IP address to a public IP address for users on the Internet.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The second NAT configuration is a Dynamic Policy PAT with also the Static NAT done with a Twice NAT / Manual NAT configuration.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The way it works is that when the ASA sees a connection coming from the network LAN to the Public IP address then it will PAT the LAN users to the interface LAN IP address and it will also UN-NAT the public IP address to the local IP address of the server. This will enable you to connect to the server using the public IP address even from the LAN.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope I made any sense. &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt; Please do ask more if I didnt &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hope this helps &lt;SPAN __jive_emoticon_name="happy" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/images/emoticons/happy.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;- Jouni&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 04 Apr 2013 17:09:45 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/webserver-and-nat-can-access-from-outside-not-inside/m-p/2195296#M358925</guid>
      <dc:creator>Jouni Forss</dc:creator>
      <dc:date>2013-04-04T17:09:45Z</dc:date>
    </item>
  </channel>
</rss>

