Wireless Access

 View Only
last person joined: yesterday 

Access network design for branch, remote, outdoor, and campus locations with HPE Aruba Networking access points and mobility controllers.
Back to discussions
Expand all | Collapse all

PEAP with MSM765 and Windows XP SP3

This thread has been viewed 0 times

  • 1.  PEAP with MSM765 and Windows XP SP3

    Posted May 04, 2011 12:27 PM

    Hello Everyone!

    I have a pair of MSM765 wireless controllers and a bunch of MSM430 AP's I'm trying to configure. I have a couple of VSC's and I'm using the controller for authentication but not access control. Things work great when I use pre-shared keys for authentication. Users can obtain an IP address and get to things.

    When I try switching one of the VSC's to use 802.1x for authentication, I cannot associate anymore. I run wireshark on the client, and I see the client sends an "EAPOL Start" then the client receives an "EAP Request Identity" message that contains the name of the VSC. The Windows XP client seems to ignore that and starts sending DHCP Discover messages. And we just repeat this over and over again.

    I've tried a bunch of settings on the Windows XP client, but no luck. Am I missing something? Should the "EAP Request Identity" contain the name of the VSC?

    This seems like more of a Windows XP issue, I think. But any help would be appreciated. Thanks!

    -julio

     

    P.S. This thread has been moved from Communications, Wireless (Legacy ITRC forum) to MSM Series. -HP Forum Moderator



  • 2.  RE: PEAP with MSM765 and Windows XP SP3

    Posted Aug 28, 2012 09:46 PM

    Hi Julio,

     

    I have the exact same problem.

    Were you able to solve it?

     

    Thanks

     

    Regards



  • 3.  RE: PEAP with MSM765 and Windows XP SP3

    Posted Sep 07, 2012 11:26 PM
      |   view attached

    This document should help with setup and configuration of 802.1x authentication. It also has a section on enabling accounting, troubleshooting and example error conditions.