Ruckus Wireless Setup with Windows 2008 NPS

The wireless project requires domain users (staffs) using domain joined notebooks, non-domain (workgroup) notebooks and mobile devices to be authenticated to use the wireless. I will not be going into the detailed Ruckus wireless setup and will be concentrating on the NPS setup along with the client’s configuration. The biggest challenge was authenticating the non-domain notebook/laptops. Unix/Linux OS based and mobile devices didn’t have much issue in the authentication process as these clients have the option to ignore the certificate whereas windows based OS (tested on Vista and 7) throws errors like “windows was unable to verify the identity of the server”.
Here is the Ruckus Wireless snapshot detail of the SSID “Staff” which I have used for the project. It’s using 802.1 x EAP authentication method with WPA2 encryption and AES algorithm.
The Active Director Directory Services (AD DS) and Active Directory Certificate Service (AD CS) are on two separate machines running Windows Server 2008. Network Policy Server (NPS) is installed on the same server as AD CS which is also the Root CA.
On the AD CS, we create a computer certificate following the procedure below:
Creating Certificate: Open MMC > File > Add/Remove Snap-in… > Certificates > Add > Computer account > Local computer > Finish > Expand Certificates (Local Computer) > right click Personal > All Tasks > Request New Certificates … > Next > Next > check Computer > Enroll.
This certificate will be used when building the NPS.
Setting up NPS: Open NPS from Administrative Tools. Right click on NPS (Local) and click Register server in Active Directory. Click OK on the two dialog boxes.
Click NPS (Local) and chose RADIUS server for 802.1X Wireless or Wired Connections from the drop down list and click Configure 802.1X
Select Secure Wireless Connections and give a name (“wireless” in my case). Click Next and Add a Radius Client (for my case the radius client is the IP or DNS name of the Ruckus Zone Director). Create a Shared secret manually click next and select Microsoft: Protected EAP (PEAP) and then click on the Configure. The Certificate issued must have the certificate enrolled in the steps above.

Click Next and select a user group from the AD to secure the wireless. I just used domain user group “staff” for my case. Accept the defaults and restart the NPS service.
Important Point: Window based systems will have authentication issue while connecting to the wireless. To resolve this issue, the Certificate Authority (CA) certificate that certifies the Computer certificate used in NPS must be imported to the Trusted Root Certification Authorities of the client Notebook.
The settings automatically captured by the client notebook for the authenticated wireless are shown below:
I leave the distribution of the certificate to the end users (non-domain) as it can be carried out is multiple ways.
That’s the way of process of installing the CA in the Trusted Root Certification Authorities
Note: I’ll not be responsible for any issues coming out of this implementation but I’ll be happy to help out with any questions.

Comments

  1. Hi this is pretty awesome !
    Just having some issues with authenticating the Zone Director with the Radius server. After putting in the settings for setting up the AAA server in Zone Director when I test it only gives me invalid password.
    any ideas ?
    Thanks in advance.

    ReplyDelete

Post a Comment

Popular posts from this blog

Wireless DPSK setup with Ruckus Zone Director

Access denied for user 'bacula'@'localhost' (using password: YES)

Operation could not be completed (error 0x00000709)