+ 0 Votes The trickiest part is usually the client setup robo_dev 1 year ago What version Windows? In the past when setting up stuff like this, it was a million times easier to use a third party app such as the AEGIS client, since the Windows connection sometimes does odd things. For example, are you letting Windows manage the WLAN connection or a utility that comes with the adapter.....some of those utils are very good (Cisco) and some, well, not so much (Belkin). Not to sound like a big Cisco fan, but Cisco WLAN gear lets you run it in debug mode, and even lets you debug the AP-to-Radius server communication. That can be invaluable in figuring out authentication failures. I would recommend putting an ethernet hub between the AP and radius server and firing up Wireshark on a machine...this way you can watch the authentication ( or lack of it) in real time. + 0 Votes Reponse To Answer Trini_Randy 1 year ago It's a mix of OS between Windows 7 and Windows XP SP3 as well a couple iPads for the execs. We are using a Nexxt WAP for testing but I have requested Cisco WAPs or WLAN, whichever we can get within budget expenditure. I got the setup of the NPS finally I put the NPS and CA on the same server, but because my AD is still in 2000 domain environment it is not working until we update the AD will it work, so that project has now been giving priority. As to the last recommendation, there are no direct communication between the server and any AP. the Servers are connected to switches. Thanks though for your help and I will update when we jump back onto the RADIUS project.