This kind of Q&A thing helps no one here! Many people are reporting the same issue on different platforms! I don't think the problem is either with the client or the certificates since I conducted some testing using the same client and the same certificates but an old FR version (1.1.7) and the tests pass. It's easier to blame something else but we could spend that time contributing to the solution and so helping others!
Date: Wed, 26 Oct 2011 15:36:19 +0200 From: aland@deployingradius.com To: freeradius-users@lists.freeradius.org Subject: Re: PEAP with Machine auth
Phil Mayers wrote:
Seriously - it's important to understand that the CLIENT stops responding. FreeRADIUS can't do anything more in this case - the client has stopped sending EAPOL packets, so the client must think that something is wrong.
That's the main issue people have with RADIUS. The client is in charge of pretty much everything, and few people understand that.
Q: Why does the client stop talking to the server? A: Because it doesn't like the response from the server
Q: OK... *what* part of the response doesn't it like? A: Go ask the client
Q: But I can't! What do I do? A: well... we don't know, either. Go ask Microsoft.
You will have to debug the client. This is very very painful on Windows; it's hard to even find the EAPOL debugging options, let alone interpret the results.
Yes. Everyone reading this list should understand CLIENT issues cause you to debug the CLIENT.
If the server returns the wrong thing... you can fix the server. Fort pretty much everything else, blame the client.
Alan DeKok. - List info/subscribe/unsubscribe? See http://www.freeradius.org/list/users.html