Solved

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

Posted on 2011-09-22
7
1,002 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
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 4
  • 3
7 Comments
 
LVL 11

Expert Comment

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

Author Comment

by:MartynLawson
ID: 36580679
Hi
It's Windows 2003 (not R2)

Thanks
0
 
LVL 11

Expert Comment

by:TheGeezer2010
ID: 36581249
And which GP setting are you using ?
0
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

 
LVL 1

Author Comment

by:MartynLawson
ID: 36581355
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
ID: 36708969
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
ID: 36898842
Correct solution.
0
 
LVL 11

Expert Comment

by:TheGeezer2010
ID: 36709645
Nice one !!
0

Featured Post

Surfing Is Meant To Be Done Outdoors

Featuring its rugged IP67 compliant exterior and delivering broad, fast, and reliable Wi-Fi coverage, the AP322 is the ideal solution for the outdoors. Manage this AP with either a Firebox as a gateway controller, or with the Wi-Fi Cloud for an expanded set of management features

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In-place Upgrading Dirsync to Azure AD Connect
This article shows the method of using the Resultant Set of Policy Tool to locate Group Policy that applies a particular setting.
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 Micro Tutorial hows how you can integrate  Mac OSX to a Windows Active Directory Domain. Apple has made it easy to allow users to bind their macs to a windows domain with relative ease. The following video show how to bind OSX Mavericks to …

749 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