Domain not available error on wireless clients
Posted on 2009-05-05
At the start of the year, we changed our wireless security over to a more secure network (802.1x with PEAP and MSCHAPv2) authenticating to a Microsoft IAS Server (Windows Server 2003 Standard). I followed the very detailed solution guide from Microsoft (Securing Wireless LANs with PEAP and Passwords). It all works flawlessly until about 2 weeks later when a few laptops prompt a student with the message domain not available . Logging onto the laptop shows that it hasnt connected to wireless. Attempting to reconnect fails and the only way to get it going again is to do a gpupdate /force while plugged into the LAN and then do a restart. After that all is well again, until another 2 weeks or so. This is not just for one laptop, its totally random with any of our laptops. Usually it would be 5 or so that happen at the same time.
We are using Colubris/Procruve wireless solution, but dont think that is causing the problem as I had exactly the same problem at a previous workplace.
I have googled and havent really come up with much apart from a small forum with 2 or so other people with the same problem with no solution.
Has anyone deployed 802.1x with PEAP and run into the problem we are having?
Has anyone found a solution to this problem?