Domain not available error on wireless clients
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?
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?
ASKER
* We have only two client configs on the IAS server so this is not an issue.
* We dont have more than two remote RADIUS server groups
* We are not using IP address ranges
* We dont have more than two remote RADIUS server groups
* We are not using IP address ranges
The first limitation isn't related to the number of client configs on the RADIUS server, but the actual number of clients that can connect to it at one time.
ASKER
That number of clients does not affect us as only one client from each of two controllers makes a connection. We have had over 250 wireless connections happening without any problems so I can be pretty sure the number of clients is not a problem.
Through other research we have found that PEAP may be the problem and EAP-TLS is recommended so we are now trying that out.
Through other research we have found that PEAP may be the problem and EAP-TLS is recommended so we are now trying that out.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
-- You can configure no more than 50 RADIUS clients (NAS's)
-- You can configure no more than two Remote RADIUS server groups
-- You can't configure RADIUS clients by IP address range
If you have hit the 50 RADIUS Clients, that may be what is causing your issue. Windows 2003 Enterprise Edition does not have the above limitations.