AD Authentication + radius + foundryAP

[Mark Pipkin]

>  What does that look like to you?
	
Looks like it is trying to use PAP to authenticate with. Though PAP is
local only, at least from what I can tell, and there is no local
user/pass for this account.  Then it looks like it rolls to a EAP/leap
authentication method.  At this point it fails.

>  Are the debug messages helpful?

If I truly understood more, then I'm sure that they would be.  That are
not as helpful for me; I have a lack of understanding at this point in
time.

>  Do they accurately describe the problem, and give you hints for the
solution?

I just see the problem as not working.  I don't understand why it didn't
even attempt mschapv2 when eap default was set to peap and peap default
was set to mschapv2.

>> I don't know much about FreeRadius.  I have never had to work with a
>> radius server of any type before.  I do apologize, but while this
stuff
>> might be obvious to someone that created it or works in radius
servers
>> every day of the week, I am not that person.  So to me, the only
obvious
>> thing is that I get rejected at leap, while another radius server
that
>> is running FreeRadius 1.x on Getoo is working just find with
mschapv2.

>  The PC is choosing LEAP, not FreeRADIUS.

I'm using Win7.  Are you telling me that the PC is the one that is
picking the security for the radius and not the Foundry Wireless AP
controller?  

>  Configure the PC to use LEAP, as was suggested in *another* response
to your post.

I read that post.  I thought the he was referring to the Foundry AP
controller.  You just told me that it was the fault of the PC though.


Mark Pipkin