Re: Securing Wireless LANs with PEAP and Passwords
From: James McIllece [MS] (jamesmci_at_online.microsoft.com)
Date: 08/04/04
- Next message: James McIllece [MS]: "Re: Wireless 802.11x PEAP failure IAS Cicso 1200"
- Previous message: Keith Mitchell: "Re: WinXP 802.1X Client doesn't Respond"
- Next in thread: Agent News Reader: "Re: Securing Wireless LANs with PEAP and Passwords"
- Reply: Agent News Reader: "Re: Securing Wireless LANs with PEAP and Passwords"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 04 Aug 2004 14:09:29 -0700
"Jesper Harder" <-J-esper-H-arder@gts.dk> wrote in
news:cdnsgh$lab$1@news.cybercity.dk:
> Hi Group
>
> Following the guidelines in the Microsoft paper "Securing Wireless
> LANs with PEAP and Passwords"
> I'm having problems getting things to work.
>
> My setup consists of a Lucent AP500 Access Point with 802.1x turned
> on. Server is DC, CA, IAS Windows 2003
> Clients is Windows XP SP1, IBM Think Pad
>
> I have created everything (I think) following the white paper.
>
> My problem is the clients cannot connect to the 802.1x wlan.
>
> The log shows nothing, except if the user is not allowed wireless
> access. In the Server Event viewer i get the following:
>
> Access request for user xxxxx\Administrator was discarded.
> Fully-Qualified-User-Name = xxxxxx\Administrator
> NAS-IP-Address = 172.16.16.240
> NAS-Identifier = AP500-1
> Called-Station-Identifier = 00053c041b9a
> Calling-Station-Identifier = 00601d1f7391
> Client-Friendly-Name = 172.16.16.240 HTXL
> Client-IP-Address = 172.16.16.240
> NAS-Port-Type = Wireless - IEEE 802.11
> NAS-Port = <not present>
> Proxy-Policy-Name = Use Windows authentication for all users
> Authentication-Provider = Windows
> Authentication-Server = <undetermined>
> Reason-Code = 97
> Reason = The authentication request was not processed because it
> contained
> a Remote Authentication Dial-In User Service (RADIUS) message that was
> not appropriate for the secure authentication transaction.
>
>
> On the client i can see the computer is trying to authenticate for at
> while, then fails.
>
>
> Any ideas out there ?
>
>
> Thanks!
>
> Best regards
>
> Jesper Harder
>
>
>
>
Hi Jesper --
I'm not certain what problem you're having, but you may want to review this
other whitepaper to verify your deployment -- "Enterprise Deployment of
Secure 802.11 Networks Using Microsoft Windows" at
http://www.microsoft.com/technet/prodtechnol/winxppro/deploy/ed80211.mspx
-- James McIllece, Microsoft Please do not send email directly to this alias. This is my online account name for newsgroup participation only. This posting is provided "AS IS" with no warranties, and confers no rights.
- Next message: James McIllece [MS]: "Re: Wireless 802.11x PEAP failure IAS Cicso 1200"
- Previous message: Keith Mitchell: "Re: WinXP 802.1X Client doesn't Respond"
- Next in thread: Agent News Reader: "Re: Securing Wireless LANs with PEAP and Passwords"
- Reply: Agent News Reader: "Re: Securing Wireless LANs with PEAP and Passwords"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
