WPA Authentication times out/failed every now and then but after some time succesfull

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
123...

WPA Authentication times out/failed every now and then but after some time succesfull

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
WPA Authentication times out/failed every now and then but after some time succesfull
WPA Authentication times out/failed every now and then but after some time succesfull
2020-08-07 15:30:46 - last edited 2023-11-23 09:22:34
Model: EAP245  
Hardware Version: V3
Firmware Version: 2.20.0 Build 20200423 Rel. 36779

I experience a for me weird connection lost and reconnect problem.

 

I've Omada AP contoller (V4.1.5) that's controlling 3 AP's: 2 EAP245 and 1 outdoor eap225.

The use of the Omage AP control program makes sure the definitions of the AP's are identical as they're applied to all AP's.

So SSID's and WPA2 secure string is all the same for all AP's.

 

As of the installation begin of this year but now as of the juni release more ofter the WiFi is instable.

While connected and working client it suddenly looses its connection and attempts to reconnect.

Reconnect takes some time.

In the logs i see "WPA Authentication times out/failed"

But after a minute or so the client does get connected.

All type clients experience this problems: android, windows, chromebook.

The AP's provide 2,4 and 5 GHz using the same SSID.

I've reset the most setting back to standard.

I did orginally use Fast Roaming and band steering. Did uncheck them for now, that improved it a bit  but not enough.

When checked these I noticed the client kept conencted but lost internet connectivity.

On android changing "using mac address to random mac" speeds up the relinking.

 

What could cause this behaviour and what to change here in the conguration ?

 

The DHCP is delivered using an Edgemax router. The DHCP logs do not reveal much here. Looks like the AP handshake somewhere fails within the alloted time.

DHCP is very busy, but seems the message does not pass:

17:53:31 Information    xxx    daemon    dhcpd3    DHCPOFFER on x.x.x.101 to MyMACaddr via switch0
17:53:31 Information    xxx    daemon    dhcpd3    DHCPDISCOVER from MyMACaddr  via switch0
17:53:29 ... same message over and over again...
17:53:29
17:53:28
17:53:28
17:53:28
17:53:28
17:53:23
17:53:23
17:53:21
17:53:21
17:53:20
17:53:20
17:53:19
17:53:19
17:53:18
17:53:18
17:53:16
17:53:16
17:53:15
17:53:15

 

The omada logs show less details:

7-8-2020    17:53:44    Information    MyOmadacontroller    local1    1    2020-08-07T15:53:45.934Z - Omada Controller - - [client:MyMACaddr] is connected to [ap:D8-0D-17-94-07-34] with SSID MySSID on channel 1.
7-8-2020    17:53:44    Information    MyOmadacontroller    local1    1    2020-08-07T15:53:45.900Z - Omada Controller - - [client:MyMACaddr] is disconnected from SSID MySSID on [ap:1C-3B-F3-A1-62-DE] (10s connected, 1.73KB).
7-8-2020    17:53:41    Information    MyOmadacontroller    local1    1    2020-08-07T15:53:42.721Z - Omada Controller - - [client:MyMACaddr] is connected to [ap:1C-3B-F3-A1-62-DE] with SSID MySSID on channel 11.
7-8-2020    17:53:41    Information    MyOmadacontroller    local1    1    2020-08-07T15:53:42.694Z - Omada Controller - - [client:MyMACaddr] is disconnected from SSID MySSID on [ap:D8-0D-17-94-07-34] (7s connected, 2.74KB).
7-8-2020    17:53:14    Information    MyOmadacontroller    local1    1    2020-08-07T15:53:15.782Z - Omada Controller - - [client:MyMACaddr] is connected to [ap:D8-0D-17-94-07-34] with SSID MySSID on channel 108.
7-8-2020    17:53:14    Information    MyOmadacontroller    local1    1    2020-08-07T15:53:15.756Z - Omada Controller - - [client:MyMACaddr] is disconnected from SSID MySSIDon on [ap:D8-0D-17-94-07-34] (17s connected, 7.78KB).

 

I'm reading on the subject "WPA Authentication times out/failed" discussions on changing Beacon interval of DTIM period. Do not feel comfortable with this yet to start experiments.

In the mean time the customers on the site are getting upset on this instable WiFi.

 

Any thoughts?

  1      
  1      
#1
Options
1 Accepted Solution
Re:WPA Authentication times out/failed every now and then but after some time succesfull-Solution
2021-01-13 07:48:47 - last edited 2023-11-23 09:22:34

Hi all,

 

The WPA Authentication Timeout/Failed may be prompted on the Omada SDN Controller in two situations:

 

  • There is a packet loss in the wireless associated handshake process, which causes the handshake process to timeout
  • The wireless password is input wrong when connecting to the SSID on the wireless client.

 

So please ensure your wireless clients can get a strong signal strength from the SSID, and the wireless password is input correctly first.

Besides, please make sure your Omada Controller and EAPs are all up to date. (The Omada Controller v4.2.8 has been released)

 

If the signal strength is strong enough and the password is input correctly, please try providing the info below for further analysis.

 

1. What else phenomenon do you notice in your network except for WPA Authentication times out/failed on the Omada Controller?


2. What devices(brand/model/OS) are you using in your network? What devices are suffering from the problem?

    For example, iPhone12 with iOS 14.3, Samsung SM-A217F with Android 10.

 

3. Does the problem only occur on certain devices or only exist on a specific band (2.4GHz or 5GHz), specific SSID?

 

4. Does the issue occur regularly and how often would it happen for your case? Can you reproduce the problem steadily?

 

5. How do you get the devices to be connected finally? Would a reboot help for your case?

 

6. Do you configure any advanced features like Band Steering, Airtime Fairness, Fast Roaming, Mesh or 802.11 Rate Control?

    Note: they are disabled on the Omada Controller by default unless you enable it manually.

 

7. Are you using Omada Software Controller or OC200? What's the version of the Omada Controller?

    For example, Omada Controller v4.2.8 - Windows.

 

8. How many EAPs do you have in total, what's the detailed firmware version of your EAPs?

    For example, only one EAP245 V3 whose firmware is 5.0.0 Build 20200918.

 

TP-Link team will try the best to figure out the problem, your feedback is much appreciated!

If you have any further clues, please feel free to leave your comments. Thank you for your cooperation and support!

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
Recommended Solution
  0  
  0  
#24
Options
57 Reply
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-08-08 05:10:33

@sjon 

 

The Omada SDN contoller V4.1.5 has been changed a lot in my view.

I would reset everything and test with default settings to avoid some misconfigurations, if I were you.

  0  
  0  
#2
Options
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-08-15 10:32:36

@Yannie 

I experience the same issues and I dont think its a configuration problem as I have reset all settings to default. In addition I have replaced an EAP245 with a EAP225 which is working without connection problems.

 

Especially EAP245 in combination with "slow" devices like ESP8266, ESP32 or wireless printers are effected. Usually they dont get an IP as they can not finish the authentication process. In my opinion there is a bug in the firmware or the controler software.

 

 

 

  0  
  0  
#3
Options
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-08-19 02:49:23

@SiKo 

 

Hello,

 

SiKo wrote

Especially EAP245 in combination with "slow" devices like ESP8266, ESP32 or wireless printers are effected. Usually they dont get an IP as they can not finish the authentication process. In my opinion there is a bug in the firmware or the controler software.

 

Did you check for firmware update on the EAP245? I found a new firmware released for EAP245 V3 in EU version.

https://www.tp-link.com/en/support/download/eap245/#Firmware

 

Note sure what causes the problem, perhaps TP-Link support in your region could help you.

  0  
  0  
#4
Options
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-09-24 15:24:17

I'm facing similar issues with my two EAP 225. I've fast roaming and band steering turned on.

 

One of the things I find interesting is that they show you these errors in a summary in the home page, but there is no drill down: I want to learn when this happened, on which device, connecting to which AP, etc... but can't.. I've enabled additional alerts at the log section, to see if that helps a bit.

 

 

  6  
  6  
#5
Options
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-11-10 16:31:07

On my site the error appears also if I activate 5 GHz. The clients connect get an IP and then disconnect. I discovered the error the first time with my old tablet then with a new MacBook und a new Windows laptop.

 

My configuration: 3x EAP225(EU) v3.0 with OC200.

  0  
  0  
#6
Options
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-11-12 07:15:22 - last edited 2020-11-12 07:15:40

Dear @MacPo,

 

On my site the error appears also if I activate 5 GHz. The clients connect get an IP and then disconnect. I discovered the error the first time with my old tablet then with a new MacBook und a new Windows laptop.

 

Are you able to connect your devices properly on 2.4GHz? Do you mean that you get the error only after you enable 5GHz?

 

From UG, WPA Authentication Timeout/Failure indicates an issue due to authentication timeout or wrong password.

Please ensure your devices can get a good signal strength from the EAP's 2.4G/5G SSID before connecting.

 

If you configured any advanced settings such as Airtime Fairness, Band Steering, Fast Roaming, try disable them and see if it works.

 

My configuration: 3x EAP225(EU) v3.0 with OC200.

 

Where do you install the 3 EAP225, on the ceiling or on the wall? Are they all hardwired to your main router for the Internet connection?

 

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#7
Options
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-12-04 07:53:51

@Fae Hello,

 

Same problem for me.

I have 3 EAP245 on OC200 and I have Authentication Timeout.

 

All "special" features are disabled.

 

Last firmware installed.

 

Another solution?

 

Thks!

 

David

 

 

  0  
  0  
#8
Options
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-12-04 09:37:28

Dear @Cotchet,

 

Same problem for me.

I have 3 EAP245 on OC200 and I have Authentication Timeout.

All "special" features are disabled.

Last firmware installed.

Another solution?

 

Try rebooting the EAP245s and check if it helps for the case.

>> Omada EAP Firmware Trial Available Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
  0  
#9
Options
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-12-07 17:13:28

@sjon 

In German it is called "Reboot tut gut" which means reboot is good. The reboot of all AP and Omada solved the probelm for me.

  0  
  0  
#10
Options
Re:WPA Authentication times out/failed every now and then but after some time succesfull
2020-12-22 15:08:22 - last edited 2021-01-13 18:53:33

@sjon I'm getting the same problem.  Network is unreliable.

 

Chromecasts constantly dropping. If a phone device is casting to chromecasts and the phone is moved so it connects to a different AP, the casting stops.

Reboot of APs will temporarily solve, but the problem returns same day or a few days later.

 

All devices have excellent connection signal.

 

Constant reports of WPA association failures, today is 132.

 

I have no idea where these WPA fails are coming from. Clicking on the failures doesn't result in a page showing the detail of clients.

This setup used to be so reliable but now it's a mess.

  1  
  1  
#11
Options