<?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 Accessing inside service from outside via 5505 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/accessing-inside-service-from-outside-via-5505/m-p/2425319#M268931</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your response. I'm going to rate your answer as correct but there was a line you were missing that I believe was the initial problem all along.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I had forgotten was to apply the access list to the outside interface:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group outside_access in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once I did this it worked!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS:&amp;nbsp; Anyone in future looking at this - You will also need to ensure your http server enable is on a separate port using command&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;http server enable &lt;EM&gt;port-number&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sat, 01 Mar 2014 03:25:23 GMT</pubDate>
    <dc:creator>Lemon Lime</dc:creator>
    <dc:date>2014-03-01T03:25:23Z</dc:date>
    <item>
      <title>Accessing inside service from outside via 5505</title>
      <link>https://community.cisco.com/t5/network-security/accessing-inside-service-from-outside-via-5505/m-p/2425317#M268929</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I feel that this should be straight forward but I am having a lot of trouble getting this to work.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am using v8.2 (security plus license) and have an ASA which does the standard allow internal access outside but I also have an additional network which is accessed with AnyConnect client.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I now have another requirement to place a web service so it is publically accessible.&amp;nbsp; I only have 1 available IP address which is the outside IP of my ASA (I cannot get anymore).&amp;nbsp; I though I could achieve this with port forwarding so if I chose to go to my IP with a :portnumber I could forward that traffic to my internal server.&amp;nbsp; Is this correct.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Example:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Outside World&amp;nbsp; ------------- Outside ASA / Inside ASA --------------------- Web Server&lt;/P&gt;&lt;P&gt;&lt;EM&gt;0.0.0.0&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 1.1.1.1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.1.1&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; 192.168.1.2&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;What I would like to do is enter the outside IP of my ASA into a browser with a random port and that redirects to my internal server (e.g. &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://1.1.1.1:55000" target="_blank"&gt;http://1.1.1.1:55000&lt;/A&gt;&lt;SPAN&gt; redirects to &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="https://192.168.1.2" target="_blank"&gt;https://192.168.1.2&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="text-decoration: underline;"&gt;&lt;STRONG&gt;Additional Criteria&lt;/STRONG&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; I must not affect current services including my VPN connections&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; I may have additional web servers in future which will have to also use same outside IP address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Can this be done and if so, how?&lt;/P&gt;</description>
      <pubDate>Tue, 26 Mar 2019 00:53:02 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accessing-inside-service-from-outside-via-5505/m-p/2425317#M268929</guid>
      <dc:creator>Lemon Lime</dc:creator>
      <dc:date>2019-03-26T00:53:02Z</dc:date>
    </item>
    <item>
      <title>Accessing inside service from outside via 5505</title>
      <link>https://community.cisco.com/t5/network-security/accessing-inside-service-from-outside-via-5505/m-p/2425318#M268930</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi Simon,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you need to setup port forwarding on ASA runnin 8.2, the configuration will look like this:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface 55000 192.168.1.2 443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;So traffic coming from the Internet will reach the external IP 1.1.1.1:55000 and the ASA will send the traffic to internal web server on tcp port 443.&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Also remember to add the access list:&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside_access line 1 extended permit tcp any host 1.1.1.1 eq 55000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;If you have another web server behind the inside you can the same public IP address but different random port:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface 56000 192.168.1.3 443&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-list outside_access line 1 extended permit tcp any host 1.1.1.1 eq 56000&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="font-size: 10pt;"&gt;Please rate and select a correct answer.&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 28 Feb 2014 03:07:51 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accessing-inside-service-from-outside-via-5505/m-p/2425318#M268930</guid>
      <dc:creator>Harvey Ortiz</dc:creator>
      <dc:date>2014-02-28T03:07:51Z</dc:date>
    </item>
    <item>
      <title>Accessing inside service from outside via 5505</title>
      <link>https://community.cisco.com/t5/network-security/accessing-inside-service-from-outside-via-5505/m-p/2425319#M268931</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thank you for your response. I'm going to rate your answer as correct but there was a line you were missing that I believe was the initial problem all along.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I had forgotten was to apply the access list to the outside interface:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;access-group outside_access in interface outside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once I did this it worked!!&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;PS:&amp;nbsp; Anyone in future looking at this - You will also need to ensure your http server enable is on a separate port using command&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;http server enable &lt;EM&gt;port-number&lt;/EM&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 01 Mar 2014 03:25:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/accessing-inside-service-from-outside-via-5505/m-p/2425319#M268931</guid>
      <dc:creator>Lemon Lime</dc:creator>
      <dc:date>2014-03-01T03:25:23Z</dc:date>
    </item>
  </channel>
</rss>

