<?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 Just to let you know, we in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090990#M25531</link>
    <description>&lt;P&gt;Just to let you know, we raised a TAC case to investigate this, as we were troubleshooting Win10 logins. The TAC engineer confirmed there is no way to see what devices are in the MAR Cache, which is a bit of a shame.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
    <pubDate>Wed, 16 Aug 2017 20:08:25 GMT</pubDate>
    <dc:creator>JAMES WEST</dc:creator>
    <dc:date>2017-08-16T20:08:25Z</dc:date>
    <item>
      <title>Cisco ISE MAR Cache</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090984#M25503</link>
      <description>&lt;P&gt;Hello All.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I am looking at deploying 802.1x being authenticated against ISE, and l have the following 2 questions:&lt;/P&gt;
&lt;OL&gt;
&lt;LI&gt;Can ISE authenticate both Wired &amp;amp; Wireless windows machine, without using AnyConnect? Or is it a case that ISE autenticates the Wired Machine Auth, and if the user then moves onto their Wireless adaptor, this will not be in the MAR cache, so the machine is not authenticated and wireless does not work.&lt;/LI&gt;
&lt;LI&gt;How do you determine what Machines/Devices are in the MAR cache?&lt;/LI&gt;
&lt;/OL&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;James&lt;/P&gt;</description>
      <pubDate>Mon, 11 Mar 2019 07:55:30 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090984#M25503</guid>
      <dc:creator>JAMES WEST</dc:creator>
      <dc:date>2019-03-11T07:55:30Z</dc:date>
    </item>
    <item>
      <title>Hi James,</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090985#M25504</link>
      <description>&lt;P&gt;Hi James,&lt;/P&gt;
&lt;P&gt;Yes, ISE can authenticate windows machine, when connected to a wired or wireless network. Specify this in the Windows AD GPO when using native windows supplicant.&lt;/P&gt;
&lt;P&gt;I've not used MAR, but you are correct. A wired and wireless machine authentication are classed as 2 seperate authentications (different adapter mac addresses), thus causing an issue when you want to chain machine + user authentications. Only EAP Chaining which requires AnyConnec, this can properly combine machine + user authentications and not break when the laptop moves from being connected to a wifi network then connected to a wired network.&lt;/P&gt;
&lt;P&gt;HTH&lt;/P&gt;</description>
      <pubDate>Thu, 10 Aug 2017 18:00:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090985#M25504</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2017-08-10T18:00:09Z</dc:date>
    </item>
    <item>
      <title>Hi Rob,</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090986#M25505</link>
      <description>&lt;P&gt;Hi Rob,&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks for your response and clarifying what l thought may be the case.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;James&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2017 08:04:17 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090986#M25505</guid>
      <dc:creator>JAMES WEST</dc:creator>
      <dc:date>2017-08-11T08:04:17Z</dc:date>
    </item>
    <item>
      <title>Following on from Rob's help</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090987#M25514</link>
      <description>&lt;P&gt;Following on from Rob's help above, if we wanted to implement the following would this allow wired &amp;amp; wireless authentication:&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;I believe the "username" for machines when using PEAP is something like this "host/FQDN..." Thus, you could probably use a rule that states if the RADIUS username "contains" either your domain or a pattern used by machines on your domain.&lt;/P&gt;
&lt;P&gt;However, the easiest way to distinguish between domain joined and non-domain joined is the have ISE check with AD. Thus, your rule can have something like this:&lt;/P&gt;
&lt;P&gt;1. If "external group" = "domain computers"&lt;/P&gt;
&lt;P&gt;2. If "identity access restricted" = "false"&lt;/P&gt;
&lt;P&gt;3. Then "full access"&lt;/P&gt;
&lt;P&gt;This will ensure that the computer that is trying to authenticate and authorize on the network is actually joined to the domain. One thing you will need to make sure that your AD is locked down because I think by default any domain users can join up to 10 workstations to the domain.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2017 08:29:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090987#M25514</guid>
      <dc:creator>JAMES WEST</dc:creator>
      <dc:date>2017-08-11T08:29:44Z</dc:date>
    </item>
    <item>
      <title>The AD Probe will also be</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090988#M25522</link>
      <description>&lt;P&gt;The AD Probe will also be able to determine whether a machine is joined to AD.&lt;/P&gt;</description>
      <pubDate>Fri, 11 Aug 2017 14:09:33 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090988#M25522</guid>
      <dc:creator>Rob Ingram</dc:creator>
      <dc:date>2017-08-11T14:09:33Z</dc:date>
    </item>
    <item>
      <title>In addition to Rob's comments</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090989#M25529</link>
      <description>&lt;P&gt;In addition to Rob's comments.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Does anyone one know how to find what machines have been added to the MAR Cache? If so, can you let me know.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;
&lt;P&gt;Thanks,&lt;/P&gt;
&lt;P&gt;James&lt;/P&gt;</description>
      <pubDate>Tue, 15 Aug 2017 16:28:06 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090989#M25529</guid>
      <dc:creator>JAMES WEST</dc:creator>
      <dc:date>2017-08-15T16:28:06Z</dc:date>
    </item>
    <item>
      <title>Just to let you know, we</title>
      <link>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090990#M25531</link>
      <description>&lt;P&gt;Just to let you know, we raised a TAC case to investigate this, as we were troubleshooting Win10 logins. The TAC engineer confirmed there is no way to see what devices are in the MAR Cache, which is a bit of a shame.&lt;/P&gt;
&lt;P&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 16 Aug 2017 20:08:25 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/cisco-ise-mar-cache/m-p/3090990#M25531</guid>
      <dc:creator>JAMES WEST</dc:creator>
      <dc:date>2017-08-16T20:08:25Z</dc:date>
    </item>
  </channel>
</rss>

