<?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 Access Current Server using External SNAT IP in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/access-current-server-using-external-snat-ip/m-p/2130592#M394389</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you are trying to access the server with its own ip address, the ASA will detect that, and will report that as the Land Attack, ie: accessing the host with its own ip address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since the translation is being configured on the ASA, the ASA knows that the private ip of the server is trying to access its own public ip address, hence will deny that traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest that if you need to access the server with its own ip address, you would need to configure it to access its private ip address instead of the public IP. Or access its loopback address, which is normally 127.0.0.1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Mon, 10 Dec 2012 07:00:09 GMT</pubDate>
    <dc:creator>Jennifer Halim</dc:creator>
    <dc:date>2012-12-10T07:00:09Z</dc:date>
    <item>
      <title>Access Current Server using External SNAT IP</title>
      <link>https://community.cisco.com/t5/network-security/access-current-server-using-external-snat-ip/m-p/2130591#M394382</link>
      <description>&lt;P&gt;Hi there,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have an ASA 5520 with a DMZ with private addresses that I SNAT to my outside network. &lt;/P&gt;&lt;P&gt;From inside the DMZ I can reach servers by both the internal private IP and the public IP, except if the IP is from the server trying to connect.&lt;/P&gt;&lt;P&gt;So, say I have server1 and server2. I can connect from server1 to server 2 with both public and private, but can't connect from server1 to server1' using the public IP.&lt;/P&gt;&lt;P&gt;ASA logs show that packets are being denied due to land attack.&lt;/P&gt;&lt;P&gt;DNS doctoring is not an option for me.&lt;/P&gt;&lt;P&gt;Is there a way to fix this?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Tue, 12 Mar 2019 00:35:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-current-server-using-external-snat-ip/m-p/2130591#M394382</guid>
      <dc:creator>Ricardo Duarte</dc:creator>
      <dc:date>2019-03-12T00:35:11Z</dc:date>
    </item>
    <item>
      <title>Access Current Server using External SNAT IP</title>
      <link>https://community.cisco.com/t5/network-security/access-current-server-using-external-snat-ip/m-p/2130592#M394389</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;When you are trying to access the server with its own ip address, the ASA will detect that, and will report that as the Land Attack, ie: accessing the host with its own ip address.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Since the translation is being configured on the ASA, the ASA knows that the private ip of the server is trying to access its own public ip address, hence will deny that traffic.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I would suggest that if you need to access the server with its own ip address, you would need to configure it to access its private ip address instead of the public IP. Or access its loopback address, which is normally 127.0.0.1&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Mon, 10 Dec 2012 07:00:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/access-current-server-using-external-snat-ip/m-p/2130592#M394389</guid>
      <dc:creator>Jennifer Halim</dc:creator>
      <dc:date>2012-12-10T07:00:09Z</dc:date>
    </item>
  </channel>
</rss>

