The Network Administrator

Gear List

• Windows Server 2008

• IP: 10.6.231.10

• Cisco ASA Security Appliance:

  • ASA 5510
  • IP: 10.6.231.1

Cisco ASA Setup – Using the new Cisco ADSM tool

Create an IP Name object for the target

1. Under the Firewall section, expand the Objects link and select the IP Names.
2. Click the Add button at the top.
3. Enter a descriptive name, the IP address and a description of the server.
4. Name: SRV1
5. IP: 10.6.231.10
6. Description: AD Server
7. Click OK and then Apply

Create a new AAA Server Group

1. Click the Remote Access VPN section.
2. Expand AAA Setup and select AAA Server Groups.
3. Click the Add button to the right of the AAA Server Groups section.
4. Give the server group a name, like AD server, and make sure the RADIUS protocol is selected.
5. Accept the default for the other settings. And click OK

Add the RADIUS server to the Server Group.

1. Select the server group created in the step above.
2. Click the Add button to the right of Servers in the Select Group.
3. Under the Interface Name select the interface on the ASA that will have access to the RADIUS server, most likely inside.
4. Under Server Name or IP Address enter the IP Name you created for the RADIUS server above.
5. Skip to the Server Secret Key field and create a complex password. Make sure you document this as it is required when configuring the RADIUS server. Re-enter the secret in the Common Password field.
6. Leave the rest of the settings at the defaults and click Ok.

Setting Up RADIUS on Windows Server 2008

Add Network Policy Server

1. Remote into  Windows Server 2008 server and launch Server Manager.
2. Click the Roles object and then click the Add Roles link on the right.
3. Click Next on the Before You Begin page.
4. Select the Network Policy and Access Services role and click Next.
5. Under Role Service select only the Network Policy Server service and click Next.
6. Click Install.

Setup your server using the Network Policy Server (NPS)

1. After launching the NPS tool right-click on the entry NPS(Local) and click the Register Server in Active Directory.

Create a RADIUS client entry for the ASA.

1. Expand the RADIUS Clients and Servers folder.
2. Right-click on RADIUS Clients and select New RADIUS Client.
3. Create a Friendly Name for the ASA device. Maybe LocationName_ASA_FW1.
4. Enter the Server Secret Key specified on during the ASA configuration in the Shared secret and Confirm shared secret field.
5. Leave the default values for the other settings and click OK.
   
   

Create a Connection Request Policy.

1. Expand the Policies folder.
2. Right-click on the Connection Request Policies and click New.
3. Set the Policy Name to something meaningful. I used LocationNameFW because this policy is geared specifically for that RADIUS client. Leave the Type of network access server as Unspecified and click Next.
4. Under Conditions click Add. Scroll down and select the Client Friendly Name condition and click Add…
5. Specify the friendly name that you used when creating the RADIUS Client above. Click OK and Next.
6. On the next two pages leave the default settings and click Next.
7. Under the Specify a Realm Name select the Attribute option on the left. From the drop down menu next to Attribute: on the right select User-Name. Click Next again.
8. Review the settings on the next page and click Finish.

Create a Network Policy.

1. Right-click the Network Policy folder and click New.
2. Set the Policy Name to something meaningful. Leave the Type of network access server as Unspecified and click Next.
3. Under Conditions click Add.
4. Add a User Group condition to limit access to a specific AD security group. You can use a generic group like Domain Users or create a group specifically to restrict access.
5. Add a Client Friendly Name condition and again specify the Friendly Name you used for your RADIUS client.
6. Click Next. Leave Access granted selected and click Next again.
7. On the authentication methods leave the default selection and add Unencrypted authentication (PAP, SPAP).
8. Accept the default Constraints and click Next.
9. Accept the default Radius Settings and click Next. Review the settings and click Finish.

I know that with the release of Service pack 1 for Exchange you may not need the PowerShell commands for permissions, here is a great reference.

http://technet.microsoft.com/en-us/library/bb310789.aspx

http://advisors.dell.com/AdvisorWeb/Advisor.aspx?advisor=c82c3ec8-c94f-4602-9a41-c20382db1cd0&c=us&l=en&cs=555

If you are using WEP either 128bit or 64bit, you will have issues with iPhones, iPads, etc unless you enter $ before your actual WEP key. So from  favorite Apple device, enter WEP key as $1234567891 if your WEP key is 1234567891

Often time it is necessary to segment your network via different subnets and in some cases, you will need a DHCP scope for both subnets. In my case, I am creating a 2nd VLAN to be used for a public wireless network. I thought it would be nice to manage both DHCP scopes via MS DHCP.

This is the perfect situation to use a DHCP relay agent.

First you need to make sure you have your VLANS set up on your switches and trunk your up link ports all the way back to your default gateway. Next you want to be sure your switch ports are tagged for the proper VLAN ID (ie. VLAN1 for data, VLAN 2 for wireless). In my case, I am using Cisco wireless access points and I tagged the switch ports that they are connected to VLAN ID 2.

Next you need to add a 2nd DHCP scope to your MS DHCP server and add the proper scope options (Router, Name Server and DNS Servers)

The actual relay agent itself is the easy part. Enter the config mode on your router and set your encapsulation type to dot1Q, and assign a VLAN ID to each of your interfaces. The use the ip helper-address command to point to your DHCP Server. Then make sure your IP address for each interface is on the same subnet as the DHCP scopes your configured in DHCP. Below is an example of what your interfaces might look like.

Simply remove the checkbox on "Automatically detect settings" in settings on the browser.