Hi,
I am going through Microsoft's 'Step-by-Step Guide for Setting Up Secure Wireless Access in a Test Lab' now, and the solution does not seem very simple.
To setup 802.1x you need:
- Active Directory (usually, but you could use standalone IAS)
- IAS service (MS's RADIUS server)
- Access policy on IAS setup for 802.1x
- Certificate server, with computer certificate issued to the IAS server
- AP and wireless client that supports WPA Enterprise.
- Patches on the client to give operating system support (e.g post sp2 patch to support WPA2).
Then, when you configure the client, and connect it seems kind of clunky with popup's for entering credentials and others to verify certificates.
Do third party solutions make it simpler, or just outsource the Certificate Services part?
Slashdot Mirror
You basically get twice as much off peak traffic, as on peak.
This would basically encourage the users themselves to schedule their p2p to be kind to others (as well as themselves).
Anyone else tried this approach.
P.S I won't mention the ISP or the plans, people outside NZ wouldn't understand how you can get so little for so much $$.
Hi, I am going through Microsoft's 'Step-by-Step Guide for Setting Up Secure Wireless Access in a Test Lab' now, and the solution does not seem very simple. To setup 802.1x you need: - Active Directory (usually, but you could use standalone IAS) - IAS service (MS's RADIUS server) - Access policy on IAS setup for 802.1x - Certificate server, with computer certificate issued to the IAS server - AP and wireless client that supports WPA Enterprise. - Patches on the client to give operating system support (e.g post sp2 patch to support WPA2). Then, when you configure the client, and connect it seems kind of clunky with popup's for entering credentials and others to verify certificates. Do third party solutions make it simpler, or just outsource the Certificate Services part?