Re: No EAP Start, assuming it's an on-going EAP conversation

dvmp wrote:

mschap validation occur with success but wireless client can't authenticate.

So... read the entire debug log.

On several tests when run radiusd -X and force join to Active Directory, during the next 2 ou 3 minutes clients can authenticate with success.

I'm not sure what that means.

Difference between logs:

*Not Authenticate:*

[eap] EAP packet type response id 2 length 25

[eap] No EAP Start, assuming it's an on-going EAP conversation

I don't think that matters.

EAP isn't happening ?

No idea. You posted the logs when it works. That doesn't help.

Follow, all the radiusd -X when start:

That doesn't help, either. You need to post the FULL LOGS from WHEN IT FAILS. I have no idea why this is a difficult concept. Alan DeKok.