WMM causes other devices to not connect

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

WMM causes other devices to not connect

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
31 Reply
Re:WMM causes other devices to not connect
2021-08-31 18:15:10

@Kevin_Z 

Thank you for your response.

 

I'm specifically having issues with a MacMini M1 on macOS 11.5.2 and sometimes with a HP Pavillion AMD Ryzen 5 running Linux Mint 12 and kernel 5.14.0-051400rc3-generic. The HP's WiFi adapter identifies as "Intel Corporation Wi-Fi 6 AX200 (rev 1a)". Apple's WiFi identifies as "AirPort Extreme", Firmware: wl0: Jul  7 2021 00:48:27 version 18.50.40.10.7.8.121 FWID 01-f5ad2691

 

Having the issues regardless of distance to the router/repeater. Pings from the Mac are especially choppy:

64 bytes from 192.168.1.150: icmp_seq=0 ttl=64 time=119.115 ms

64 bytes from 192.168.1.150: icmp_seq=1 ttl=64 time=39.175 ms

64 bytes from 192.168.1.150: icmp_seq=2 ttl=64 time=47.252 ms

64 bytes from 192.168.1.150: icmp_seq=3 ttl=64 time=98.471 ms

64 bytes from 192.168.1.150: icmp_seq=4 ttl=64 time=88.705 ms

64 bytes from 192.168.1.150: icmp_seq=5 ttl=64 time=112.129 ms

64 bytes from 192.168.1.150: icmp_seq=6 ttl=64 time=85.960 ms

64 bytes from 192.168.1.150: icmp_seq=7 ttl=64 time=49.029 ms

64 bytes from 192.168.1.150: icmp_seq=8 ttl=64 time=100.927 ms

64 bytes from 192.168.1.150: icmp_seq=9 ttl=64 time=89.077 ms

64 bytes from 192.168.1.150: icmp_seq=10 ttl=64 time=102.592 ms

64 bytes from 192.168.1.150: icmp_seq=11 ttl=64 time=18.993 ms

64 bytes from 192.168.1.150: icmp_seq=12 ttl=64 time=144.129 ms

^C

--- sonny ping statistics ---

14 packets transmitted, 13 packets received, 7.1% packet loss

round-trip min/avg/max/stddev = 18.993/84.273/144.129/34.352 ms

 

the other way around - right now - is fine:

64 bytes from tucker (192.168.1.146): icmp_seq=1 ttl=64 time=6.85 ms

64 bytes from tucker (192.168.1.146): icmp_seq=2 ttl=64 time=6.68 ms

64 bytes from tucker (192.168.1.146): icmp_seq=3 ttl=64 time=5.86 ms

64 bytes from tucker (192.168.1.146): icmp_seq=4 ttl=64 time=7.50 ms

64 bytes from tucker (192.168.1.146): icmp_seq=5 ttl=64 time=5.87 ms

64 bytes from tucker (192.168.1.146): icmp_seq=6 ttl=64 time=4.09 ms

64 bytes from tucker (192.168.1.146): icmp_seq=7 ttl=64 time=4.97 ms

^C

--- tucker ping statistics ---

7 packets transmitted, 7 received, 0% packet loss, time 6010ms

rtt min/avg/max/mdev = 4.089/5.973/7.504/1.082 ms

 

 

 

  0  
  0  
#23
Options
Re:WMM causes other devices to not connect
2021-09-01 01:32:19

@w321 

 

Hi, the tech team was made aware of your issue. They will likely reach out to you via email to continue troubleshooting your issue.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#24
Options
Re:WMM causes other devices to not connect
2021-10-01 23:06:21
Try turning QOS off first. New UI, standard is off.
  0  
  0  
#27
Options
Re:WMM causes other devices to not connect
2022-03-16 00:55:28 - last edited 2022-03-16 00:56:55

@Kevin_Z 

 

I am also having this issue with WMM disabled, preventing all the android phones on my network from connecting while laptops and desktops are just fine. Once re-enabled all devices can connect. 

 

I'm hoping tp-link can reach out to help me out with this. Otherwise instruction on the proper way to reach out to them would be appreciated. Love this device and hope to continue using it.

 

Here is my device and firmware release:

 

Firmware Version:

1.2.5 Build 20220117 Rel. 51845(5553)

 

Hardware Version:

Archer AX1500 v1.20

 

It's running as an Access Point. 

  0  
  0  
#28
Options
Re:WMM causes other devices to not connect
2022-03-18 03:11:30

lostboykev wrote

@Kevin_Z 

 

I am also having this issue with WMM disabled, preventing all the android phones on my network from connecting while laptops and desktops are just fine. Once re-enabled all devices can connect. 

 

I'm hoping tp-link can reach out to help me out with this. Otherwise instruction on the proper way to reach out to them would be appreciated. Love this device and hope to continue using it.

 

Here is my device and firmware release:

 

Firmware Version:

1.2.5 Build 20220117 Rel. 51845(5553)

 

Hardware Version:

Archer AX1500 v1.20

 

It's running as an Access Point. 

 

@lostboykev 

 

May I know why do you want to disable WMM on the router? That is recommended to be on.

 

BTW, what are the brands and OS versions of the Android phones?

 

 

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#29
Options
Re:WMM causes other devices to not connect
2022-05-26 20:11:08

Hi  @Kevin_Z ,

I have same issue with AX1800. My problem is, that

- with WMM off, my Android devices won't connect (Win10 laptop is OK)

- with WMM on, my IoT devices won't connect

 

Obviously, I wont both my android devices and IoT devices stay connected at the same time. 

Is there any solution? Thanks.

  0  
  0  
#30
Options
Re:WMM causes other devices to not connect
2022-05-27 03:20:33

Hi @Kefear

 

 

I would like to know the brands and OS versions of the Android devices as well as the IoT devices, as we mentioned earlier the WMM should not affect the connection between the client devices and the router.

 

Can you confirm again if WMM is the only change when they connect and not connect? Are they all connecting to the 2.4G or 5G network?

 

Are all of them can connect to other wireless networks properly?

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#31
Options
Re:WMM causes other devices to not connect
2022-06-08 17:31:21

  @Kevin_Z I first noticed with Android 10 on a Motorola Z4. The problem continued with Android 11 on a Pixel 4a-5G, and continues with Android 12 on a Pixel 5a. For some this was an issue that caused a return, i.e. devices not connecting with in on, but others won't connect with it off. My last non TP-Link router did not prevent devices from connecting with WMM on or off so it is definitely a TP-Link issue. An issue I'm surprised isn't fixed.

 

Yes, I am running the latest firmware.

AX6000 v2

 

 

 

  0  
  0  
#32
Options
Re:WMM causes other devices to not connect
2022-06-15 06:31:36

Dugguh wrote

  @Kevin_Z I first noticed with Android 10 on a Motorola Z4. The problem continued with Android 11 on a Pixel 4a-5G, and continues with Android 12 on a Pixel 5a. For some this was an issue that caused a return, i.e. devices not connecting with in on, but others won't connect with it off. My last non TP-Link router did not prevent devices from connecting with WMM on or off so it is definitely a TP-Link issue. An issue I'm surprised isn't fixed.

 

Yes, I am running the latest firmware.

AX6000 v2

 

 

 

 

@Dugguh 

 

Thank you for posting on the TP-Link Community. 

 

For further clarity on the issue, please enable WMM on the AX6000 first, then monitor the connectivity and let us know which device cannot connect to the network, does it fail to connect to 2.4G or 5G, what are the wireless security settings on the AX6000, etc. It's suggested to change the wireless security on the AX6000 to WPA2-PSK AES, then reboot the router and reconnect to the Wi-Fi on the device.

Nice to Meet You in Our TP-Link Community. Check Out the Latest Posts: Connect TP-Link Archer BE550 to Germany's DS-Lite (Dual Stack Lite) Internet via WAN Archer GE550 - BE9300 Tri-Band Wi-Fi 7 Gaming Router Archer BE800 New Firmware Added Support for EasyMesh in AP Mode, DoH&DoT, and 3-Band MLO Connection Archer AX90 New Firmware Added Support for EasyMesh and Ethernet Backhaul If you found a post or response helpful, please click Helpful (arrow pointing upward icon). If you are the author of a topic, remember to mark a helpful reply as the "Recommended Solution" (star icon) so that others can benefit from it.
  0  
  0  
#33
Options
Re:WMM causes other devices to not connect
2022-06-24 15:19:30

Same issue here. Got an AX1500 yesterday and noticed right after setting up that all my devices connected wiressly to the router were facing a weird behavior where the internet connection would become slow or intermittent for no apparent reason, no disconnections, just slow or inconsistent internet connectivity. The issue SEEMS to be particularly prevalent right after connecting the client to the router. 

Today I stopped to look further into this and took 4 from my devices to do a few tests. Here's where I'm at:

 

Network setup is: 

ISP modem connected to my router over LAN port (Modem) to WAN port (Router). Firewalls disabled both on modem and router, no QOS, port-forwarding, or anything else that might prevent or delay any specific connections. Changing LAN ports on modem doesn't seem to improve or decrease consistency in any noticeable way. Contracted carrier bandwitdth is 500mbs. Router operation mode set-up as Wireless Router Mode (not Access Point). Wi-Fi 2.4ghz and 5ghz combined on single network using the built-in Smart Connect feature, no fiddling with channels, frequencies or anyting else. Every client device (wired or not) within the same sub-net (192.168.1.*). The only device fixed over an IP address is the PC connected over cable, everything else (Wi-Fi) is dealt with by DHCP with no MAC affinity set up for any device.

 

Devices used during my tests (all within 6 feet, no walls, from the router), all drivers and OS packs are up-to-date:

1. Win10 PC - Connected to the router over cable on LAN ports 1 throught 4 during the tests. No discerneable difference in behavior, connection fast and consistent, ping response <1ms.

2. Win10 Notebook - Connected over Wi-Fi 5ghz, getting constant ping response times in the range of 200-400ms, and eventual timed-out responses (less than 1%).

3. Motorola Android Phone - Connected over Wi-Fi 5ghz, getting constant ping response times in the range of 200-400ms, and eventual timed-out responses (less than 1%).

4. Apple Ipad 9 - Connected over Wi-Fi 5ghz, getting the same constant ping response times in the range of 200-400ms, but every ping attempt times out when device is idle after a minute or two.

 

Troubleshooting attempted:

At first I thought this behavior on the Ipad was being caused by the TWT feature. However, to my surprise, it is turned off by default on the router. I have no clue why the Ipad specifically is getting dropped off when idle (AFAIK it doesn't have any of the wifi6 smart battery-saving features). When not idle, it takes a minute to get the internet back online, I was suspecting the DHCP was renewing the lease to a different IP address, but no, it stays the same.

Since changing ports doesn't seem to be helping much overall, and no firewall or QOS is setup either on the modem or router, I disabled the WMM feature and strangely enough every wireless device was kicked out of the network, every single one. The PC stays connected to both the internet and the router, and my Win10 notebook displays a message "failing to authenticate" to the network. After reverting the change on the WMM, all devices are allowed back in. 

 

Honestly I'm out of ideas at this point. I don't understand what might be the cause for such high response times and inconsistent connection behaviors from a brand-new router, configured pretty much by the factory standards. WMM specialy shouldn't be preventing any devices from connecting as far as I'm concerned.

 

Any help is appreciated, the router is pretty much unusable at this state.

  1  
  1  
#35
Options