<?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: Webserver behind ASA 5505 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752762#M984901</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks!  That's what I wanted!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 09 Jul 2007 13:32:50 GMT</pubDate>
    <dc:creator>enkrypter</dc:creator>
    <dc:date>2007-07-09T13:32:50Z</dc:date>
    <item>
      <title>Webserver behind ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752760#M984897</link>
      <description>&lt;P&gt;I have an ASA 5505 at home and I am currently staticly NATing my internal resources to the outside world successfuly.  My only problem is that when I try to access my internal resources by name from the inside, they resolve to the IP of my external interface and I am unable to access them.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I know the simple solution would be to make a host file entry or modify my DNS, but I am unwilling to let the ASA beat me.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I assume I need some sort of ACL to stop NATing or some sort of NAT exemption, but am unsure of what to do.  Can anyone help me?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks,&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 10:41:54 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752760#M984897</guid>
      <dc:creator>enkrypter</dc:creator>
      <dc:date>2019-03-11T10:41:54Z</dc:date>
    </item>
    <item>
      <title>Re: Webserver behind ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752761#M984899</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;You need either dns doctoring or hairpinning.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Here is the link which explains both. DNS doctoring will actually change the resolved ip address in the ASA to the inside address. Hairpinning will allow you to request the public address and allow you to bounce off the inside interface of the ASA.&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/ps6120/products_configuration_example09186a00807968d1.shtml" target="_blank"&gt;http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a00807968d1.shtml&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Please rate helpful posts.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2007 13:20:08 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752761#M984899</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-07-09T13:20:08Z</dc:date>
    </item>
    <item>
      <title>Re: Webserver behind ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752762#M984901</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks!  That's what I wanted!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2007 13:32:50 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752762#M984901</guid>
      <dc:creator>enkrypter</dc:creator>
      <dc:date>2007-07-09T13:32:50Z</dc:date>
    </item>
    <item>
      <title>Re: Webserver behind ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752763#M984903</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Here is what I have configured and it is not working.  The haripin example you sent me only shows how to do static nat not pat.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;same-security-traffic permit intra-interface&lt;/P&gt;&lt;P&gt;access-list inbound extended permit tcp any interface outside eq ftp &lt;/P&gt;&lt;P&gt;access-list inbound extended permit tcp any interface outside eq www &lt;/P&gt;&lt;P&gt;access-list inbound extended permit tcp any interface outside eq ftp-data &lt;/P&gt;&lt;P&gt;access-list inbound extended permit udp any interface outside eq tftp &lt;/P&gt;&lt;P&gt;access-list inbound extended permit tcp any interface outside eq 3389 &lt;/P&gt;&lt;P&gt;access-list inbound extended permit icmp any interface outside &lt;/P&gt;&lt;P&gt;access-list inbound extended deny tcp any interface outside eq smtp log &lt;/P&gt;&lt;P&gt;access-list inbound extended permit tcp any interface outside eq 6129 &lt;/P&gt;&lt;P&gt;access-list inbound extended permit tcp any interface outside eq 5900 &lt;/P&gt;&lt;P&gt;access-list inbound extended permit udp any interface outside eq 5900 &lt;/P&gt;&lt;P&gt;access-list inside_nat0_outbound extended permit ip any interface outside &lt;/P&gt;&lt;P&gt;pager lines 24&lt;/P&gt;&lt;P&gt;logging enable&lt;/P&gt;&lt;P&gt;logging asdm informational&lt;/P&gt;&lt;P&gt;mtu inside 1500&lt;/P&gt;&lt;P&gt;mtu outside 1500&lt;/P&gt;&lt;P&gt;ip local pool VPN-Pool 192.168.1.130-192.168.1.135 mask 255.255.255.0&lt;/P&gt;&lt;P&gt;ip verify reverse-path interface outside&lt;/P&gt;&lt;P&gt;icmp unreachable rate-limit 1 burst-size 1&lt;/P&gt;&lt;P&gt;asdm image disk0:/asdm-522.bin&lt;/P&gt;&lt;P&gt;no asdm history enable&lt;/P&gt;&lt;P&gt;arp timeout 14400&lt;/P&gt;&lt;P&gt;global (inside) 1 interface&lt;/P&gt;&lt;P&gt;global (outside) 1 interface&lt;/P&gt;&lt;P&gt;nat (inside) 1 192.168.1.0 255.255.255.0&lt;/P&gt;&lt;P&gt;nat (inside) 1 0.0.0.0 0.0.0.0&lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface 3389 192.168.1.16 3389 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) udp interface tftp 192.168.1.16 tftp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface ftp 192.168.1.16 ftp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface 5900 192.168.1.16 5900 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) udp interface 5900 192.168.1.16 5900 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,outside) tcp interface www 192.168.1.5 www netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,inside) tcp interface 3389 192.168.1.16 3389 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,inside) udp interface tftp 192.168.1.16 tftp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,inside) tcp interface ftp 192.168.1.16 ftp netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,inside) tcp interface 5900 192.168.1.16 5900 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,inside) udp interface 5900 192.168.1.16 5900 netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;static (inside,inside) tcp interface www 192.168.1.5 www netmask 255.255.255.255 &lt;/P&gt;&lt;P&gt;access-group inbound in interface outside&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2007 16:09:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752763#M984903</guid>
      <dc:creator>enkrypter</dc:creator>
      <dc:date>2007-07-09T16:09:40Z</dc:date>
    </item>
    <item>
      <title>Re: Webserver behind ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752764#M984904</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sorry, I don't think either work with pat. I've never tried to hairpin with pat but if it would work it would probably look more like this...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (inside,inside) tcp &lt;OUTSIDE.IP.ADDRESS&gt; 3389 192.168.1.16 3389 netmask 255.255.255.255 &lt;/OUTSIDE.IP.ADDRESS&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2007 16:31:15 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752764#M984904</guid>
      <dc:creator>acomiskey</dc:creator>
      <dc:date>2007-07-09T16:31:15Z</dc:date>
    </item>
    <item>
      <title>Re: Webserver behind ASA 5505</title>
      <link>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752765#M984906</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I agree, but the problem is the outside IP is dynamic and when the IP changed the whole config would too..  Sounds like a limitation on Cisco's part if you as me.  &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Funny how a $50.00 linksys can overcome this problem, but not an ASA...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for the advice!&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 09 Jul 2007 16:46:23 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/webserver-behind-asa-5505/m-p/752765#M984906</guid>
      <dc:creator>enkrypter</dc:creator>
      <dc:date>2007-07-09T16:46:23Z</dc:date>
    </item>
  </channel>
</rss>

