11-14-2016 08:34 AM
We have a couple of AP running 220.127.116.11-18.104.22.168_50009 and they have configured MAC authentication with internal server authentication ( blacklist disable, uppercase support disable). The issue is when a new machine tried to authenticate I got a radius authentication failure on the logs, this happend with win7 or some win10 machines, is there a specific setting on the machines that might need in order to connect to the aruba wireless?
We have WPA2-Personal on the Aruba AP and currently using around 28 users. All of them are registered on the Security settings MAC address with Uppercase and delimite character - , the profile is employee we only have 1 SSID,.
11-14-2016 08:37 AM
11-14-2016 08:41 AM
The new machines are added to the database, eventhough the are in the DB , I am still getting radius authentication failure (win7 or win10) . If I disable the mac authentication and use WPA2-Personal with no MAC authentication the machines are able to use the wireless network. We have disabled antiviruses , firewalls on the machines.
11-14-2016 12:14 PM
I found something odd on the configuration:
user A4-34-D9-A9-18-61 35c3b2ba6bbbc788590840c0be938a5cf4838edc51529147ec
user A0-8D-16-88-CB-E1 15d3c8356485bd5e4356fa9b4dba2ce21e97b6ee276c4452 radius
the lenght of the password is different for those 2, in the case of the long lenght the MAC authenticatio is working while the other it is not.