Solved

Wireless on XP clients, PEAP setting not applying from Group Policy GPO

Posted on 2011-09-22
7
995 Views
Last Modified: 2013-12-09
Hi

I have a problem as follows.

I have set up some Cisco Aironet 1042 APs. These use RADIUS to authenticate the clients against our Active Directory using EAP.

Our Windows 7 laptops will connect and authenticate straight away with no problem.

By default when the Windows XP SP3 clients try to connect they display an error "Windows was unable to find a certificate to log you on to the network xxxxx". This can be resolved by setting the EAP type to 'PEAP' instead of 'Use smart card or other certificate'.

I have created a GPO for the XP clients to pre-configure the SSID so that the correct settings should be available, however the 'EAP Type Protected PEAP (PEAP)' setting does not get set on the client. All the other GPO settings do get set correctly.

Does anyone know why this setting is not being applied by the GPO?

Thanks in advance.
0
Comment
Question by:MartynLawson
  • 4
  • 3
7 Comments
 
LVL 11

Expert Comment

by:TheGeezer2010
Comment Utility
What is the GPO setting you are using - Windows 2008 server ?
0
 
LVL 1

Author Comment

by:MartynLawson
Comment Utility
Hi
It's Windows 2003 (not R2)

Thanks
0
 
LVL 11

Expert Comment

by:TheGeezer2010
Comment Utility
And which GP setting are you using ?
0
Free Gift Card with Acronis Backup Purchase!

Backup any data in any location: local and remote systems, physical and virtual servers, private and public clouds, Macs and PCs, tablets and mobile devices, & more! For limited time only, buy any Acronis backup products and get a FREE Amazon/Best Buy gift card worth up to $200!

 
LVL 1

Author Comment

by:MartynLawson
Comment Utility
In the Computer Configuration/Windows Settings/Security Settings/Wireless Network, I have created a GPO called 'Wifi'. In the Preferred Networks section I've added my SSID, and in the IEEE 802.1x section I've set the EAP type to 'Protected EAP (PEAP)'

Thanks
0
 
LVL 1

Accepted Solution

by:
MartynLawson earned 0 total points
Comment Utility
I have resolved this issue. You need to extend the Active Directory schema to allow 802.11 PEAP authentication, Windows 2003 domain controllers do not support this by out of the box. See the following TechNet page which explains how to do it. It takes approximately minutes.

http://technet.microsoft.com/en-us/library/bb727029.aspx
0
 
LVL 1

Author Closing Comment

by:MartynLawson
Comment Utility
Correct solution.
0
 
LVL 11

Expert Comment

by:TheGeezer2010
Comment Utility
Nice one !!
0

Featured Post

What Should I Do With This Threat Intelligence?

Are you wondering if you actually need threat intelligence? The answer is yes. We explain the basics for creating useful threat intelligence.

Join & Write a Comment

For both online and offline retail, the cross-channel business is the most recent pattern in the B2C trade space.
Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of configuring their Windows Server 2012 domain controller to synchronize its time with a trusted, external resource. Use Google, Bing, or other preferred search engine to locate trusted NTP …

763 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

7 Experts available now in Live!

Get 1:1 Help Now