Security

Android device showing 'Authentication Error' when trying to connect to to WiFi - device connects to home WiFi and iPhone hotspot WiFi connection fine.

There is no Radius authentication setup.

There is no Mac Whitelisting or Blacklisting (cleared this out already just in case).

Issue seems to only be with one device, rebooted the device and AP's several times, 'forgotten' the WiFi connection on the device. 

APs are 305's and are running version 8.3.0.5, previously were running 6.x and the clients device still had the 'Authentication Error' issue when trying to connect.

Any suggestions would be greatly appreciated.

Does your WLAN SSID Profile have any specific options enabled? Some devices do not support all features advertised by a SSID. What kind of SSID is this, PSK? Is there any other working devices on the same SSID?

If you create a default SSID, does the device connect?

Thank you for your response.

The SSID is WPA-2 Encrtypted PSK.

I setup a new employee SSID with the default parameters and the device had the same issue.

I also setup a guest SSID with no PSK and the device could not connect.

There are two SSIDs on our network, guest and employee both have WPA-2 PSKs and have a number of working devices connected to them. 

There is one single android device which will not connect, the device connects to multiple other WAPs but not the one in our office.

Any other suggestions?!

Cheers,

Chris.

how old is the android device ? if it's old, it may be reacting badly to bandsteering - this was a problem some years ago. you can try adding the device to the clientmatch unsupported list:

from the CLI

add ap arm client-match unsupported <mac>

Good afternoon,

Thank you for your suggestion. It doesn't look like that is a valid command for our version, unless I am missing something.

add ap arm client-match unsupported xx:xx:xx:xx:xx - returns 'parse error'

And I can't seem see an alternative...

I can see from running command show ap client-match-history that the affected client is being connected then disconnected as it thinks there is a better AP..

xx:xx:xx:xx:xx:xx Normal Normal Client associated 1 2019-02-20 15:22:59
xx:xx:xx:xx:xx:xx Normal Home Band Steering 1 2019-02-20 15:23:00
xx:xx:xx:xx:xx:xx Normal Target Band Steering 0 2019-02-20 15:23:00
xx:xx:xx:xx:xx:xx Home Done Moving client to better AP 1 2019-02-20 15:23:00

The device is from 2017, a Galaxy A3.

do you have an MM or is it standalone controller for your 8.3 network?

Good morning,

If by MM you mean Mobility Master then no we do not have one of these.

We have 9 different AP's, a random one is assigned the maser role and the others are 'slaves'. We do not have a stand alone controller in our environment.

Thanks,

Chris.

ok, so you have "Instant APs" or IAPs, not controller based APs. Is client match enabled ? (webUI -> RF). If yes try disabling it. If not, if bandsteering is set to 'prefer 5ghz" then try disabling it.

If either of those fix it then you have to decide whether you want to sacrifice those features for the sake of 1 client, if those don't fix it, you may need to engage support and do a wireless capture and really dig into what the problem is.