Windows PEAP failure in FreeRADIUS 3.1

Scott Armitage S.P.Armitage at lboro.ac.uk
Tue Mar 1 15:35:36 CET 2016


> On 1 Mar 2016, at 14:29, Matthew Newton <mcn4 at leicester.ac.uk> wrote:
> 
> On Tue, Mar 01, 2016 at 02:12:51PM +0000, Scott Armitage wrote:
>> When using FreeRADIUS v3.1 Windows devices fail to authenticate
>> using PEAP.  Other OS work fine but Windows fails.  If I use a
>> client cert and EAP-TLS windows succeeds.  It appears the
>> Windows devices stop responding after the establishment of the
>> PEAP tunnel.  Can anyone point out where I am going wrong:
> 
> Does the same certificate/config work OK on FR3.0?
> 

Same cert and ciphers works fine for FR 2.2.9
I haven’t tried FR 3


> We've got Windows machine authenticating with PEAP/EAP-TLS on 3.0
> and 3.1 both fine, so I wouldn't think it's a fundamental issue
> with PEAP alone.

Its useful to know that it should work :-) and is most likely a configuration issue.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.freeradius.org/pipermail/freeradius-users/attachments/20160301/be924141/attachment.sig>


More information about the Freeradius-Users mailing list