Solved

Domain not available error on wireless clients

Posted on 2009-05-05
5
346 Views
Last Modified: 2013-11-12
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?
0
Comment
Question by:darem
  • 3
  • 2
5 Comments
 
LVL 3

Expert Comment

by:ISWSIMBX
ID: 24315884
How many clients do you have running against the IAS Server?  Since you are running standard edition of 2003, there are some limitations to consider:

-- 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.
0
 

Author Comment

by:darem
ID: 24320679
* 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
0
 
LVL 3

Expert Comment

by:ISWSIMBX
ID: 24326446
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.
0
 

Author Comment

by:darem
ID: 24350471
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.
0
 

Accepted Solution

by:
darem earned 0 total points
ID: 24371647
Changed the value on the machine password age to not expire until the end of the year and so far we have not had any further dropouts so we consider the case solved
0

Featured Post

PRTG Network Monitor: Intuitive Network Monitoring

Network Monitoring is essential to ensure that computer systems and network devices are running. Use PRTG to monitor LANs, servers, websites, applications and devices, bandwidth, virtual environments, remote systems, IoT, and many more. PRTG is easy to set up & use.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Using in-flight Wi-Fi when you travel? Business travelers beware! In-flight Wi-Fi networks could rip the door right off your digital privacy portal. That’s no joke either, as it might also provide a convenient entrance for bad threat actors.
In this article, I am going to show you how to simulate a multi-site Lab environment on a single Hyper-V host. I use this method successfully in my own lab to simulate three fully routed global AD Sites on a Windows 10 Hyper-V host.
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…
This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles to another domain controller. Log onto the new domain controller with a user account t…

919 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

16 Experts available now in Live!

Get 1:1 Help Now