Solved

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

Posted on 2011-09-22
7
1,001 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
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
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.

 
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

Connect further...control easier

With the ATEN CE624, you can now enjoy a high-quality visual experience powered by HDBaseT technology and the convenience of a single Cat6 cable to transmit uncompressed video with zero latency and multi-streaming for dual-view applications where remote access is required.

Question has a verified solution.

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

Synchronize a new Active Directory domain with an existing Office 365 tenant
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 steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
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 to another domain controller. Log onto the new domain controller with a user account t…

791 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