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.
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?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
This issue has been driving me crazy for months, but I think I've just found a fix in a different channel. If you haven't already, please try:
https://community.tp-link.com/en/business/forum/topic/592190?replyId=1164912
(Disable 6GHz in the wireless network and lock the security to WPA2/AES)
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
@Fae 6 years later still the same issue. was there ever a solution
- Copy Link
- Report Inappropriate Content
@esctec I have tried all the suggestions of this thread and not had any positive result.
- Copy Link
- Report Inappropriate Content
@TuataraTec It woiuld be interesting to hear your issues. I've had a problem-free time since I figured out the WPA3 issue.
- Copy Link
- Report Inappropriate Content
@gabrielhopkins Likewise, I have found success turning off WPA3 and Protected Management Frames.
- Copy Link
- Report Inappropriate Content
I've been experiencing this issue on and off for years.
Note I've never used Omada and the EAP245 is CAT6 wired to R605. The 605 reports no corresponding errors, while the EAP245 log shows 8 pages of this error.
Probably not related this but may be coincident with another recurring problem: 5Ghz network refuses connection yet 2.4 Ghz wifi works fine. Y
The 2.4 and 5 Ghz networks have different SSID.
Has anyone turned off DHCP and used static addresses (using whatever method) and continued to see this error?
I ask because this feels like a DHCP server error. I just tried isolating my LAN and enabling mDNS, thinking there might be a Bonjour issue. Has anyone else tried this?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 1
Views: 44924
Replies: 57
Voters 0
No one has voted for it yet.