Improve company productivity with a Business Account.Sign Up

x
?
Solved

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

Posted on 2011-09-22
7
Medium Priority
?
1,015 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
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

Improved Protection from Phishing Attacks

WatchGuard DNSWatch reduces malware infections by detecting and blocking malicious DNS requests, improving your ability to protect employees from phishing attacks. Learn more about our newest service included in Total Security Suite today!

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

It’s time for spooky stories and consuming way too much sugar, including the many treats we’ve whipped for you in the world of tech. Check it out!
You have missed a phone call. The number looks like it belongs to the bunch of numbers which your company uses. How to find out who has just called you?
This video shows how to use Hyena, from SystemTools Software, to update 100 user accounts from an external text file. View in 1080p for best video quality.
Sometimes it takes a new vantage point, apart from our everyday security practices, to truly see our Active Directory (AD) vulnerabilities. We get used to implementing the same techniques and checking the same areas for a breach. This pattern can re…

606 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