<?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:inside host available to inside users by External IP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290178#M342649</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nevermind. You are not using dns.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Sun, 22 Sep 2013 02:12:53 GMT</pubDate>
    <dc:creator>jj27</dc:creator>
    <dc:date>2013-09-22T02:12:53Z</dc:date>
    <item>
      <title>inside host available to inside users by External IP</title>
      <link>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290174#M342639</link>
      <description>&lt;P&gt;Pix 515 6.3.5&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have this configuration&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;static (outside,inside) 1.1.1.1 192.168.1.1&lt;/P&gt;&lt;P&gt;access-list ACL permit tcp any host 1.1.1.1 eq https&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;In this case all users from OUTSIDE can access the server by IP 1.1.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Because of a special case that I do not want to resolve with DNS zones and "A" records, I need to make this same host available to INSIDE users by same external IP: 1.1.1.1&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;How can this be accomplished? &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Juan&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 02:41:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290174#M342639</guid>
      <dc:creator>johnramz</dc:creator>
      <dc:date>2019-03-12T02:41:40Z</dc:date>
    </item>
    <item>
      <title>Re:inside host available to inside users by External IP</title>
      <link>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290175#M342641</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Try adding the "DNS" keyword at the end of your static NAT statement. DNS rewrite should occur and point it to the internal IP.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Sep 2013 15:27:47 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290175#M342641</guid>
      <dc:creator>jj27</dc:creator>
      <dc:date>2013-09-21T15:27:47Z</dc:date>
    </item>
    <item>
      <title>Re:inside host available to inside users by External IP</title>
      <link>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290176#M342642</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;ljohnston1127,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Possibly, I did not explain myself well. That configuration there works fine for external users accessing the external IP 1.1.1.1. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What I want to is to make possible for the INSIDE/internal users to access that server with the EXTERNAL ip 1.1.1.1 . Users in the INSIDE zone can acccess host by internal ip 192.168.1.1 . I want them to access it by External IP.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Hopefully I am making sense.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Juan&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Sep 2013 17:06:43 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290176#M342642</guid>
      <dc:creator>johnramz</dc:creator>
      <dc:date>2013-09-21T17:06:43Z</dc:date>
    </item>
    <item>
      <title>inside host available to inside users by External IP</title>
      <link>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290177#M342647</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 your intention to do that?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Go out of your network to get back again to access info that is inside?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN __jive_emoticon_name="confused" __jive_macro_name="emoticon" class="jive_macro jive_emote" src="https://community.cisco.com/4.5.4/images/tiny_mce3/plugins/jiveemoticons/images/spacer.gif"&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sat, 21 Sep 2013 23:31:05 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290177#M342647</guid>
      <dc:creator>Antonio Simoes</dc:creator>
      <dc:date>2013-09-21T23:31:05Z</dc:date>
    </item>
    <item>
      <title>Re:inside host available to inside users by External IP</title>
      <link>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290178#M342649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Nevermind. You are not using dns.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Sent from Cisco Technical Support Android App&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Sun, 22 Sep 2013 02:12:53 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/inside-host-available-to-inside-users-by-external-ip/m-p/2290178#M342649</guid>
      <dc:creator>jj27</dc:creator>
      <dc:date>2013-09-22T02:12:53Z</dc:date>
    </item>
  </channel>
</rss>

