rolamento wrote

My Archer C1200 V2, still reboots randomly after the update to firmware C1200(EU)_V2_180118.
Major problem that is making me crazy is that the OpenVPN Server included never auto starts on boot. I have always to tick off and tick on the VPN in order for it to start.

Anyone solved this issue yet?

Thank you.

Same Problem at this date 01/09/2019 :

2.0.2 Build 20180118 rel.38979 (EU)

Archer C1200 v2.0

Using 2,4Ghz for : Google Home, Yeeligh 
Using 5Ghz for : Hp printer, Macbooks, iphones

I see every SSID but i cannot be connected to it... no internet connection but sometimes after a while or a reboot it works...

Please help! I do not want to restart my router every times...

r2hubert wrote

I've seen this issue reported by a couple of people already and some say upgrading firmware solves it.
The issue is that after a while the route still works, you can ping the web interface but don't even load loading page. Also the Wifi is visible but doesn't give any network access.
Rebooting the router solves the issue for a little while.

It seems like v2 of the C1200 is the only version that did not get a 2017 update, it is still on 2016-11-30.
Any chance to get a firmware update to fix this issue? it's plaguing my network and it is really annoying.


Solution

TP-Admin wrote

Hi All,

Following initial research and investigation, our Engineering Team is confident that they've determined one of the key origins of the issue. From what we have gathered so far, the issue appears to be related to some recent releases of Android OS and Google Apps. This issue stems from these devices' "Cast" feature, which sends MDNS multicast discovery packets in order to keep a live connection with Google products such as Google Home. These packets normally sent in a 20-second interval. However, we have discovered that the devices will sometimes broadcast a large amount of these packets at a very high speed in a short amount of time. This occurs when the device is awakened from the "sleep mode", and could exceed more than 100,000 packets in a short amount of time. The longer your device is in "sleep", the larger this packet burst will be. This issue may eventually cause some of router’s primary features to shut down – including wireless connectivity.
 

so how to prevent it from doing so, also i dont have any google products i only have an android phone !!

@r2hubert 

Iam having the same issue, but it didnt apear until i recently purchased a new windows laptop (cant see how is that related or may be not) also it kept happening very frequently while downloading.

But i tested a few steps with a 100 Gigabyte file (downloaded online) alongside some simultaneous downloads including torrenting and found :

- Shutting down the 5Ghz antena solved the problem (atleast no hanging during the first 30 Gigs of download).

- Then alternatively enabling & reducing the Transmit Power of the 5Ghz antena to "Low" propably fixed the issue ( at least for the rest of the download).

If any one can also test and confirm so we can pin point the problem or to make sure it wasnt a good luck during the test i made.

The reboot issue is still there, c1200 v3 just recently got a firmware update, which looks like it fixes the stability that has been plaguing all c1200 models.
 

Can we please get an update also for c1200 v2 

Dead TP-Link, 

Ignoring this issue doesn't make it go away. Last firmware update for V2 was over 2 years ago, and the problem still persists. I'm starting to lose faith in TP-Link products because of this. 

I noticed something while trying to get my router to stay up. I had some smart light switches connected, specifically Tuya operated ones. Every time I tried to pair a new one, the router would crash. So I thought fair enough, the problem is the switches I have. I then took my old ASUS router and connected all the smart switches to that, and then connected the ASUS to my TP-Link. Now, ASUS does not crash with these switches, so the problem is clearly the Archer router. Now I have to rely on my old ASUS to run some of my Wifi stuff just because TP-Link is incompetent in fixing their stuff. I'm running out of reasons to not throw the Archer in the bin and buying a new router from ASUS.