<?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 In AWS Active Directory Diagnostic Tool test in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4516403#M571580</link>
    <description>&lt;P&gt;It should be using whichever DNS servers you have configured when you provisioned it.&lt;/P&gt;
&lt;P&gt;You will need to SSH with your AWS private key to see the DNS server configuration with a `show run`.&lt;/P&gt;</description>
    <pubDate>Fri, 10 Dec 2021 03:56:28 GMT</pubDate>
    <dc:creator>thomas</dc:creator>
    <dc:date>2021-12-10T03:56:28Z</dc:date>
    <item>
      <title>ISE In AWS Active Directory Diagnostic Tool test</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4513898#M571478</link>
      <description>&lt;P&gt;I have just added a our first AWS instance to you our ISE Deployment and when I join it to the Active Directory domain the following tests are failing/showing a warning:&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Failed AD Diagnostic Tests.png" style="width: 999px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/138764i58BB956A630546F1/image-size/large?v=v2&amp;amp;px=999" role="button" title="Failed AD Diagnostic Tests.png" alt="Failed AD Diagnostic Tests.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt;The same tests on the physical appliances work.&lt;/P&gt;&lt;P&gt;On the AWS node an nslookup for&amp;nbsp;&lt;SPAN&gt;_ldap._tcp.dc._msdcs for the SRV records for domain is working.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;Any ideas?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Dec 2021 13:29:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4513898#M571478</guid>
      <dc:creator>pinglis</dc:creator>
      <dc:date>2021-12-06T13:29:21Z</dc:date>
    </item>
    <item>
      <title>Re: ISE In AWS Active Directory Diagnostic Tool test</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4513928#M571479</link>
      <description>&lt;P&gt;The physical appliances are not in AWS.&lt;/P&gt;
&lt;P&gt;Security Groups?&lt;/P&gt;
&lt;P&gt;Network ACLs?&lt;/P&gt;
&lt;P&gt;VPN firewall?&lt;/P&gt;
&lt;P&gt;Other firewall?&lt;/P&gt;
&lt;P&gt;See &lt;A href="https://www.cisco.com/c/en/us/td/docs/security/ise/3-1/install_guide/b_ise_InstallationGuide31/b_ise_InstallationGuide31_chapter_7.html#ID-1420-00000011" target="_blank"&gt;Cisco ISE Administration Node Ports&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Mon, 06 Dec 2021 14:48:48 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4513928#M571479</guid>
      <dc:creator>thomas</dc:creator>
      <dc:date>2021-12-06T14:48:48Z</dc:date>
    </item>
    <item>
      <title>Re: ISE In AWS Active Directory Diagnostic Tool test</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4513953#M571480</link>
      <description>&lt;P&gt;There may be some firewall rules/ACLs but I am unclear which DNS server the ISE node is using for the tests As I said nslookup from node cli itself seems to be working but I know this DNS server is a layer below the application itself. Could the ISE application be picking up a different DNS server?&lt;/P&gt;</description>
      <pubDate>Mon, 06 Dec 2021 15:25:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4513953#M571480</guid>
      <dc:creator>pinglis</dc:creator>
      <dc:date>2021-12-06T15:25:20Z</dc:date>
    </item>
    <item>
      <title>Re: ISE In AWS Active Directory Diagnostic Tool test</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4516403#M571580</link>
      <description>&lt;P&gt;It should be using whichever DNS servers you have configured when you provisioned it.&lt;/P&gt;
&lt;P&gt;You will need to SSH with your AWS private key to see the DNS server configuration with a `show run`.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Dec 2021 03:56:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4516403#M571580</guid>
      <dc:creator>thomas</dc:creator>
      <dc:date>2021-12-10T03:56:28Z</dc:date>
    </item>
    <item>
      <title>Re: ISE In AWS Active Directory Diagnostic Tool test</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4516595#M571595</link>
      <description>&lt;P&gt;The problem appears to be with the AWS based DNS server. Switching to on premise DNS servers resolves the issue.&amp;nbsp;&lt;/P&gt;&lt;P&gt;I m getting our DNS team to check the differences.&lt;/P&gt;</description>
      <pubDate>Fri, 10 Dec 2021 10:05:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-in-aws-active-directory-diagnostic-tool-test/m-p/4516595#M571595</guid>
      <dc:creator>pinglis</dc:creator>
      <dc:date>2021-12-10T10:05:40Z</dc:date>
    </item>
  </channel>
</rss>

