Re: !! PEAP/MSCHAPV2 : Windows CLient works, NOT the intel Client .. !!

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Your non Microsoft supplicant might be using an incompatible version of PEAP
I recommend that you use the Windows supplied supplicant


--
=============================================
This posting is provided "AS IS" with no warranties, and confers no rights
=============================================

"me" <me@xxxxx> wrote in message
news:OO0XVomqFHA.1336@xxxxxxxxxxxxxxxxxxxxxxx
> Hello,
> I have a Windows Server 2003 Radius server with IAS and a strange thing :
>
> The connection works fine with the Windows XP (SP2) Client but not with
> the Intel Client ( 2200BG Wireless card). I good parameter the PEAP and
> the MSCHAPV2 but i still have this error :
>
>
> Description :
> L'accès a été refusé à l'utilisateur user@mydomain
> ..........................
> Adresse-IP-NAS = 172.19.10.10
> Identificateur-NAS = AP1121-P1-01
> Identificateur-Station-Appelée = 0013.19a5.0a6e
> Identificateur-Station-Appelante = 000e.356c.704c
> Nom-Convivial-Client = 172.19.10.10
> Adresse-IP-Client = 172.19.10.10
> Type-Port-NAS = Wireless - IEEE 802.11
> Port-NAS = 268
> Proxy-Policy-Name = .......
> Authentication-Provider = Windows
> Authentication-Server = <undetermined>>
> Policy-Name = WIFI19
> Authentication-Type = PEAP
> EAP-Type = <undetermined>
> Reason-Code = 16
> Reason = There was an authentication failure because of an unknown user
> name
> or a bad password.
>
>
> => with the windows CLient, i have this : EAP-TYPE= secure password
> (EAP-MSCHAP Version 2)
> I use CISCO 1100 with last IOS ...
>
> Where could i do a good debug ? Cisco ??
>
> Thanks a lot !
>
>
>
>
>
>


.

Relevant Pages

  • Re: WiFi Authentication Options
    ... Zero Config dialog pop up in front of our application, ... >I think that you should be able to use PEAP with OpenNETCF's .Net namespace ... >> to use PEAP to authenticate devices to a wireless network. ... >> is that these are Windows CE devices, and Microsoft has not released APIs ...
    (microsoft.public.dotnet.framework.compactframework)
  • WiFi Authentication Options
    ... use PEAP to authenticate devices to a wireless network. ... these are Windows CE devices, and Microsoft has not released APIs to ... communicate with the "Zero Configuration Utility", ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: WiFi Authentication Options
    ... What version of Windows CE are you targeting? ... provided by MS for replacing the various network UIs and the documentation ... If that's not a fair assumption, you can dive in and look at the EAP fields ... >> supports PEAP, ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: WiFi Authentication Options
    ... I think that you should be able to use PEAP with OpenNETCF's .Net namespace ... > use PEAP to authenticate devices to a wireless network. ... > that these are Windows CE devices, and Microsoft has not released APIs to ... > Outside of the various EAP flavors, what security options have you all ...
    (microsoft.public.dotnet.framework.compactframework)
  • Re: IAS as RADIUS
    ... The "supplicant" is a piece of software on the client PC. ... developed to prevent unauthorized PC's from being placed on the network. ... We're in a non AD enviroment, have windows and linux servers, and catalyst ...
    (microsoft.public.windows.server.networking)