08-21-2019 09:47 AM
Hello, Friends!
We used Native Win supplicant earlier with PEAP method.
Recently we decided to install AC NAM(with EAP-FAST) on top of it.
I see weird behavior after host reloaded.
The PC firstly trying to Auth using PEAP, looks like Native supplicant still alive and functional.
The second Auth attempt(~200msec later) going through EAP-FAST(the AC NAM wake up =) ) and completes correctly.
First attempt through PEAP looks in ISE as abandoned session by supplicant.
Is it normal? I thought the AC NAM completely replace native supplicant or wee need to somehow disable it (GPO etc)
Thanks,
Artyom
08-22-2019 05:38 AM
08-22-2019 06:22 AM
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: