plasmahal wrote

Hi,

 

Had the Arccher Vr2100 a few eeks now and it reboots itself several times during a 24hr period.

 

Firmware up to date and cannot see and kind of schedules in the settings that would reboot it.

 

The logs do not show anything obvious.

 

Do i have a faulty device?

@plasmahal 

@360 Seems to be global problem for VR2100. There are many beta firmware version but problem remains.

You have two solution:

a) wait for fix by TP-LINK (unknown when)

b) RMA/make a complaint and return it

For me I'm using last official firmware now (1.4.0 0.9.1 v009e.0 Build 201122 Rel.72659n) - not ideal but i can work with it. Other beta firmwares were unstable for me (i had problem with abnormaly CRC errors). 

@360

@Kevin_Z might say more and better than I did.

And if not restarting, there is my problem with speed. You can check video: 

https://www.youtube.com/watch?v=rApa82ZuVDo

If i use reconnect internet 'Advanced/Network/Internet' then it will do reconnect but result is same.

But if i use manual reboot... Makes no sense to me.

david-m wrote

I was asked to try disabling the 5G WiFi as a debug step - has anyone already tried this?

I tried. Today modem did self restart (uptime 12-20 min :X). 5G disabled.

@david-m

I tried this and it stayed up for a day. The speed afterwards was awful. Dropped to 0.8-1.5 MB/s on WiFi

@NobFox If you see problem with speed then you try first start speedtest on web administration VR2100. WIFI can be affected by range, some noise etc. (but yea VR2100 TPLINK representing as modem with strong wifi :) )

Today it is horror with VR2100. 

About 5x crash today. And maybe I am starting be paranoid but the modem often crashes when I am using any voip program as Teamspeak/Discord etc. Yea, it is very weird but whenever I use something like then it  will follow modem crash.

(yea it is restarting without voip programs too, but not so often)

@NobFox 

Same - I have 5Ghz back on because Smart Connect/ OneMesh was the reason for buying the VR2100.

F.Y.I  I received my brand new RMA V2100 Unit yesterday (Still a V1). This lasted 15 Hours before the first reboot. So this re-inforces the fact that the problem is not specifically hardware issues with individual units but more a generic Hardware Design / Firmware Issue.

I have fed this back to support and will let you know if I get a response..