NAM installation after Native supplicant

[tommy182]

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

[Mike.Cifelli]

Upon installation of NAM that should take priority over the native supplicant. How is your NAM profile configured? Can you share? I have configured both at the same time without problems where NAM (eap-fast) always occurs and works just fine. Also, out of curiosity what windows version?

[tommy182]

Sure, I`ve inserted here configuration.xml content

On the particular testing PC win10 LTSB installed.