RADIUS: getting timeouts while authenticating

[snoerre]

Hi,

 

I have some strange problems with our (different) wifi controllers. Our users use 802.1x (MS-CHAPv2/PEAP) to connect to our wlan system. The problem: The popup for authentication reappears several times, before they finally get in. First I though, hey, 802.1x, they didn´t setup the connection properly. You all know, 802.1x on e.g. Windows XP can be a little annoying... Some of my users don´t have problems at all, others have to retype their password and user 3,4,5 times to get in.

 

But my controllers tell me that they can´t authenticate the users, because the RADIUS server doesn´t answer or that there´s a timeout. So, my RADIUS server is a Windows Server 2008 R2 being on a vmware system. Well, the system itself is actually a little bored. The cpus are far away from being overloaded. It is really strange, I can´t find the reason.

And what is really annoying, I can´t find useful logging data on the Windows Server 2008 R2. The setup ist really simple. No NAP so far. Just authenticate and voila you should be connected. filter-id is given back to the controllers.

 

Perhaps someone of you knows, what´s going wrong?

Edited October 11, 2011 by snoerre

[featured_spectre]

Which wifi controllers are you using? They may be conflicting the RADIUS auth server which could be causing issues

[snoerre]

HP, Aruba, Netgear, Enterasys

[featured_spectre]

No wonder you are having issues!!!

 

All 4 are probably fighting for control of RADIUS auth.

[snoerre]

No wonder you are having issues!!!

 

All 4 are probably fighting for control of RADIUS auth.

 

Although they share the same policy on the radius, they all have different IPs and the RADIUS should therefore distinguish all requests. Am I wrong?

[featured_spectre]

You may need to assign priorities on the RADIUS, and do it based on which has most AP's. If it is even, then do it based on most used AP's.