<?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 No, we are not  and just in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-and-windows-8-eap-chaining-failing-with-computer/m-p/2683805#M54983</link>
    <description>&lt;P&gt;No, we are not &amp;nbsp;and just using AD groups for authentication and with Windows 8 - I get the computer password is wrong and even with this fix - still no resolution&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;below are the details -&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;M: Windows 8 Machine Auth not working.&lt;/P&gt;&lt;P&gt;CSCuc13862&lt;/P&gt;&lt;P&gt;&lt;A name="description"&gt;&lt;STRONG&gt;Description&lt;/STRONG&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Symptom:&lt;/STRONG&gt;&lt;BR /&gt;Machine authentication using machine password will not work on Windows 8 /&amp;nbsp;&lt;BR /&gt;Server 2012.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Conditions:&lt;/STRONG&gt;&lt;BR /&gt;Windows 8 and Windows Server 2012 platforms.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;BR /&gt;Registry fix described in Microsoft KB 2743127&amp;nbsp;&lt;BR /&gt;(&lt;A href="http://support.microsoft.com/kb/2743127)" target="_blank"&gt;http://support.microsoft.com/kb/2743127)&lt;/A&gt;&amp;nbsp;needs to be applied to the client&amp;nbsp;&lt;BR /&gt;desktop. This fix includes adding a DWORD value&amp;nbsp;&lt;BR /&gt;LsaAllowReturningUnencryptedSecrets to the&amp;nbsp;&lt;BR /&gt;HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa registry key and&amp;nbsp;&lt;BR /&gt;setting this value to 1. This change permits Local Security Authority (LSA)&amp;nbsp;&lt;BR /&gt;to provide clients like Cisco Network Access Manager with the Machine&amp;nbsp;&lt;BR /&gt;password. It is related to the increased default security settings in Windows&amp;nbsp;&lt;BR /&gt;8 / Server 2012. Machine authentication using Machine certificate does not&amp;nbsp;&lt;BR /&gt;require this change and will work the same as it worked with pre Windows 8&amp;nbsp;&lt;BR /&gt;OSes.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Note:&lt;/STRONG&gt;&lt;BR /&gt;Machine authentication allows a client desktop to be authenticated to the&amp;nbsp;&lt;BR /&gt;server before the user logs in. During this time server can perform scheduled&amp;nbsp;&lt;BR /&gt;administrative tasks for this client machine. Machine authentication is also&amp;nbsp;&lt;BR /&gt;required for the EAP Chaining feature where a server can authenticate both&amp;nbsp;&lt;BR /&gt;User and Machine for a particular client. This will result in identifying&amp;nbsp;&lt;BR /&gt;company assets and applying appropriate access policy. For example, if this&amp;nbsp;&lt;BR /&gt;is a personal asset (PC/laptop/tablet), and a company login is used, server&amp;nbsp;&lt;BR /&gt;will fail Machine authentication, but succeed User authentication and will&amp;nbsp;&lt;BR /&gt;apply proper access restrictions to this client desktop.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 01 Jul 2015 03:19:27 GMT</pubDate>
    <dc:creator>kanwar</dc:creator>
    <dc:date>2015-07-01T03:19:27Z</dc:date>
    <item>
      <title>Cisco ISE 1.3 and Windows 8 EAP chaining failing with computer Password</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-and-windows-8-eap-chaining-failing-with-computer/m-p/2683803#M54978</link>
      <description>&lt;P&gt;I have a Windows 8 laptop with registry fix applied for computer name password issue and still not able to get authenticated with ISE&amp;nbsp;&lt;/P&gt;&lt;P&gt;was just wondering if that is a known issue out there ??&lt;/P&gt;&lt;P&gt;Thanks&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 05:51:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-and-windows-8-eap-chaining-failing-with-computer/m-p/2683803#M54978</guid>
      <dc:creator>kanwar</dc:creator>
      <dc:date>2019-03-11T05:51:25Z</dc:date>
    </item>
    <item>
      <title>Can you expand on what you</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-and-windows-8-eap-chaining-failing-with-computer/m-p/2683804#M54981</link>
      <description>&lt;P&gt;Can you expand on what you mean by computer name password issue? Are you using certificates?&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2015 03:14:58 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-and-windows-8-eap-chaining-failing-with-computer/m-p/2683804#M54981</guid>
      <dc:creator>franklinb</dc:creator>
      <dc:date>2015-07-01T03:14:58Z</dc:date>
    </item>
    <item>
      <title>No, we are not  and just</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-and-windows-8-eap-chaining-failing-with-computer/m-p/2683805#M54983</link>
      <description>&lt;P&gt;No, we are not &amp;nbsp;and just using AD groups for authentication and with Windows 8 - I get the computer password is wrong and even with this fix - still no resolution&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;below are the details -&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;M: Windows 8 Machine Auth not working.&lt;/P&gt;&lt;P&gt;CSCuc13862&lt;/P&gt;&lt;P&gt;&lt;A name="description"&gt;&lt;STRONG&gt;Description&lt;/STRONG&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;BR /&gt;&lt;STRONG&gt;Symptom:&lt;/STRONG&gt;&lt;BR /&gt;Machine authentication using machine password will not work on Windows 8 /&amp;nbsp;&lt;BR /&gt;Server 2012.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Conditions:&lt;/STRONG&gt;&lt;BR /&gt;Windows 8 and Windows Server 2012 platforms.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Workaround:&lt;/STRONG&gt;&lt;BR /&gt;Registry fix described in Microsoft KB 2743127&amp;nbsp;&lt;BR /&gt;(&lt;A href="http://support.microsoft.com/kb/2743127)" target="_blank"&gt;http://support.microsoft.com/kb/2743127)&lt;/A&gt;&amp;nbsp;needs to be applied to the client&amp;nbsp;&lt;BR /&gt;desktop. This fix includes adding a DWORD value&amp;nbsp;&lt;BR /&gt;LsaAllowReturningUnencryptedSecrets to the&amp;nbsp;&lt;BR /&gt;HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa registry key and&amp;nbsp;&lt;BR /&gt;setting this value to 1. This change permits Local Security Authority (LSA)&amp;nbsp;&lt;BR /&gt;to provide clients like Cisco Network Access Manager with the Machine&amp;nbsp;&lt;BR /&gt;password. It is related to the increased default security settings in Windows&amp;nbsp;&lt;BR /&gt;8 / Server 2012. Machine authentication using Machine certificate does not&amp;nbsp;&lt;BR /&gt;require this change and will work the same as it worked with pre Windows 8&amp;nbsp;&lt;BR /&gt;OSes.&lt;BR /&gt;&lt;BR /&gt;&lt;STRONG&gt;Note:&lt;/STRONG&gt;&lt;BR /&gt;Machine authentication allows a client desktop to be authenticated to the&amp;nbsp;&lt;BR /&gt;server before the user logs in. During this time server can perform scheduled&amp;nbsp;&lt;BR /&gt;administrative tasks for this client machine. Machine authentication is also&amp;nbsp;&lt;BR /&gt;required for the EAP Chaining feature where a server can authenticate both&amp;nbsp;&lt;BR /&gt;User and Machine for a particular client. This will result in identifying&amp;nbsp;&lt;BR /&gt;company assets and applying appropriate access policy. For example, if this&amp;nbsp;&lt;BR /&gt;is a personal asset (PC/laptop/tablet), and a company login is used, server&amp;nbsp;&lt;BR /&gt;will fail Machine authentication, but succeed User authentication and will&amp;nbsp;&lt;BR /&gt;apply proper access restrictions to this client desktop.&lt;BR /&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 01 Jul 2015 03:19:27 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-and-windows-8-eap-chaining-failing-with-computer/m-p/2683805#M54983</guid>
      <dc:creator>kanwar</dc:creator>
      <dc:date>2015-07-01T03:19:27Z</dc:date>
    </item>
    <item>
      <title>this is the fix for windows</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-and-windows-8-eap-chaining-failing-with-computer/m-p/2683806#M54984</link>
      <description>&lt;P&gt;this is the fix for windows 10 on desktop/laptops and my surface as well.&amp;nbsp; i had the same issue.&lt;/P&gt;</description>
      <pubDate>Wed, 11 May 2016 17:45:20 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-1-3-and-windows-8-eap-chaining-failing-with-computer/m-p/2683806#M54984</guid>
      <dc:creator>Neal Gravatt</dc:creator>
      <dc:date>2016-05-11T17:45:20Z</dc:date>
    </item>
  </channel>
</rss>

