<?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: ISE NMAP Failing in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4034848#M558288</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;TAC case number is SR 688095965 : Manual NMAP scan not working&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;</description>
    <pubDate>Mon, 24 Feb 2020 17:58:34 GMT</pubDate>
    <dc:creator>gschmitt.ngit</dc:creator>
    <dc:date>2020-02-24T17:58:34Z</dc:date>
    <item>
      <title>ISE NMAP Failing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4030141#M558219</link>
      <description>&lt;P&gt;I have been working with TAC on an NMAP failure issue since December 2019 and the results are that it is broken. The problem started after upgrading v2.2 from patch 13 to 15. The manual NMAP scan sits on Manual scan in progress... and never populates the Manual NMAP Scan Results page.&lt;/P&gt;
&lt;P&gt;TAC confirmed that installing patch 16 does not correct the problem.&lt;/P&gt;
&lt;P&gt;They told me today that rolling back to patch 13 did not fix the problem either.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 21:11:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4030141#M558219</guid>
      <dc:creator>gschmitt.ngit</dc:creator>
      <dc:date>2020-02-21T21:11:00Z</dc:date>
    </item>
    <item>
      <title>Re: ISE NMAP Failing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4030145#M558220</link>
      <description>Did they provide you with a bug ID yet?  I've had some issues on the latest patch of 2.4 with this too.</description>
      <pubDate>Fri, 14 Feb 2020 23:36:39 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4030145#M558220</guid>
      <dc:creator>Damien Miller</dc:creator>
      <dc:date>2020-02-14T23:36:39Z</dc:date>
    </item>
    <item>
      <title>Re: ISE NMAP Failing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4030148#M558221</link>
      <description>&lt;P&gt;Not yet, and if they are true to course it may never be forth coming...&lt;/P&gt;</description>
      <pubDate>Fri, 14 Feb 2020 23:39:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4030148#M558221</guid>
      <dc:creator>gschmitt.ngit</dc:creator>
      <dc:date>2020-02-14T23:39:26Z</dc:date>
    </item>
    <item>
      <title>Re: ISE NMAP Failing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4033912#M558222</link>
      <description>&lt;P&gt;If you may share the TAC case number, I will take a look.&lt;/P&gt;
&lt;P&gt;PS: I moved your thread to its own. In the future, please avoid resurrect an older post more than a couple of weeks ago and the circumstances are unlikely the same.&lt;/P&gt;
&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 21 Feb 2020 21:13:57 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4033912#M558222</guid>
      <dc:creator>hslai</dc:creator>
      <dc:date>2020-02-21T21:13:57Z</dc:date>
    </item>
    <item>
      <title>Re: ISE NMAP Failing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4034848#M558288</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;TAC case number is SR 688095965 : Manual NMAP scan not working&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2020 17:58:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4034848#M558288</guid>
      <dc:creator>gschmitt.ngit</dc:creator>
      <dc:date>2020-02-24T17:58:34Z</dc:date>
    </item>
    <item>
      <title>Re: ISE NMAP Failing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4034968#M558295</link>
      <description>&lt;P&gt;We usually don't comment on TAC cases - Please see &lt;SPAN class="lia-link-navigation lia-link-disabled"&gt;&lt;A href="https://community.cisco.com/t5/security-documents/how-to-ask-the-community-for-help/ta-p/3704356" target="_self"&gt;How to Ask The Community for Help.&lt;/A&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&lt;SPAN class="lia-link-navigation lia-link-disabled"&gt;You should have an option to Escalate your case to the product engineering team if you aren't getting answers in a reasonable time.&lt;/SPAN&gt;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 24 Feb 2020 21:12:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4034968#M558295</guid>
      <dc:creator>thomas</dc:creator>
      <dc:date>2020-02-24T21:12:04Z</dc:date>
    </item>
    <item>
      <title>Re: ISE NMAP Failing</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4039602#M558540</link>
      <description>&lt;P&gt;Thanks Thomas.&lt;/P&gt;&lt;P&gt;This issue has generated a bug being logged. CSCvt22199&lt;/P&gt;&lt;P&gt;Bug ID: &lt;A href="https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt22199" target="_blank"&gt;https://bst.cloudapps.cisco.com/bugsearch/bug/CSCvt22199&lt;/A&gt;&lt;/P&gt;&lt;P&gt;Cheers,&lt;/P&gt;&lt;P&gt;Greg&lt;/P&gt;</description>
      <pubDate>Tue, 03 Mar 2020 19:52:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-nmap-failing/m-p/4039602#M558540</guid>
      <dc:creator>gschmitt.ngit</dc:creator>
      <dc:date>2020-03-03T19:52:30Z</dc:date>
    </item>
  </channel>
</rss>

