<?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 We are running into the exact in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942822#M38886</link>
    <description>&lt;P&gt;We are running into the exact same issue. Strange thing is wireless works without a problem. it is only affecting wired 802.1x.&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Tue, 18 Oct 2016 19:22:40 GMT</pubDate>
    <dc:creator>Ryan McDonald</dc:creator>
    <dc:date>2016-10-18T19:22:40Z</dc:date>
    <item>
      <title>EAP Chaining not working with Cisco NAM, ISE 2.0 and Windows 10</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942819#M38873</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;
&lt;P&gt;I have Windows 10 machines and i am trying to deploy Wired 802.1X for both machine and user authentication as clearly explained on the below link&lt;/P&gt;
&lt;P&gt;&lt;A href="http://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/design-zone-security/howto_80_eapchaining_deployment.pdf" target="_blank"&gt;http://www.cisco.com/c/dam/en/us/solutions/collateral/enterprise/design-zone-security/howto_80_eapchaining_deployment.pdf&lt;/A&gt;&lt;/P&gt;
&lt;P&gt;I also have Cisco NAM supplicant 4.3 installed on end user devices and i am using EAP-FAST for authentication of users.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;The problem is that it is kind of a hit and miss at the moment, It works sometimes, sometimes not. Surprisingly, I am prompted to re-enter credentials on the Cisco NAM client and i am still not able to authenticate using the right user credentials. I notice on the Cisco ISE radius logs that sometimes the windows machine sends the wrong username to ISE which results in authentication failure. The machine mac address is sent or anonymous as a username.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Does anyone have a solution on better way to deploy Wired 802.1X for Windows 10 using Cisco NAM and ISE 2.0? The most surprising is it does work sometimes and sometimes not. I also tried using Windows native supplicant and still not successful.&lt;/P&gt;
&lt;P&gt;I did run a few Wireshark traces on the test machine while authenticating and it looks like the PC is submitting the right username, but to my surprise the ISE logs show a failed authentication message for the username anonymous.&lt;/P&gt;
&lt;P&gt;I tried fine tuning the xml configuration file for NAM thinking it would be a problem, but no luck with that.&lt;/P&gt;
&lt;P&gt;Any help or guidance or is very much appreciated !&lt;/P&gt;
&lt;P&gt;For Wireless 802.1X using ISE 2.0 as a radius server and the NAM supplicant on Windows 10, all works with no issues&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks in advance for any help on this !&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 06:58:21 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942819#M38873</guid>
      <dc:creator>abukuru95</dc:creator>
      <dc:date>2019-03-11T06:58:21Z</dc:date>
    </item>
    <item>
      <title>The below has worked for me.</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942820#M38878</link>
      <description>&lt;P&gt;The below has worked for me.&lt;/P&gt;
&lt;P&gt;&lt;A href="https://support.microsoft.com/en-us/kb/2743127"&gt;https://support.microsoft.com/en-us/kb/2743127&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 14:44:04 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942820#M38878</guid>
      <dc:creator>abukuru95</dc:creator>
      <dc:date>2016-09-01T14:44:04Z</dc:date>
    </item>
    <item>
      <title>Could you give us the RADIUS</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942821#M38884</link>
      <description>&lt;P&gt;Could you give us the RADIUS Livelog, NAM Profile, and Windows NIC 802.1X configuration for the failed authentication?&lt;/P&gt;</description>
      <pubDate>Thu, 01 Sep 2016 15:15:11 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942821#M38884</guid>
      <dc:creator>myachi991</dc:creator>
      <dc:date>2016-09-01T15:15:11Z</dc:date>
    </item>
    <item>
      <title>We are running into the exact</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942822#M38886</link>
      <description>&lt;P&gt;We are running into the exact same issue. Strange thing is wireless works without a problem. it is only affecting wired 802.1x.&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2016 19:22:40 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942822#M38886</guid>
      <dc:creator>Ryan McDonald</dc:creator>
      <dc:date>2016-10-18T19:22:40Z</dc:date>
    </item>
    <item>
      <title>the link you provided applies</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942823#M38887</link>
      <description>&lt;P&gt;the link you provided applies to windows 8 not windows 10.&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2016 19:25:28 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942823#M38887</guid>
      <dc:creator>Ryan McDonald</dc:creator>
      <dc:date>2016-10-18T19:25:28Z</dc:date>
    </item>
    <item>
      <title>Hi Ryan,</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942824#M38888</link>
      <description>&lt;P&gt;Hi Ryan,&lt;/P&gt;
&lt;P&gt;It applies to windows 8 but also works for windows 10. The odd thing is that i also had it working well for wireless, but not wired.&lt;/P&gt;
&lt;P&gt;I upgraded to the latest Anyconnect client version, applied the fix and it has since been working for me.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;What error message do you see on your ISE/ACS logs for these failed connections? Does the Anyconnect client keep prompting to you to enter login credentials each time.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;please rate if this helps!&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2016 19:59:42 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942824#M38888</guid>
      <dc:creator>abukuru95</dc:creator>
      <dc:date>2016-10-18T19:59:42Z</dc:date>
    </item>
    <item>
      <title>ISE fails because it is</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942825#M38889</link>
      <description>&lt;P style="padding-left: 30px;"&gt;ISE fails because it is getting the mac address rather than the user ID. we are on 4.3.03086 and are still having the issue how did you fix it?&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2016 20:22:26 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942825#M38889</guid>
      <dc:creator>Ryan McDonald</dc:creator>
      <dc:date>2016-10-18T20:22:26Z</dc:date>
    </item>
    <item>
      <title>Have you tried the suggested</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942826#M38890</link>
      <description>&lt;P&gt;Have you tried the suggested registry fix below? This works for me on windows 10 machines.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;https://support.microsoft.com/en-us/kb/2743127&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 18 Oct 2016 21:06:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942826#M38890</guid>
      <dc:creator>abukuru95</dc:creator>
      <dc:date>2016-10-18T21:06:30Z</dc:date>
    </item>
    <item>
      <title>yep just tried.  No change,</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942827#M38891</link>
      <description>&lt;P&gt;yep just tried. &amp;nbsp;No change, still not working correctly. I'm going to open a tac case.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 19 Oct 2016 15:25:46 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942827#M38891</guid>
      <dc:creator>Ryan McDonald</dc:creator>
      <dc:date>2016-10-19T15:25:46Z</dc:date>
    </item>
    <item>
      <title>Hi</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942828#M38892</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I have same issue.I'm runing ISE2.1 with AnyConnect 4.3 NAM and posture module.&lt;/P&gt;
&lt;P&gt;I have done the Lsa registry hack for windows 8.&lt;/P&gt;
&lt;P&gt;Issue is first time when we connect Laptop to Switch(Wired) it get authenticated and get postured.But if logoff an login it get&amp;nbsp; authentication failed.Once this authentication fails happens it will not get authenticated for sometime(1hr). Then it automatically get authenticated.In unsuccessful scenario AnyConnect keep prompting credentials.Switch shows dot1x failed syslog massage.But ther is no log in ISE live log.&lt;/P&gt;
&lt;P&gt;Some times it show anonymous identity log.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2016 14:15:03 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942828#M38892</guid>
      <dc:creator>Ridma Ransara Jayaweera</dc:creator>
      <dc:date>2016-10-26T14:15:03Z</dc:date>
    </item>
    <item>
      <title>Hi Ryan</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942829#M38893</link>
      <description>&lt;P&gt;Hi Ryan&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Can you share configuration.xml and the port configuration.&lt;/P&gt;
&lt;P&gt;Thanks&lt;/P&gt;</description>
      <pubDate>Wed, 26 Oct 2016 14:17:34 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942829#M38893</guid>
      <dc:creator>Ridma Ransara Jayaweera</dc:creator>
      <dc:date>2016-10-26T14:17:34Z</dc:date>
    </item>
    <item>
      <title>the microsoft link is no</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942830#M38894</link>
      <description>&lt;P&gt;the microsoft link is no longer valid, seeing this as well on windows 10&lt;/P&gt;</description>
      <pubDate>Mon, 06 Feb 2017 19:38:52 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/2942830#M38894</guid>
      <dc:creator>Jeffrey Jones</dc:creator>
      <dc:date>2017-02-06T19:38:52Z</dc:date>
    </item>
    <item>
      <title>Re: We are running into the exact</title>
      <link>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/3410412#M38895</link>
      <description>&lt;P&gt;Hi I have the same issue sometimes getting on wireless and sometimes on wired&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Does anybody have a fix .. I have machine certificate based authentication + User authentication&amp;nbsp; with EAP FAST&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Jul 2018 18:50:01 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/eap-chaining-not-working-with-cisco-nam-ise-2-0-and-windows-10/m-p/3410412#M38895</guid>
      <dc:creator>CCertified85</dc:creator>
      <dc:date>2018-07-04T18:50:01Z</dc:date>
    </item>
  </channel>
</rss>

