Windows

Ultimate wireless security guide: Microsoft IAS RADIUS for wireless authentication

Enterprise wireless LAN security is a persistent concern for every system administrator and CIO. This article, part of the TechRepublic ultimate guide to enterprise wireless LAN security, describes how to configure Microsoft's IAS RADIUS server, provided free with Windows Server 20003, for wireless authentication.

The complete TechRepublic Ultimate Wireless Security Guide is available as a download in PDF form.

Windows Server 2003 comes bundled with a very capable RADIUS (also known as AAA) server that's extremely stable, secure, and robust. When you search on Internet security databases for Microsoft IAS vulnerabilities, you won't find any. The IAS service just runs for years without the need to patch IAS. If your Windows Server 2003 box is hardened to only accept IAS requests with host-based firewall restrictions on all other ports and you install no other services on a Windows 2003 box, you can literally keep an IAS RADIUS server up for years of zero downtime or reboots.

IAS competitors

One of IAS' biggest competitors in the Enterprise market is Cisco ACS which people often assume they must use if they're using Cisco networking equipment which simply isn't true. Your Cisco network equipment works perfectly fine so long as you avoid proprietary, less-secure harder-to-deploy protocols, like LEAP or EAP-FAST.

Furthermore, the stability of ACS is questionable and there is an endless patch cycle for it since it has been plagued with security vulnerabilities and bugs. I've spent my share of time troubleshooting ACS and many hours on tech support. I have had a lot of hands-on experience with Cisco ACS. The latest version of Cisco ACS 4.x currently has two unpatched security vulnerabilities one of which is critical. Version 3.x and 2.x also have their share of critical vulnerabilities some of which are unpatched as of December 10, 2006.

Cisco ACS also lacks the ability to act as a relay RADIUS server which limits its ability to serve in a more robust multi-tier RADIUS environment. You need that ability to link to multiple Active Directories or other user directories that are not tied to each other. ACS also costs around $8000 per copy whereas Microsoft IAS comes with Windows Server 2003. Two redundant RADIUS servers would add up pretty quickly. Cisco ACS also comes on a dedicated appliance but that's even harder to use in my experience since you don't even get a Windows console graphical interface to work with.

Funk software (acquired by Juniper) has a pretty good solution with Steel-belted RADIUS at around $4000 per copy but that is still a significant cost especially when you need two RADIUS servers for redundancy. Funk is a great solution for companies which don't run a Windows Active Directory environment because IAS is tightly wound in to Microsoft Active Directory and doesn't support non-Microsoft databases.

Linux users have FreeRADIUS available to them. FreeRADIUS has had critical flaws (0.x and 1.x) in the past but they're all patched now unlike Cisco. FreeRADIUS still isn't as clean as the Funk or Microsoft RADIUS solutions but it's completely free if you're rolling your own Linux distribution or you don't need enterprise Linux support. If you're talking about SuSE or Red Hat and you want enterprise support, then the annual support contracts is double the cost of a perpetual Windows Server 2003 license. It all depends on usage model and some people will prefer Linux and some will prefer Microsoft.

Install IAS

Windows Server 2003 doesn't come with any extra services installed by default for security reasons so you'll need to manually install IAS. It's fairly simple if you have the Windows Server 2003 install CD. To install IAS, simply open "Add remove programs" from your control panel and select "Add remove windows components". You will see the following window (Figure OO) so you'll need to scroll down to "Network Services". You don't want to just check it because you don't want all Network Services installed, just highlight it and hit the "Details" button.

Figure OO

Networking services

Once you get to the screen shown in Figure PP, scroll down and just check off "Internet Authentication Service" IAS for short.

Figure PP

Internet Authentication

Once you've installed IAS, you'll be able to launch IAS from your Administrative Tools either from the control panel or from the start menu. You'll see the following interface. (Figure QQ)

Figure QQ

Service

Set logging policies

The first thing we'll do is look at and set the logging policies (Figure RR). Right click on "Internet Authentication Service (Local)" and click Properties.

Figure RR

IAS Properties

You will now see the screen in Figure SS. If you check off the two checkmarks here, you will force IAS to log successful and reject authentication requests to the Windows Event Viewer. If you're intending to use text or SQL based logging, you don't need to check these unless you want the logs showing up in both places.

Figure SS

Local Properties

If you click on the "Ports" tab, you'll see the screen shown in Listing TT. These are the default RADIUS ports and you should generally leave them alone for standardized RADIUS conventions. Microsoft IAS will actually listen on two sets of ports. The lower number ports are the more traditional port numbers, Microsoft applications prefer the higher number ports. You should generally leave this setting alone as is.

Listing TT

Ports

This next part lets you set the standalone text and SQL logging capability of Microsoft IAS. You right click on "Local File" under "Remote Access Logging" page and hit "Properties". (Figure UU)

Figure UU

Remote Access Logging

The first "settings" tab lets you set what events you want to log. (Figure VV)

Figure VV

Local file properties

The "Log File" tab lets you set the file format and the log size limits. (Figure WW)

Figure WW

Log file

We won't go in to SQL logging in this article because it gets rather complex to set up a SQL database. You have to manually create the accounts and tables in SQL in order for this to work. Furthermore, IAS under Windows Server 2003 insists on stopping the RADIUS service if logging doesn't work so if the SQL server doesn't respond, all of your RADIUS servers stop working. Unfortunately, Microsoft doesn't give you any way to override this "fail-shut" behavior because they claim customers want it this way because it's more secure but every customer I've talked to wants a choice on this behavior.

There is no security risk because the Authentication and Authorization component of Microsoft IAS is working perfectly fine, it's merely unable to make a record of the transaction. I've spoken with Microsoft and they're telling me they will correct this with Windows Server 2007 (or whatever it's going to be called when it's released next year). Hopefully they'll automate the SQL database creation process with a script too.

Add RADIUS clients

A RADIUS "client" is not what you would typically think of as a "client" as in a user. A RADIUS client is something like a wireless access point, a router, a switch, a firewall, or a VPN concentrator. Any device that provides network access that needs to delegate AAA (Access, Authorization, and Accounting) to a RADIUS server is considered a RADIUS client. For the purpose of this tutorial, we'll set up a single access point as a client.

To start, we'll right click on "RADIUS Clients" and select "New RADIUS Client" as shown in Figure XX.

Figure XX

Radius Client

You then get the screen shown in Figure YY where we give the device its name and set the IP address of the access device which in this case is an access point. Be aware that if you're talking about a router or firewall that has multiple IP addresses because it has multiple interfaces, you must configure the IP address that is closes to the RADIUS server. This is because the RADIUS request is seen as coming from the closest interface on a multi-homed access device and if you configure the wrong IP, it will not be able to communicate with the RADIUS server.

Figure YY

New RADIUS client name and IP

Then we set the RADIUS type and RADIUS secret. The RADIUS type is almost always set to "RADIUS Standard". Cisco devices are the exception and you must select "Cisco" for the "Client-Vendor" field if you want your Cisco devices to work. There are exceptions like Cisco wireless switches because the switches were acquired from Airespace in 2005.

Airespace wireless switches use "RADIUS Standard" like everyone else in the industry. The "shared secret" is the secret shared between the RADIUS server and the access device (Figure ZZ). Try to make the secret 10 characters or more comprised of random numbers and letters. Avoid spaces and special characters since that might have incompatibilities in some devices and software and you'll have a rough time troubleshooting.

Figure ZZ

Setting the shared secret

Click "Finish" to complete. You'll need to repeat this for all of your access devices.

Add remote access policies

Now we need to create a remote access policy to authenticate and authorize the user trying to access our access devices. To do this, right click on "Remote Access Policies" and click "New Remote Access Policy". (Figure AAA)

Figure AAA

New Remote Access Policy

Click "Next" to move to the next screen (Figure BBB).

Figure BBB

Policy Wizard

Give your policy a name and use the wizard. Hit "Next". (Figure CCC)

Figure CCC

Policy Name

Choose "Wireless" and hit "Next". (Figure DDD)

Figure DDD

Wireless

Here you'll need to grant access to your users and computers. Hit "Add". (Figure EEE)

Figure EEE

Group Access

Here you'll need to adjust the location to your domain. Hit "Locations". (Figure FFF)

Figure FFF

Select Groups

Choose the domain you're trying to authenticate to and hit "Ok". Note that the IAS server must be joined to the domain you're authenticating to or a trusted domain. (Figure GGG)

Figure GGG

Select Location

Type "Domain Users" and "Domain Computers and separate them with a semicolon. (Figure HHH) Then click on "Check Names" to force it to underline and validate your entries. You may of course restrict access to a smaller group of users and computers since the following option allows all domain users and all domain computers to connect to your wireless LAN. Hit "Ok".

Figure HHH

Enter domain

Note that "Domain Computers" is used to authenticate your computer for "machine authentication" which connects your wireless PC before the user even logs in. This is a very useful and unique benefit of the Windows Wireless Client since it emulates the full wired experience for wireless users.

If "machine authentication" isn't implemented, group policies and login scripts won't fire off. Furthermore, only cached users can login to the wireless computer, because users who have never signed on to that PC can't authenticate with the domain. For this reason alone is enough for me to always recommend using the Windows Wireless client for Windows users not to mention the auto-deployment capability.

Now you see the screen shown in Figure III with a summary of the user and computer groups you're allowing access. Note that this is an OR operator between these two group names. Either one true registers a success. Hit "Next".

Figure III

Group access defined

Choose "Protected EAP (PEAP)" authentication. Then hit "Configure". (Figure JJJ)

Figure JJJ

Authentication

Before you get to this page, you must either have a valid Machine Certificate from a Certificate Authority or you have already self-signed one yourself. Leave the rest of the settings like you see in Figure KKK and click OK.

Figure KKK

PEAP Properties

Finalize the remaining dialog box and you're finished making a new wireless authentication profile. Now we'll move on to fine tuning the configuration.

Tweak remote access policies

Once you complete the previous steps, you'll see a new Remote Access Policy called whatever name you gave it. The two default policies you see in Figure LLL the one we created are just there as samples and are disabled by default. We'll right click on it and hit "Properties".

Figure LLL

Remote Access Properties

You'll notice there are two "Policy conditions" shown in Figure MMM. Note that there is an AND operator operating between the two conditions. That means both conditions must be true or else the policy spits out a rejection and it moves on to the next "Remote Access Policy". The first policy forces "Wi-Fi Policy" to only permit users coming in from 802.11 connections. The second policy is the permissible user or computer groups we set earlier. Click on "Edit Profile" to continue.

Figure MMM

WiFi Policy Properties

The "Dial-in Constraints" tab lets you set the dial-in and session limit restrictions (Figure NNN). It also lets you restrict the times people are allowed to log in.

Figure NNN

Dial-in Profile

The "Encryption" tab is important for security (Figure OOO). You must uncheck the three insecure checkmarks to enforce maximum strength encryption.

Figure OOO

Encryption

The "Advanced" tab (Figure PPP) is something we won't go in to now, but note that this is a very powerful tab for advanced features. With special RADIUS attributes configured on this page, you can do things like tell your Cisco VPN concentrator what user group a user belongs to so that the concentrator will set VLAN and firewall policies on that user matching their group rights. You can also do things like set VLANs or group association for an Aruba wireless switch which has a built-in firewall. We'll leave the details for a future advanced RADIUS configuration article.

Figure PPP

Advanced tab

Under the "Authentication" tab, you can tweak the EAP methods (Figure QQQ). For wireless LAN PEAP authentication, you actually leave all the checkmarks alone. These settings are for more traditional RADIUS applications like a modem dialup service provider that proxies to your RADIUS server. Let's click on the "EAP Methods" button to see what it has.

Figure QQQ

Authentication

Here you can edit the PEAP configuration. (Figure RRR) We already set these settings during the initial policy wizard. Click "OK".

Figure RRR

EAP Providers

You'll need to click OK one more time to get out of the Dial-in profile window.

This final section in the IAS interface is something we won't do in this article. (Figure SSS) I just wanted to give you a preview of what it does. The "Connection Request Processing" section lets you set advanced RADIUS relaying features. You have granular control of what kind of RADIUS requests you want to relay off to a different RADIUS server and which RADIUS requests you want to handle in the local "Remote Access Policy" engine.

You can even configure groups of RADIUS servers that you want to forward to. This allows IAS to participate in a multi-tier RADIUS environment. For example, if you have a user that isn't in your domain belonging to a business partner's network that needs guest access to your environment, you can forward to the RADIUS request to your business partner for them to process. There are even Universities that honor each other's students and staff by allowing a student to securely log in to any campus participating in the network.

Figure SSS

Connection Request

Backup and restore IAS policy

Finally, after all this work we want to be able to backup our RADIUS configuration and maybe even restore it on to a redundant RADIUS server. Microsoft gives you a simple command line tool for exporting and importing the RADIUS configuration.

To perform the backup operation, simply run the following command.

netsh aaaa show config c:\IAS.txt

Note that you can use any name for the file. You can use that file locally if you ever screw up the IAS configuration and you want to rapidly recover or if you want to copy the IAS setting to another IAS RADIUS server. To restore the IAS settings from the text file you created, simply run the following command assuming the correct path and file name.

netsh exec c:\IAS.txt

This makes it easy to rapidly deploy multiple redundant IAS RADIUS servers and it also gives you the peace of mind to rapidly repair an IAS server.


119 comments
MajBarny
MajBarny

Hi I have followed these steps and setup Radius on server and WiFi AP, but unable to connect wix xp just says "Validating ID' win 7 just gives error. Have checked log. please find log can you please assist. Fully-Qualified-User-Name = rockwell.local/Rockwell User Groups/Mail Group 4/NC Ops/Inet Group 4/Control 2/Kevin van Rensburg NAS-IP-Address = 192.168.1.122 NAS-Identifier = 0024a56f130d Called-Station-Identifier = 0024a56f130d Calling-Station-Identifier = 88532ed39636 Client-Friendly-Name = WF_BW_BOARDROOM Client-IP-Address = 192.168.1.122 NAS-Port-Type = Wireless - IEEE 802.11 NAS-Port = 51 Proxy-Policy-Name = Use Windows authentication for all users Authentication-Provider = Windows Authentication-Server = Policy-Name = Rockwell WiFi Authentication-Type = PEAP EAP-Type = Reason-Code = 16 Reason = Authentication was not successful because an unknown user name or incorrect password was used. For more information, see Help and Support Center at Please assist

ken.diekemper
ken.diekemper

Thanks so much for explaining all the different EAP protocols.

sheldonpittman
sheldonpittman

I am having trouble finding this PDF. Maybe not familar enough with how your site works but any help would be great. Thanks

sureshvkumar
sureshvkumar

Hi I am a visual person, anyone have a network diagram of this setup? I am trying to put the IAS on the DC to have a minimal setup for my lab. Anyone throw some idea, appreciated. Thank you

marc.laflamme
marc.laflamme

I've tried searching for the Complete TechRepublic Ultimate Wireless Security Guide PDF that's listed as available at the top of the article but can't seem to locate it. Is this only available for paid subscriptions?

robo_dev
robo_dev

SBR gives you a lot more authentication options, and it's much simpler to configure and support. In terms of simplicity, a Cisco ACS appliance or a Juniper SBR appliance is much much easier to support and maintain than a Windows server setup with ICS or SBR. The 'best' solution depends on what WLAN hardware you are using, what authentication types you need, and even what clients you are using. If ALL your WLAN clients are Windows PCs, then IAS would work fine. But if you have a whole mix of different devices and client OSs, IAS does not play well with everybody, and if your requirement is, for example, to authenticate against a Sun LDAP server versus Active Directory, or bring in RSA ClearTrust for authentication, you need a solution that's more extensible, such as SBR or ACS.

shaungun
shaungun

just wondering if its possible to have wireless authed by active directory, without the need for certificates. i want people to be able to connect just by selecting the wireless network, and enterting there AD credentials.

computer
computer

Yeah, I'm late to this party (ok, really late but I just found this page) but I was wondering, can the server be set up for both wireless and wired Ethernet connections? in the Access Method page I get a "one or the other" feeling but I'd like to set things up for both the wired and wireless connections. SO, do I need one server for wireless and another for Ethernet/Wired? Thanks, Joe B

OzRK
OzRK

This is a great article and helped me setup the system. I do however have one question for anyone still listening.... Can IAS on server 2003 do both machine and user authentication in this setup? I have IAS set up with Domain users and Domain COmputer in the policy but users on my network can get in with any device as long as they use their AD credentials... I want to be able to limit users to only coming invia work laptops. Any Suggestions ??

pellja
pellja

This article was awesome! Exactly what I needed to go through and get setup for about 300 laptops. Wireless and Radius are new for my company. Now my question is how do you use the Windows Wireless utility to authenticate to the Radius server? What I have are Dell laptops that have a Dell Wireless utility that allow me the option to select "Use Windows username and password" and "Include Windows domain" as well as Authenticate prior to Windows domain logon" and when I go to login using a domain account, it pops up saying it's authenticating and getting an ip address using the Dell utility. When I turn off this Dell utility and try to use the Windows Wireless utility, it won't connect at all! My Radius server is setup exactly as this article describes. The only thing that you probably need to know is that I have a Cisco access points controlled by a Cisco 5508 WLAN Controller. Like I said it all works great with the Dell Wireless utility so I know all settings are right. I just don't see how to get this to work with the Windows utility. Also, if you have suggestions for this, I need for it to authenticate before login so it can load network drives during the login. Thanks!!!

milindbableshwar
milindbableshwar

After following the above steps, how do i configure the RADIUS clients, having a really hard time getting support over the net, I have an Edimax 6574n AP, please help me out!!!

naveen.a
naveen.a

how to configure wireless authentication 2008 server

jengels
jengels

for me. I have tested this and even spoke with Microsoft and they can't figure this out. Any help would be greatly appreciated. Thanks in advance for your assistance. :)

stant0s
stant0s

...or can it function without doing this? I'm curious as there was no mention of this in the tutorial.

Sratostat
Sratostat

Which EAP should I use to authenticate wireless users without using a certificate? I've got a lot of various devices in my wireless network (a university campus), so I need a universal and relatively secure way of authorization using the Cisco WLC with LWAPP access points, IAS and AD. Thanks.

niemeyerstein
niemeyerstein

Interesting and comprehensive, but not too much wireless, eh?

padayaw
padayaw

is this possible im using dlink wifi router dir 615 model?

Thierrypenning
Thierrypenning

Hi, if this authentication is based on authorized domain computers criteria, then why are local users denied on such an authorized computer? is this because there is no GPO applied to the local user? and is there also a possibility for using computer authentication in wired networks? thanks in advance

joekoerambala55
joekoerambala55

Hi, I have a problem when running the computer startup scripts. If i enable "verify servercertificate" in the wireless profile then my startup scripts won't run. If i uncheck this checkbox there is no problem. The strange thing is that it only happens with computer authentication, with user authentication i can use this option. Anyone a solution I use a self signed certificate.

baskarguha
baskarguha

This is quite helpful, thanks. One question: Does Win2003 IAS or Win2007 equivalent allow relaying of just the accounting records. The idea is to just do the accounting on a remote server without requiring that server to be part of the authentication. The proxy feature seems like all or nothing.

colin.laurie
colin.laurie

I must have missed a step or screwed up. At step KKK i dont see an option to select the Self Signed cert i created in the other guide. I have imported that cert in to the Trusted Root certs on the IAS server. Can you advise please? Thanks.

Mortain
Mortain

Hi. Thanks for a good tutorial, but It Is not working for me. There are some problem authcenthing users. In event Viewer the IAS comes with this error message: Domain/User/Username Access denied. Errorcode 260, some problems with the Certificate, after manual installed the certificate I get an 262 error. "This Supplied message is incomplete. The signature was not verified" Some good explantions to what I could do? I'm curently using Win2k3 32bit Microsoft IAS Server Linksys/Cisco SBS, WAP4400N Edit: Got It to work, when manualy installed the cert as a root cert on the computer. But why is it not working automatacly? have done the tutorial just as told.

erkan102
erkan102

This is very usefull article, many thanks to the author. I build this 802.1x IAS authentication infrastructure with HP Procurve 420 AP and HP Procurve 2610 switch. It is running very good for domain users but sometimes our customers coming to our factory and they want to connect to internet. This is my problem. I should allow unauthenticated users to access vlan2(only internet). Is there anyone know how to allow unauthenticated guest users? Which type of RAP policy i should build? I tried many different methods but can not solve this problem.

scott.french
scott.french

I am wondering if you can authenticate users who are not members of the domain so they may get access to the wireless network and then be able to route them only to the internet?

neftali.reyes
neftali.reyes

Outstanding article! Very clear and concised. You are doing better than Microsoft and they should be paying you royalties. Any more articles like this, swing them my way.

ericwf1
ericwf1

Great walkthru, Thanks!

Naveed A
Naveed A

I have found out on few occasions that if the user's password expires,(We have a policy of 30 day password) he is not able to login because the wireless client says user or password wrong because windows has the old credentials cached. Has anyone had this problem? or does anyone know the solution to this?

schadow1
schadow1

Is there a way using IAS to limit the number of logins a single user can make at the same time? I can easily do this with Steel Belted Radius but it is too expensive for me.

alex.valenzuela
alex.valenzuela

Is IAS capable of sending Access control lists to deny/grant access to single ports, protocols to "radius clients" as Cisco ACS is? Or in that case, we are stuck with Cisco?

jickfoo
jickfoo

We are desparate for a system that will authenticate the machine as well as the user. For a particular SSID, we want only domain authenticated machines to get access to it. We took a laptop off of our domain, removed the computer account from Domain Computers, rebooted, and were easily still able to authenticate. We tried dozens of different ways. This system doesnt provide machine auth. We're baffled as to why this is so difficult to do, we would have thought that the IT industry would have demanded this kind of authentication. We've been through multiple vendors. If anyone has the answer to this, please let us know where to look.

bboswell
bboswell

Excellent article. I got this working in under two hours. However, I have one question: is it possible to authenticate non-Windows WiFi clients this way? Thanks for the answer!

marc.laflamme
marc.laflamme

Nevermind... my next search was successful! Oops.

AnsuGisalas
AnsuGisalas

The article is several years old. You may want to check if it's obsolete in ways relevant to you.

pellja
pellja

Ok, so I found what makes this work. Under the configuration in the Windows utility for PEAP, I told it not to authenticate a certificate and then it connects fine. Now, is doing it this way insecure because I'm not checking a certificate? So my assumption is that if I would copy the certificate that I exported on my Radius server to the laptop and installed it, I could let it authenticate this certificate and it would work this way. Is this correct? I just need for this to be secure. We are already using MAC Reservation on our DHCP server so that's one form of security but we still want it to be completely secure on the wireless side as well. Thanks for any help you can give.

cplummer
cplummer

If so that may be the issue. The controller sub's in it's name as the domain machine name when sauthenticating thru Radius. I haven't figured out how to allow it to let the correct domain machine name thru, any help there would be great. :)

scotter
scotter

At the top, if you did the self-sign correctly (mmc, certs and see if it is in Personal on the Local Machine - if it is, export it again)it will be the only option in the drop-down (assuming this is the first time that server has created a cert). you then have to use a group policy to make the same cert a Trusted cert or use the MMC on the clients and import it (trusted entpr. not personal folder). The AP/Client/Radius communications can still work, even without the cert portion if you are having trouble. On the clients wireless config skip the portion where the client is required to know the certificate. sean

scotter
scotter

If you have the GPO setup correctly try running GPUPDATE /FORCE a couple times from a cmd line on the client machine. Also, for me I really didnt know if the GPO would take the cert and embed in the GPO itself or rather link to the cert where the client would then import it (still not sure how that works, but my method works fine). So I put the cert in the sysvol where everyone could get it, then edited the GPO and added the Cert from the sysvol location. Does the rest of the GPO work for the wifi settings? They just don't get the cert (i am running two policies, one for wifi, one for certs - like in the tutorial). Finally, certs are machine based, so make sure that the cert GPO is readable and applied to the domain computers.

sccrockarell
sccrockarell

Has anyone tried to deploy this solution remotely and have the users authenticate through a VPN tunnel? Everything seems to be setup correctly, but it will not work.

Homerotrix
Homerotrix

Hi, did you? I don?t have any response from Microsoft when i ask this many times to many people since 2004. And Aruba support team (wireless "RAS") dont help "radius problem is not my problem"... we have other custom ideas to solve that we can share if you want to.

georgeou
georgeou

If you're asking whether IAS works with Cisco switches to deny/grant access to individual ports, then the answer is yes. If that doesn't answer your question, please clarify your question.

hamlet505a
hamlet505a

George's article really did speed up this deployment. I can't say thanks enough. I am in a mixed environment of Windows, MACs, and Linux clients. The Windows GP was slick and easy. George might be able to provide some insight on this, I noticed that if I did not export/import the RADIUS server self-signed certificate into Windows clients either by GPO push or manual, Windows would not join the the Wireless Network. However, with MAC Leopard clients, I did not have to export/import the certificate. The MAC client received the Radius server's certificate when trying to connect and automatically installed it in the Keychain. All I had to do was go into the keychain and "Always trust" the signing authority. Soon, I will be adding Linux clients and I'll post my experience. I'd like to ask a question, can I add client certificates so that only clients that have a proper certificate can join the wireless network? I wouldn't see why not, but after my MACs joined so easily to wireless network (of course they still needed user authentication), I'd much rather allow user's with a proper certificate that the RADIUS server trusts. This way user will need proper username/password and his/her own valid certificate. thanks, scott

georgeou
georgeou

Yes you can, 802.1x and PEAP are very standardized. The only issue with non Windows or Windows not joined to a domain is that it doesn't let you do group policy configuration.

OzRK
OzRK

Hi, thanks for your reply. yes I realise the post was from 2007 but there are recent questions from 2010. Also the basis of the article is windows server 2003 and all the original setup infomration is very valid and worked for me. I do see various snippets of what looks like the same question as mine which don't seem to be answered over time so I'm thinking maybe this just doesn't work for both user Auth and machine Auth. Anyone out there know ??!!

alex.valenzuela
alex.valenzuela

I saw some documents, IAS can name the ACL's that would apply to a particular user, but you need to have those ACL's already deployed on each Cisco PIX. With Cisco ACS, the ACL's is actually configured on the Cisco ACS and it gets downloaded on whatever PIX the user is using. I have about 18 PIXes now and just mantain a set of ACL's on a central Cisco ACS.. Still have not found a replacement for that, but it would be great if I find a way for IAS to do it..

bboswell
bboswell

Hi, I'm trying to connect a Mac PowerBook running Leopard to our MS IAS RADIUS authenticated access point. However, it seems to not be working...I got asked once or twice to add a key to the keychain and make it fully accessible (which I did). However, I haven't suceessfully gotten the Mac authenticated yet. The common failure mode is that no matter what I do on the "Advanced..." tab under the System Settings->Networking pane, the system asks me for something else (like some sort of first-level authentication that apparently gets sent in the clear?). Everything works peachy with Windows domain members...

georgeou
georgeou

User info is typically shipped in the EAP success message within attributes. I've gotten Cisco ACS to authenticate off of a Microsoft IAS server. Using RADIUS attributes delivered via EAP success message, we mapped Windows Active Directory groups to the Cisco VPN concentrator appliance access control lists. The PIX and ASA have the same feature sets from the VPN concentrator so it should be the same. It worked quite well and I found documentation on Cisco's support website on which attribute to set. If you call Cisco smartnet, they'll also help you out.