Home All Groups Group Topic Archive Search About

Re: PEAP Authentication in IAS

Author
2 Feb 2009 1:24 PM
Paul Bergson [MVP-DS]
This question is based for Networking not AD.

I have copied them in on this query.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.


Show quoteHide quote
"Caio" <C***@discussions.microsoft.com> wrote in message
news:02D2B215-ED24-43EB-8D92-B30986E0FB7C@microsoft.com...
> Hello,
> I'm having some troubles trying to configure my wired network to use
> 802.1X
> with Radius server.
> Here my problem: I'm using a Procurve 2650 as Radius Client, IAS as Radius
> Server and Windows XP as supplicant.
>
> If I configure CHAP authentication, selecting MD5-Challenge under
> Authentication in the network configuration of Windows XP and CHAP
> authentication under Authentication window of the Radius (IAS) policy, all
> works fine and I can login correctly in my network (I can see the log into
> the event viewer).
>
> But when I choose to use PEAP, selecting it from the drop down list under
> Authentication window of network configuration (in XP), and selecting the
> same into the radius policy, I can't correctly login, and in the event
> viewer
> I see this error:
> Reason-Code = 66.
> Reason = The user attempted to use an authentication method that is not
> enabled on the matching remote access policy
>
> This is a problem because only PEAP permit to automatically submit the
> login
> credentials (or does somebody know how to do it with CHAP?), and because
> with
> Windows Vista MD5 is totally unavailable because it's considered obsolete
> and
> unsecure.
>
> Probably I'm missing some step to enable that authentication method in the
> GPO of my domain, or something similar.
> Does somebody has a suggestion about this problem?
>
> Thank you

Author
2 Feb 2009 10:47 PM
Robert L. (MS-MVP)
It seems to me the authentication methods don't match. Or check this link.

IAS Issue CollectionsIAS related Event ID and IAS Reason Codes. Most Windows
IAS Event ID errors are related ... IAS Event ID 2 - Reason-Code = 65 ·
Event ID 2: Reason-Code = 66 ...
      www.chicagotech.net/troubleshooting/eventid2.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
Show quoteHide quote
"Paul Bergson [MVP-DS]" <pbbergs@nopspam_msn.com> wrote in message
news:ueO4UmThJHA.3904@TK2MSFTNGP02.phx.gbl...
> This question is based for Networking not AD.
>
> I have copied them in on this query.
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Caio" <C***@discussions.microsoft.com> wrote in message
> news:02D2B215-ED24-43EB-8D92-B30986E0FB7C@microsoft.com...
>> Hello,
>> I'm having some troubles trying to configure my wired network to use
>> 802.1X
>> with Radius server.
>> Here my problem: I'm using a Procurve 2650 as Radius Client, IAS as
>> Radius
>> Server and Windows XP as supplicant.
>>
>> If I configure CHAP authentication, selecting MD5-Challenge under
>> Authentication in the network configuration of Windows XP and CHAP
>> authentication under Authentication window of the Radius (IAS) policy,
>> all
>> works fine and I can login correctly in my network (I can see the log
>> into
>> the event viewer).
>>
>> But when I choose to use PEAP, selecting it from the drop down list under
>> Authentication window of network configuration (in XP), and selecting the
>> same into the radius policy, I can't correctly login, and in the event
>> viewer
>> I see this error:
>> Reason-Code = 66.
>> Reason = The user attempted to use an authentication method that is not
>> enabled on the matching remote access policy
>>
>> This is a problem because only PEAP permit to automatically submit the
>> login
>> credentials (or does somebody know how to do it with CHAP?), and because
>> with
>> Windows Vista MD5 is totally unavailable because it's considered obsolete
>> and
>> unsecure.
>>
>> Probably I'm missing some step to enable that authentication method in
>> the
>> GPO of my domain, or something similar.
>> Does somebody has a suggestion about this problem?
>>
>> Thank you
>
Author
2 Feb 2009 10:48 PM
Robert L. (MS-MVP)
Check my reply in wireless.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
Show quoteHide quote
"Paul Bergson [MVP-DS]" <pbbergs@nopspam_msn.com> wrote in message
news:ueO4UmThJHA.3904@TK2MSFTNGP02.phx.gbl...
> This question is based for Networking not AD.
>
> I have copied them in on this query.
>
> --
> Paul Bergson
> MVP - Directory Services
> MCTS, MCT, MCSE, MCSA, Security+, BS CSci
> 2008, 2003, 2000 (Early Achiever), NT4
>
> http://www.pbbergs.com
>
> Please no e-mails, any questions should be posted in the NewsGroup This
> posting is provided "AS IS" with no warranties, and confers no rights.
>
>
> "Caio" <C***@discussions.microsoft.com> wrote in message
> news:02D2B215-ED24-43EB-8D92-B30986E0FB7C@microsoft.com...
>> Hello,
>> I'm having some troubles trying to configure my wired network to use
>> 802.1X
>> with Radius server.
>> Here my problem: I'm using a Procurve 2650 as Radius Client, IAS as
>> Radius
>> Server and Windows XP as supplicant.
>>
>> If I configure CHAP authentication, selecting MD5-Challenge under
>> Authentication in the network configuration of Windows XP and CHAP
>> authentication under Authentication window of the Radius (IAS) policy,
>> all
>> works fine and I can login correctly in my network (I can see the log
>> into
>> the event viewer).
>>
>> But when I choose to use PEAP, selecting it from the drop down list under
>> Authentication window of network configuration (in XP), and selecting the
>> same into the radius policy, I can't correctly login, and in the event
>> viewer
>> I see this error:
>> Reason-Code = 66.
>> Reason = The user attempted to use an authentication method that is not
>> enabled on the matching remote access policy
>>
>> This is a problem because only PEAP permit to automatically submit the
>> login
>> credentials (or does somebody know how to do it with CHAP?), and because
>> with
>> Windows Vista MD5 is totally unavailable because it's considered obsolete
>> and
>> unsecure.
>>
>> Probably I'm missing some step to enable that authentication method in
>> the
>> GPO of my domain, or something similar.
>> Does somebody has a suggestion about this problem?
>>
>> Thank you
>
Author
3 Feb 2009 4:43 PM
Caio
thank you to everyone for the replies,
I discovered that my was a Procurve problem, related to the old firmware
version.

Now, with the latest version, PEAP authentication works like a charm. :-)
Author
4 Feb 2009 12:09 AM
Robert L. (MS-MVP)
Thank you for the update.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
Show quoteHide quote
"Caio" <C***@discussions.microsoft.com> wrote in message
news:AAA81CC4-45D6-48F2-A186-9010DFB8AAEE@microsoft.com...
> thank you to everyone for the replies,
> I discovered that my was a Procurve problem, related to the old firmware
> version.
>
> Now, with the latest version, PEAP authentication works like a charm. :-)
>