Re: WM6 + PEAP/MSCHAPv2

The registry hack worked on Sprint HTC Mogul (WM6):
\HKLM\Comm\EAP\Extension\25\ValidateServerCert=dword:00000000

Thanks.



"Eric Hicks [MVP]" wrote:

When you setup the wireless conenctions make sure the last page of the setup
is set to PEAP not Smart Car or Certificate

--
--
Eric Hicks [That_Kid] (MS-MVP Mobile Devices)

The MS-MVP Program - http://mvp.support. microsoft.com This posting is
provided "AS IS" with no warranties, and confers no rights...

"dGeneral" <dGeneral@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:C963BECA-EC7B-48AE-96C7-1B9C88B874DE@xxxxxxxxxxxxxxxx
I have the same problem with a Sprint HTC Mogul. My Dell Axim X51v with WM
5
works fine.

"goeman@xxxxxxxxx" wrote:

I'm having a real problem getting a new T-Mobile Wing running WM6 on
our corporate wireless network. Our wifi network here uses PEAP/
MSCHAPv2 against an Active Directory-based RADIUS server, which works
swimmingly for XP/Vista clients, and even WM2003/WM2005-based handheld
barcode scanners running stuff like the AEGIS wifi client. I'd like to
think that WM6 will work out of the box with this, but now I'm
wondering if I need to put another wifi client on there.

When I try to connect to the network here, the Wing just goes from
"Connecting" back to "Available" without actually connecting. On the
IAS server, I see this event in the log:

Event Type: Warning
Event Source: IAS
Event Category: None
Event ID: 2
Date: 2/28/2008
Time: 10:58:22 AM
User: N/A
Computer: (RADIUS server)
Description:
User domain\user was denied access.
Fully-Qualified-User-Name = domain.local/Users/user
NAS-IP-Address = 10.10.2.10
NAS-Identifier = WLC4400-12
Called-Station-Identifier = 00-1A-E3-D0-A1-C0
Calling-Station-Identifier = 00-18-41-1D-E8-1E
Client-Friendly-Name = WLC4400-12
Client-IP-Address = 10.10.2.10
NAS-Port-Type = Wireless - IEEE 802.11
NAS-Port = 1
Proxy-Policy-Name = Use Windows authentication for all users
Authentication-Provider = Windows
Authentication-Server = <undetermined>
Policy-Name = wireless
Authentication-Type = EAP
EAP-Type = <undetermined>
Reason-Code = 22
Reason = The client could not be authenticated because the
Extensible Authentication Protocol (EAP) Type cannot be processed by
the server.

All of that is good up until the EAP-Type, which should be EAP-
MSCHAPv2. I don't know how to force the Wing to send that type; it's
got the right domain credentials.

In the setup for the wireless connection, on the "Configure Network
Authentication" screen, I've got 802.1x checked, EAP type set to PEAP.
If I click Properties there, it lets me select personal certificates
from the local certificate store, which immediately tells me
something's wrong since we don't use personal certificates to do the
authentication - just domain usernames/passwords combined with the CA
cert, which I have imported.

I've seen other people with this problem, but no solutions yet. Has
anyone successfully gotten a WM6 install on a wifi network like mine?
Or should I be investigating 3rd party wifi clients? If so, which ones?



.

Relevant Pages

  • Re: WM6 + PEAP/MSCHAPv2
    ... When you setup the wireless conenctions make sure the last page of the setup is set to PEAP not Smart Car or Certificate ... barcode scanners running stuff like the AEGIS wifi client. ... Extensible Authentication Protocol Type cannot be processed by ...
    (microsoft.public.pocketpc.wireless)
  • Re: PEAP user authentication failed - need help
    ... How to Setup Windows, Network, VPN & Remote Access on ... I set up a domain controller (Windows Server 2008), ... DHCP, NPS, AD certificate services and created ... authentication), it NEVER asks me to enter user credentials and there ...
    (microsoft.public.windows.server.networking)
  • Re: PEAP user authentication failed - need help
    ... How to Setup Windows, Network, VPN & Remote Access on ... > my own enterprise root certificate, ... > authentication), it NEVER asks me to enter user credentials and there ... > if the certificate is shown in the field while i configured wireless ...
    (microsoft.public.windows.server.networking)
  • WM6 + PEAP/MSCHAPv2
    ... Our wifi network here uses PEAP/ ... barcode scanners running stuff like the AEGIS wifi client. ... Extensible Authentication Protocol Type cannot be processed by ...
    (microsoft.public.pocketpc.wireless)
  • RE: WM6 + PEAP/MSCHAPv2
    ... Our wifi network here uses PEAP/ ... barcode scanners running stuff like the AEGIS wifi client. ... Extensible Authentication Protocol Type cannot be processed by ...
    (microsoft.public.pocketpc.wireless)
Loading