Deco M9 plus wifi connections dropping continuously
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi,
I bought Deco M9 plus 3-pack one month ago and been generally happy with the equipment and its performace, except one thing: the M9 mesh system wifi connections are dropping continuously.
I have following quite standard setup:
- ISP modem (bridged) --eth--> Main DecoM9 (DHCP, NAT) --eth--> Gigabit switch --eth--> 2nd/3rd DecoM9 (both connected directly to the switch).
- The system is set into Router mode and satellite decos connected to main one via ethernet backhaul. I am having both 2,4+5GHz frequencies selected.
- Wired devices: One PC, Mac and TV connected via ethernet to gigabit switch, PS4 to 3rd Deco's ethernet port
- Wireless devices at home: 2 ipads, 4 iphones, AppleTV, two notebooks, etc.
My problem is that the wifi connection drops often unexpectedly and then all wireless devices lose simultaneously internet connection. These devices can be in different places at home. However, all wired devices are having flawless internet connection at the same time so this cannot be an ISP issue. While the wifi connection goes down, the wifi signal strength shows still 100% in the devices. All Decos have green light when this happens, and the wifi/internet connection returns itself back after some time, typically after a couple of minutes. This can happen multiple times per day, sometimes 2-3 times per hour and while everyone at home in the evenings, it can be very frustrating.
The firmware is latest and I have tried changing AP locations, re-booted them, unplugged/plugged from power, etc. but the issue does not go away. I am a bit helpless at the moment. Is there any idea what could be causing this and how to cure to this erratic behavior?
Thank you very much, appreciate any advice on this.
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
I am having the same problem. Each Deco M9 is updated to the latest firmware release. 1.5.5 Build 202110519 Rel 35582.
Getting random shut downs on ethernet backhaul units and main unit as well. Light blinks red. Its like it is rebooting or reconnecting. This is pretty painful, esp, when in meetings.
What can be done about this other than getting a different brand? I use all the TPLink KASA products as well and love them. But this is not good to keep losing connections.
Thank you.
JC
- Copy Link
- Report Inappropriate Content
I was using a different server than my main cable router (gateway) to provide DHCP and DNS.
All my other computers worked fine.
once I switched back to having the gateway provide DHCP and DNS the M9's got better.
I've left it like that to avoid the issue.
- Copy Link
- Report Inappropriate Content
Hi,
May I know who is your internet service provider?
‘Getting random shutdowns on Ethernet backhaul units and main unit as well, did you mean the Deco would suddenly power off, then power back on, or just the LED lights would sometimes become blinking red from solid green?
How long have you had the Deco kit and how often did this issue repeat?
When the Deco starts blinking red, would reboot temporarily fix this issue?
Thank you very much.
- Copy Link
- Report Inappropriate Content
Hi @TP-Link and all,
I have the same problem.
2 Deco M9 PLUS, v2.8 - just bought them a week ago.
Bandwith always excellent - downstream 300+MB, upstream 15+MB.
Had occasional issues, but today it completely escalated.
I was in video calls (MS Teams, Zoom) and the connection kept getting interrupted. Mostly I was freezing for the others, while I could here their audio. Always took 5-10 secs to recover. My kids were home schooling (snow day) and had the same problems (google meet). This went on for hours. It was a desaster.
Pinging the router I see these substantial outliers that others also report. See below.
Any advice? I read about some seeing results after deactivating the mesh functionality while this would pretty much jeopardize the investment into the mesh.
Has anyone had the same issue and resolved it without limiting the functionality? Need to be returned?
Thanks - Roy
64 bytes from 192.168.68.1: icmp_seq=4560 ttl=64 time=7.985 ms
64 bytes from 192.168.68.1: icmp_seq=4561 ttl=64 time=5.252 ms
64 bytes from 192.168.68.1: icmp_seq=4562 ttl=64 time=5.434 ms
64 bytes from 192.168.68.1: icmp_seq=4563 ttl=64 time=12.835 ms
64 bytes from 192.168.68.1: icmp_seq=4564 ttl=64 time=8.405 ms
64 bytes from 192.168.68.1: icmp_seq=4565 ttl=64 time=4.564 ms
64 bytes from 192.168.68.1: icmp_seq=4566 ttl=64 time=5.806 ms
64 bytes from 192.168.68.1: icmp_seq=4567 ttl=64 time=13.332 ms
64 bytes from 192.168.68.1: icmp_seq=4568 ttl=64 time=8.576 ms
64 bytes from 192.168.68.1: icmp_seq=4569 ttl=64 time=4.300 ms
64 bytes from 192.168.68.1: icmp_seq=4570 ttl=64 time=6.334 ms
64 bytes from 192.168.68.1: icmp_seq=4571 ttl=64 time=4.450 ms
64 bytes from 192.168.68.1: icmp_seq=4572 ttl=64 time=4.292 ms
64 bytes from 192.168.68.1: icmp_seq=4573 ttl=64 time=3.616 ms
64 bytes from 192.168.68.1: icmp_seq=4574 ttl=64 time=5.499 ms
64 bytes from 192.168.68.1: icmp_seq=4575 ttl=64 time=5.636 ms
64 bytes from 192.168.68.1: icmp_seq=4576 ttl=64 time=6.640 ms
64 bytes from 192.168.68.1: icmp_seq=4577 ttl=64 time=8.193 ms
64 bytes from 192.168.68.1: icmp_seq=4578 ttl=64 time=108.646 ms
64 bytes from 192.168.68.1: icmp_seq=4579 ttl=64 time=31.565 ms
64 bytes from 192.168.68.1: icmp_seq=4580 ttl=64 time=79.519 ms
64 bytes from 192.168.68.1: icmp_seq=4581 ttl=64 time=75.545 ms
64 bytes from 192.168.68.1: icmp_seq=4582 ttl=64 time=4.480 ms
64 bytes from 192.168.68.1: icmp_seq=4583 ttl=64 time=42.318 ms
64 bytes from 192.168.68.1: icmp_seq=4584 ttl=64 time=14.011 ms
64 bytes from 192.168.68.1: icmp_seq=4585 ttl=64 time=6.045 ms
64 bytes from 192.168.68.1: icmp_seq=4586 ttl=64 time=5.674 ms
64 bytes from 192.168.68.1: icmp_seq=4587 ttl=64 time=13.088 ms
64 bytes from 192.168.68.1: icmp_seq=4588 ttl=64 time=3.828 ms
64 bytes from 192.168.68.1: icmp_seq=4589 ttl=64 time=13.922 ms
64 bytes from 192.168.68.1: icmp_seq=4590 ttl=64 time=15.728 ms
64 bytes from 192.168.68.1: icmp_seq=4591 ttl=64 time=5.950 ms
64 bytes from 192.168.68.1: icmp_seq=4592 ttl=64 time=12.561 ms
64 bytes from 192.168.68.1: icmp_seq=4593 ttl=64 time=16.453 ms
64 bytes from 192.168.68.1: icmp_seq=4594 ttl=64 time=14.353 ms
64 bytes from 192.168.68.1: icmp_seq=4595 ttl=64 time=15.826 ms
64 bytes from 192.168.68.1: icmp_seq=4596 ttl=64 time=6.091 ms
64 bytes from 192.168.68.1: icmp_seq=4597 ttl=64 time=13.403 ms
64 bytes from 192.168.68.1: icmp_seq=4598 ttl=64 time=13.677 ms
64 bytes from 192.168.68.1: icmp_seq=4599 ttl=64 time=13.661 ms
64 bytes from 192.168.68.1: icmp_seq=4600 ttl=64 time=5.553 ms
64 bytes from 192.168.68.1: icmp_seq=4601 ttl=64 time=4.403 ms
64 bytes from 192.168.68.1: icmp_seq=4602 ttl=64 time=5.626 ms
64 bytes from 192.168.68.1: icmp_seq=4603 ttl=64 time=5.593 ms
64 bytes from 192.168.68.1: icmp_seq=4604 ttl=64 time=6.271 ms
64 bytes from 192.168.68.1: icmp_seq=4605 ttl=64 time=14.002 ms
64 bytes from 192.168.68.1: icmp_seq=4606 ttl=64 time=8.558 ms
64 bytes from 192.168.68.1: icmp_seq=4607 ttl=64 time=15.696 ms
64 bytes from 192.168.68.1: icmp_seq=4608 ttl=64 time=3.321 ms
64 bytes from 192.168.68.1: icmp_seq=4609 ttl=64 time=5.977 ms
64 bytes from 192.168.68.1: icmp_seq=4610 ttl=64 time=4.689 ms
64 bytes from 192.168.68.1: icmp_seq=4611 ttl=64 time=4.345 ms
64 bytes from 192.168.68.1: icmp_seq=4612 ttl=64 time=4.131 ms
64 bytes from 192.168.68.1: icmp_seq=4613 ttl=64 time=4.758 ms
64 bytes from 192.168.68.1: icmp_seq=4614 ttl=64 time=4.272 ms
64 bytes from 192.168.68.1: icmp_seq=4615 ttl=64 time=8.635 ms
64 bytes from 192.168.68.1: icmp_seq=4616 ttl=64 time=32.992 ms
64 bytes from 192.168.68.1: icmp_seq=4617 ttl=64 time=4.309 ms
64 bytes from 192.168.68.1: icmp_seq=4618 ttl=64 time=44.763 ms
64 bytes from 192.168.68.1: icmp_seq=4619 ttl=64 time=6.627 ms
64 bytes from 192.168.68.1: icmp_seq=4620 ttl=64 time=13.421 ms
64 bytes from 192.168.68.1: icmp_seq=4621 ttl=64 time=4.325 ms
64 bytes from 192.168.68.1: icmp_seq=4622 ttl=64 time=14.775 ms
64 bytes from 192.168.68.1: icmp_seq=4623 ttl=64 time=13.875 ms
64 bytes from 192.168.68.1: icmp_seq=4624 ttl=64 time=14.136 ms
64 bytes from 192.168.68.1: icmp_seq=4625 ttl=64 time=16.553 ms
64 bytes from 192.168.68.1: icmp_seq=4626 ttl=64 time=13.267 ms
64 bytes from 192.168.68.1: icmp_seq=4627 ttl=64 time=9.483 ms
- Copy Link
- Report Inappropriate Content
I wonder how after so many complaints about this product, don't sit back and fix it or replace the routers of the affected users. The router is completely useless, stop selling it.
- Copy Link
- Report Inappropriate Content
Information
Helpful: 13
Views: 30272
Replies: 45
Voters 8
