<?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 Authentication and Authorization help in Network Access Control</title>
    <link>https://community.cisco.com/t5/network-access-control/ise-authentication-and-authorization-help/m-p/5066555#M588692</link>
    <description>&lt;P&gt;Those two AuthProfiles were from another lab. To simplify things, I've removed them. Now, only PermitAccess is present. I've also fixed the IP address assigned to ISE1 and ISE2 in the Radius server configuration - they were 192,168.100 before. Now, they are 192.168.139.&lt;/P&gt;&lt;P&gt;I've bounced the switch port and Windows NIC, but it's still not pulling an IP address. More specifically, Windows reports "Unidentified Network" on the NIC. I'm missing something here. What might it be? The switch complained of the incorrect Radius addresses, but no longer. It also complained of authentication failure on eth0/1. That has stopped, too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 11 Apr 2024 16:10:44 GMT</pubDate>
    <dc:creator>DamianRCL</dc:creator>
    <dc:date>2024-04-11T16:10:44Z</dc:date>
    <item>
      <title>ISE Authentication and Authorization help</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-authentication-and-authorization-help/m-p/5066440#M588690</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm working on a lab and have hit a brick wall. I've attached a screenshot of the lab top, ISE live log report, and policy set. If I remove the 802.1x config from the interface, the W10 host gets an address on the 192.168.20 VLAN. Thomas'&amp;nbsp;&lt;A href="https://community.cisco.com/t5/security-knowledge-base/how-to-troubleshoot-ise-failed-authentications-amp/ta-p/3630960" target="_blank" rel="noopener"&gt;How To Troubleshoot ISE Failed Authentications &amp;amp; Authorizations&lt;/A&gt;&amp;nbsp;guide is great, but I still have issues. I would greatly appreciate any and all help.&lt;/P&gt;&lt;P&gt;Here's my switch configuration:&lt;/P&gt;&lt;P&gt;hostname SW2&lt;BR /&gt;!&lt;BR /&gt;boot-start-marker&lt;BR /&gt;boot-end-marker&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;aaa new-model&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;aaa group server radius ISE-GROUP&lt;BR /&gt;server name ISE1&lt;BR /&gt;server name ISE2&lt;BR /&gt;ip radius source-interface Vlan100&lt;BR /&gt;!&lt;BR /&gt;aaa authentication dot1x default group ISE-GROUP&lt;BR /&gt;aaa authorization network default group ISE-GROUP&lt;BR /&gt;aaa accounting update periodic 5&lt;BR /&gt;aaa accounting dot1x default start-stop group ISE-GROUP&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;aaa server radius dynamic-author&lt;BR /&gt;client 192.168.139.210 server-key 123Test&lt;BR /&gt;client 192.168.139.220 server-key 123Test&lt;BR /&gt;!&lt;BR /&gt;aaa session-id common&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;ip name-server 8.8.8.8&lt;BR /&gt;ip cef&lt;BR /&gt;no ipv6 cef&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;dot1x system-auth-control&lt;BR /&gt;!&lt;BR /&gt;spanning-tree mode pvst&lt;BR /&gt;spanning-tree extend system-id&lt;BR /&gt;!&lt;BR /&gt;no cdp run&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/0&lt;BR /&gt;switchport trunk encapsulation dot1q&lt;BR /&gt;switchport trunk native vlan 100&lt;BR /&gt;switchport mode trunk&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/1&lt;BR /&gt;description win10 node&lt;BR /&gt;switchport access vlan 20&lt;BR /&gt;switchport mode access&lt;BR /&gt;authentication event fail action next-method&lt;BR /&gt;authentication host-mode multi-auth&lt;BR /&gt;authentication order dot1x mab&lt;BR /&gt;authentication port-control auto&lt;BR /&gt;mab&lt;BR /&gt;dot1x pae authenticator&lt;BR /&gt;dot1x timeout tx-period 10&lt;BR /&gt;spanning-tree portfast edge&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/2&lt;BR /&gt;description win10 node&lt;BR /&gt;switchport access vlan 20&lt;BR /&gt;switchport mode access&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet0/3&lt;BR /&gt;description connected to Internet Router&lt;BR /&gt;no switchport&lt;BR /&gt;ip address 192.168.99.254 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet1/0&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet1/1&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet1/2&lt;BR /&gt;!&lt;BR /&gt;interface Ethernet1/3&lt;BR /&gt;!&lt;BR /&gt;interface Vlan1&lt;BR /&gt;no ip address&lt;BR /&gt;!&lt;BR /&gt;interface Vlan10&lt;BR /&gt;ip address 192.168.10.1 255.255.255.0&lt;BR /&gt;ip helper-address 192.168.46.230&lt;BR /&gt;ip helper-address 192.168.139.230&lt;BR /&gt;!&lt;BR /&gt;interface Vlan20&lt;BR /&gt;ip address 192.168.20.1 255.255.255.0&lt;BR /&gt;ip helper-address 192.168.139.230&lt;BR /&gt;!&lt;BR /&gt;interface Vlan30&lt;BR /&gt;ip address 192.168.30.1 255.255.255.0&lt;BR /&gt;ip helper-address 192.168.46.230&lt;BR /&gt;ip helper-address 192.168.139.230&lt;BR /&gt;!&lt;BR /&gt;interface Vlan40&lt;BR /&gt;ip address 192.168.40.1 255.255.255.0&lt;BR /&gt;ip helper-address 192.168.46.230&lt;BR /&gt;ip helper-address 192.168.139.230&lt;BR /&gt;!&lt;BR /&gt;interface Vlan100&lt;BR /&gt;ip address 192.168.139.254 255.255.255.0&lt;BR /&gt;!&lt;BR /&gt;ip forward-protocol nd&lt;BR /&gt;!&lt;BR /&gt;ip http server&lt;BR /&gt;ip http secure-server&lt;BR /&gt;!&lt;BR /&gt;ip route 0.0.0.0 0.0.0.0 192.168.99.1&lt;BR /&gt;ip ssh server algorithm encryption aes128-ctr aes192-ctr aes256-ctr&lt;BR /&gt;ip ssh client algorithm encryption aes128-ctr aes192-ctr aes256-ctr&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;snmp-server community 123Test RO&lt;BR /&gt;!&lt;BR /&gt;radius-server attribute 6 on-for-login-auth&lt;BR /&gt;radius-server attribute 8 include-in-access-req&lt;BR /&gt;radius-server attribute 25 access-request include&lt;BR /&gt;radius-server dead-criteria time 30 tries 3&lt;BR /&gt;radius-server timeout 2&lt;BR /&gt;!&lt;BR /&gt;radius server ISE1&lt;BR /&gt;address ipv4 192.168.139.210 auth-port 1812 acct-port 1813&lt;BR /&gt;key 123Test&lt;BR /&gt;!&lt;BR /&gt;radius server ISE2&lt;BR /&gt;address ipv4 192.168.139.220 auth-port 1812 acct-port 1813&lt;BR /&gt;key 123Test&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;control-plane&lt;BR /&gt;!&lt;BR /&gt;!&lt;BR /&gt;line con 0&lt;BR /&gt;logging synchronous&lt;BR /&gt;line aux 0&lt;BR /&gt;line vty 0 4&lt;BR /&gt;!&lt;BR /&gt;!&lt;/P&gt;&lt;P&gt;!&lt;BR /&gt;radius server ISE1&lt;BR /&gt;address ipv4 192.168.100.210 auth-port 1812 acct-port 1813&lt;BR /&gt;key 123Test&lt;BR /&gt;radius server ISE2&lt;BR /&gt;address ipv4 192.168.100.220 auth-port 1812 acct-port 1813&lt;BR /&gt;key 123Test&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-04-11 100718.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/215548i540746D93BBA4DCF/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screenshot 2024-04-11 100718.png" alt="Screenshot 2024-04-11 100718.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-04-11 100954.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/215549iD1BC0E1CDC142BC1/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screenshot 2024-04-11 100954.png" alt="Screenshot 2024-04-11 100954.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="Screenshot 2024-04-11 101432.png" style="width: 400px;"&gt;&lt;img src="https://community.cisco.com/t5/image/serverpage/image-id/215550i33E8C214D053F7A5/image-size/medium?v=v2&amp;amp;px=400" role="button" title="Screenshot 2024-04-11 101432.png" alt="Screenshot 2024-04-11 101432.png" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;P&gt; &lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 14:28:13 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-authentication-and-authorization-help/m-p/5066440#M588690</guid>
      <dc:creator>DamianRCL</dc:creator>
      <dc:date>2024-04-11T14:28:13Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Authentication and Authorization help</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-authentication-and-authorization-help/m-p/5066498#M588691</link>
      <description>&lt;P&gt;Why are you sending two AuthZ results?&amp;nbsp; Permit access and "Authorization Employee/Contractor".&amp;nbsp; What do the logs on the switch show?&amp;nbsp; What exactly is in those two authz profiles?&amp;nbsp; Does it work if you put PermitAccess authz profile?&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 15:15:24 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-authentication-and-authorization-help/m-p/5066498#M588691</guid>
      <dc:creator>ahollifield</dc:creator>
      <dc:date>2024-04-11T15:15:24Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Authentication and Authorization help</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-authentication-and-authorization-help/m-p/5066555#M588692</link>
      <description>&lt;P&gt;Those two AuthProfiles were from another lab. To simplify things, I've removed them. Now, only PermitAccess is present. I've also fixed the IP address assigned to ISE1 and ISE2 in the Radius server configuration - they were 192,168.100 before. Now, they are 192.168.139.&lt;/P&gt;&lt;P&gt;I've bounced the switch port and Windows NIC, but it's still not pulling an IP address. More specifically, Windows reports "Unidentified Network" on the NIC. I'm missing something here. What might it be? The switch complained of the incorrect Radius addresses, but no longer. It also complained of authentication failure on eth0/1. That has stopped, too.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 16:10:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-authentication-and-authorization-help/m-p/5066555#M588692</guid>
      <dc:creator>DamianRCL</dc:creator>
      <dc:date>2024-04-11T16:10:44Z</dc:date>
    </item>
    <item>
      <title>Re: ISE Authentication and Authorization help</title>
      <link>https://community.cisco.com/t5/network-access-control/ise-authentication-and-authorization-help/m-p/5066590#M588694</link>
      <description>&lt;P&gt;ahollifield,&lt;/P&gt;&lt;P&gt;Things are working now. I wanted to dynamically assign an IP address to the host. That couldn't happen without an auth policy, so I assigned the 'Authorization Employees' profile, which assigns VLAN 10, to the 'Authorization Employee' policy. I think my other issue was having the wrong RADIUS address.&lt;/P&gt;&lt;P&gt;Thank you!&lt;/P&gt;</description>
      <pubDate>Thu, 11 Apr 2024 16:48:44 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-access-control/ise-authentication-and-authorization-help/m-p/5066590#M588694</guid>
      <dc:creator>DamianRCL</dc:creator>
      <dc:date>2024-04-11T16:48:44Z</dc:date>
    </item>
  </channel>
</rss>

