<?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: 106016: Deny IP Spoof Error on ASA 5510 in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088783#M893476</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would run a whois on those external IPs to see what they are really, this might give you an idea about the traffic. What is the destination port? (If its TCP/UDP) traffic?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Download process explorer and run it on your ISA server (no need to install it,its standalone).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx" target="_blank"&gt;http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check which 'service' or application is opening these connections from the ISA server. Perhaps a trojan/worm...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Fri, 21 Nov 2008 11:43:04 GMT</pubDate>
    <dc:creator>Farrukh Haroon</dc:creator>
    <dc:date>2008-11-21T11:43:04Z</dc:date>
    <item>
      <title>106016: Deny IP Spoof Error on ASA 5510</title>
      <link>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088778#M893471</link>
      <description>&lt;P&gt;Hi All,&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am receiving a number of errors on my Cisco ASA 5510 device that reads: &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;106016: Deny IP spoof from (127.0.0.1) to x.x.x.x on Interface Inside&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;x.x.x.x is some random IP Address. There are a number of IP Addresses that are reported. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any ideas?&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 14:14:14 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088778#M893471</guid>
      <dc:creator>pjscott13</dc:creator>
      <dc:date>2019-03-11T14:14:14Z</dc:date>
    </item>
    <item>
      <title>Re: 106016: Deny IP Spoof Error on ASA 5510</title>
      <link>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088779#M893472</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Since that is a loopback IP, it could be any host. Probably one with vmware etc. Do a packet capture for that IP and get the mac-address. Then trace it on your network&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Tue, 18 Nov 2008 08:06:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088779#M893472</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-11-18T08:06:11Z</dc:date>
    </item>
    <item>
      <title>Re: 106016: Deny IP Spoof Error on ASA 5510</title>
      <link>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088780#M893473</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I have to admit that the x.x.x.x ip addresses that appear are external public IP addresses that I have no idea what they are. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Also on the Internal Interface of the ASA there is an ISA Server... there is nothing between the ASA and ISA server. Is there another way of getting a packet capture without installing a hub between the ASA and the ISA... as obviously this means there will be an outage while I install the hub? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Nov 2008 02:36:41 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088780#M893473</guid>
      <dc:creator>pjscott13</dc:creator>
      <dc:date>2008-11-19T02:36:41Z</dc:date>
    </item>
    <item>
      <title>Re: 106016: Deny IP Spoof Error on ASA 5510</title>
      <link>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088781#M893474</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Well there is a capture command built-in 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_tech_note09186a00807c35e7.shtml#s3" target="_blank"&gt;http://www.cisco.com/en/US/products/ps6120/products_tech_note09186a00807c35e7.shtml#s3&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Once you get the mac-address, wireshark will show you the vendor name as derived from the MAC Address OID field (or you can google it up pretty quick).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 19 Nov 2008 03:13:37 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088781#M893474</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-11-19T03:13:37Z</dc:date>
    </item>
    <item>
      <title>Re: 106016: Deny IP Spoof Error on ASA 5510</title>
      <link>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088782#M893475</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks! This is somewhat helpful. From what I have found the MAC address is of the ISA server (which is the only thing that connects to the Inside interface of the ASA... no surprise really) but why?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The packet capture shows that the source IP Address is 127.0.0.1 with the MAC of the ISA server and the Destination is of various external IP Addresses with the destination MAC address of the ASA. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;What can I check now? &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Nov 2008 04:26:29 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088782#M893475</guid>
      <dc:creator>pjscott13</dc:creator>
      <dc:date>2008-11-21T04:26:29Z</dc:date>
    </item>
    <item>
      <title>Re: 106016: Deny IP Spoof Error on ASA 5510</title>
      <link>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088783#M893476</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;I would run a whois on those external IPs to see what they are really, this might give you an idea about the traffic. What is the destination port? (If its TCP/UDP) traffic?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Download process explorer and run it on your ISA server (no need to install it,its standalone).&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive-link-custom" href="http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx" target="_blank"&gt;http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check which 'service' or application is opening these connections from the ISA server. Perhaps a trojan/worm...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Farrukh&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Fri, 21 Nov 2008 11:43:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/106016-deny-ip-spoof-error-on-asa-5510/m-p/1088783#M893476</guid>
      <dc:creator>Farrukh Haroon</dc:creator>
      <dc:date>2008-11-21T11:43:04Z</dc:date>
    </item>
  </channel>
</rss>

