08-21-2022 08:07 PM
Hi
I have windows 10 with TEAP (mschap-v2) and native windows supplicant, all windows fine with connectivity and ISE. My problem begin when I execute Remote Desktop between PC windows with TEAP 802.1X. Remote Desktop can't works fine and the connection it's not successful.
Microsoft say adjust connection type to "user or computer", but this don't solve it
please someone have an idea?
Solved! Go to Solution.
08-22-2022 03:36 PM
As stated in the link shared below, the Windows supplicant does not initiate an 802.1x session when an RDP login happens. The only workaround is to use AnyConnect NAM as the supplicant instead of the native supplicant.
AnyConnect NAM supports EAP-FAST for EAP Chaining. This support actually pre-dates TEAP and was the basis for the standards-based TEAP protocol.
08-21-2022 09:56 PM
so you have 2 PC authenticated with 802.1X and working and when you initiate RDP between them RDP connection it does not work ?
what does your authorization policy looks like ?
08-21-2022 10:08 PM
08-22-2022 08:29 AM
what does the authorization policy look like for these PCs ? are you pushing any dynamic ACL as part of authorization or dynamic vlan, any ACL on VLAN SVI ?
08-22-2022 09:04 AM
08-22-2022 10:21 AM
I remember reading some limitation on this with windows native supplicant, not able to find the document, do you think you can try with Cisco NAM.
try this workaround with NAM see if it helps.
08-22-2022 12:09 PM
08-22-2022 03:36 PM
As stated in the link shared below, the Windows supplicant does not initiate an 802.1x session when an RDP login happens. The only workaround is to use AnyConnect NAM as the supplicant instead of the native supplicant.
AnyConnect NAM supports EAP-FAST for EAP Chaining. This support actually pre-dates TEAP and was the basis for the standards-based TEAP protocol.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide