Problems with Controllers and SecureW2 Windows Mobile client

Unanswered Question
May 8th, 2007


we have a wireless network with WiSM controllers. Everything is fine with laptops equipped with SecureW2 clients, but we have problems with PDA's: Odissey clients work fine, but SecureW2 for Windows Mobile don't.

We are using Freeradius (latest version) as RADIUS server. We have version of controller's software, and we are using EAP-TTLS+TKIP.

In the "aaa events" debug, we can see that de RADIUS server sends to the controller an Access-Accept, with certain override values, but we don't have "AAA Override" set in the controllers. Have you experienced similar problems? Is it possible that without the AAA override the PDA cannot connect?

Best Regards,


I have this problem too.
0 votes
  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 0 (0 ratings)
b.hsu Mon, 05/14/2007 - 12:38

If you have a shared secret with a valid special character (in this case it was an @) and you enter it at the GUI, communication with the Radius server will fail due to an "invalid Message Authenticator" which is the shared secret. As a test I changed the shared secret to alpha only and entered it from the GUI and it worked.As another test, I changed it back to the original secret on the CLI and it worked. So it seems that there is a problem with the GUI accepting special characters in the radius server shared-secret field.


This Discussion



Trending Topics - Security & Network