Home

Forums

Stories

Knowledge Base

Home Network Community > All Threads > New Archer VR2100 keeps restarting every few hours

< All Threads

New Archer VR2100 keeps restarting every few hours

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

New Archer VR2100 keeps restarting every few hours

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

deKay

2020-06-28 19:02:00 - last edited 2021-01-19 06:50:59

Posts: 11

Helpful: 2

Solutions: 0

Stories: 0

Registered: 2020-06-28

New Archer VR2100 keeps restarting every few hours

2020-06-28 19:02:00 - last edited 2021-01-19 06:50:59

Model: Archer VR2800

Hardware Version: V1

Firmware Version: 1.1.0 0.9.1 v009e.0 Build 200116 Rel.60756n

I got a new Archer VR2100 (the model field doesn't have that listed so had to choose something similar) a couple of days ago and every few hours it seems to reboot. It certainly disconnects from both the internet and LAN and the wifi vanishes for a minute or so. I'm on BT Infinity.

When it reboots, the log time and date resets back to 2016-01-01 00:00:00, which makes things tricky to sort. However, here are some extracts (apology for length):

2016-01-01 00:00:20 [4] IGMP: V2 igmp router occured! Not matching ours V3.
2016-01-01 00:00:28 [5] System: DSL Training
2016-01-01 00:00:31 [5] System: DSL Link Down
2016-01-01 00:00:35 [5] System: DSL Training
2016-01-01 00:00:40 [5] System: DSL Link Down
2016-01-01 00:00:41 [5] DHCPD: REQUEST ip c0a80067 already reserved by someone
2016-01-01 00:00:41 [5] DHCPD: Send NAK
2016-01-01 00:00:41 [6] DHCPD: Recv DISCOVER from BC:E1:XX:XX:XX
2016-01-01 00:00:41 [5] DHCPD: Send OFFER with ip 192.168.0.100
2016-01-01 00:00:41 [5] System: DSL Training
2016-01-01 00:00:42 [5] System: Enable Access Control
2016-01-01 00:00:42 [5] System: Enable IPv4 SPI Firewall
2016-01-01 00:00:42 [5] System: Enable IPv6 SPI Firewall
2016-01-01 00:00:42 [6] DHCPD: Recv DISCOVER from 98:41:5C:XX:XX:XX
2016-01-01 00:00:42 [5] DHCPD: Send OFFER with ip 192.168.0.101
2016-01-01 00:00:43 [5] DHCPD: Send ACK to 192.168.0.100
2016-01-01 00:00:44 [5] DHCPD: Send ACK to 192.168.0.101
2016-01-01 00:00:44 [6] DHCPD: Recv DISCOVER from 28:BE:03:XX:XX:XX
2016-01-01 00:00:44 [5] DHCPD: Send OFFER with ip 192.168.0.102
2016-01-01 00:00:45 [5] DHCPD: Send ACK to 192.168.0.102
2016-01-01 00:00:45 [6] DHCPD: Recv DISCOVER from 00:F6:20:XX:XX:XX
2016-01-01 00:00:45 [5] DHCPD: Send OFFER with ip 192.168.0.104
2016-01-01 00:00:45 [5] System: DSL Link Down
2016-01-01 00:00:45 [5] DHCPD: Wrong Server id or request an invalid ip
2016-01-01 00:00:45 [5] DHCPD: Send NAK
2016-01-01 00:00:45 [6] DHCPD: Recv DISCOVER from 78:5D:C8:XX:XX:XX
2016-01-01 00:00:45 [5] DHCPD: Send OFFER with ip 192.168.0.105
2016-01-01 00:00:46 [5] DHCPD: Send ACK to 192.168.0.105
2016-01-01 00:00:48 [5] System: DSL Training
2016-01-01 00:00:49 [6] DHCPD: Recv DISCOVER from 00:F6:20:XX:XX:XX
2016-01-01 00:00:49 [5] DHCPD: Send OFFER with ip 192.168.0.106
2016-01-01 00:00:50 [5] DHCPD: Send ACK to 192.168.0.106
2016-01-01 00:00:56 [5] System: DSL Link Down
2016-01-01 00:00:57 [5] System: DSL Training
2016-01-01 00:01:11 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:11 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:11 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:13 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:13 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:14 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:20 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:20 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:20 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:23 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:23 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:23 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:25 [6] DHCPD: Recv INFORM from 38:C9:86:XX:XX:XX
2016-01-01 00:01:25 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:25 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:26 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:28 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:28 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:29 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:31 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:31 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:31 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:32 [5] System: DSL Link Down
2016-01-01 00:01:35 [5] System: DSL Training
2016-01-01 00:01:37 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:37 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:38 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:40 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:40 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:40 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:43 [5] System: DSL Link Down
2016-01-01 00:01:44 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:44 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:44 [5] System: DSL Training
2016-01-01 00:01:45 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:47 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:47 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:48 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:48 [5] System: DSL Link Down
2016-01-01 00:01:49 [5] DHCPD: Send ACK to 192.168.0.100
2016-01-01 00:01:52 [5] System: DSL Training
2016-01-01 00:01:54 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:54 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:54 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:01:56 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:01:56 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:01:57 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:02 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:02 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:03 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:05 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:05 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:06 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:08 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:08 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:08 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:10 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:10 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:11 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:13 [5] System: DSL Link Up us/ds 0/79999 kbps Type 64/65B PTM Annex B
2016-01-01 00:02:17 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:17 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:18 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:18 [6] PPP: sent [PADT session is 2896]
2016-01-01 00:02:18 [6] PPP: sent [PADI Host-Uniq(0x00000694)]
2016-01-01 00:02:19 [3] PPP: Unable to complete PPPoE Discovery
2016-01-01 00:02:19 [4] PPP: Connect script failed
2016-01-01 00:02:20 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:20 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:21 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:24 [6] PPP: sent [PADT session is 2896]
2016-01-01 00:02:24 [6] PPP: sent [PADI Host-Uniq(0x0000076f)]
2016-01-01 00:02:26 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:26 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:27 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:29 [6] PPP: sent [PADI Host-Uniq(0x0000076f)]
2016-01-01 00:02:29 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:29 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:30 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:32 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:32 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:33 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:35 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2016-01-01 00:02:35 [5] DHCPD: Send OFFER with ip 192.168.0.107
2016-01-01 00:02:36 [5] DHCPD: Send ACK to 192.168.0.107
2016-01-01 00:02:39 [6] PPP: sent [PADI Host-Uniq(0x0000076f)]
2016-01-01 00:02:39 [6] PPP: rcvd [PADO PeerMac(a4-7b-2c-XX-XX-XX)]
2016-01-01 00:02:39 [6] PPP: sent [PADR Host-Uniq(0x0000076f)]
2016-01-01 00:02:39 [6] PPP: rcvd [PADS SessionID(0x0c1c)]
2016-01-01 00:02:39 [5] PPP: Connected to a4:7b:2c:XX:XX:XX via interface nas8.101
2016-01-01 00:02:39 [6] PPP: Using interface ppp1
2016-01-01 00:02:39 [5] PPP: Connect: ppp1 <--> nas8.101
2016-01-01 00:02:39 [6] PPP: CHAP authentication succeeded: CHAP authentication success
2016-01-01 00:02:39 [5] PPP: CHAP authentication succeeded
2016-01-01 00:02:39 [5] PPP: peer from calling number A4:7B:2C:CD:F4:E2 authorized
2016-01-01 00:02:39 [5] PPP: local IP address 81.157.X.X
2016-01-01 00:02:39 [5] PPP: remote IP address 172.16.X.X
2016-01-01 00:02:39 [5] PPP: primary DNS address 81.139.X.X
2016-01-01 00:02:39 [5] PPP: secondary DNS address 81.139.X.X
2020-06-28 19:39:10 [6] DHCPD: Recv DISCOVER from 7C:BB:XX:XX:XX:XX
2020-06-28 19:39:10 [5] DHCPD: Send OFFER with ip 192.168.0.107
2020-06-28 19:39:11 [5] DHCPD: Send ACK to 192.168.0.107
2020-06-28 19:44:36 [6] Httpd: DNS 81.139.X.X resolve succeed for dns.msftncsi.com
2020-06-28 19:44:36 [6] Httpd: DNS 81.139.X.X resolve succeed for www.msftncsi.com
2020-06-28 19:44:36 [6] Httpd: NCSI response check succeed.
2020-06-28 19:47:49 [6] Httpd: DNS 81.139.56.100 resolve succeed for dns.msftncsi.com
2020-06-28 19:47:49 [6] Httpd: DNS 81.139.56.100 resolve succeed for www.msftncsi.com
2020-06-28 19:47:49 [6] Httpd: NCSI response check succeed.

Any ideas?

36 Reply

naz_eg

LV2

2021-01-26 05:25:02

Posts: 48

Helpful: 10

Solutions: 0

Stories: 0

Registered: 2020-11-20

Re:New Archer VR2100 keeps restarting every few hours

2021-01-26 05:25:02

@Kevin_Z

Hi again,

After 3 days and 8 hrs, CRC errors raised to 3million suddenly but the router wasn't rebooted. I could able to make a speedtest on mobile via wifi and saw that download dropped to only 0.01 Mbit. My download is 35 Mbit normally as u can see. Than i had to reset to router manually. :(

#32

The-Geek

LV2

2021-01-26 11:31:16

Posts: 21

Helpful: 7

Solutions: 0

Stories: 0

Registered: 2020-12-03

Re:New Archer VR2100 keeps restarting every few hours

2021-01-26 11:31:16

@Kevin_Z

F.Y.I

I have been running the new beta (build 06-01-2021) for about 9 days now, I have had 3 reboots during this time, however this is an improvement over the situation before the beta.

So It appears that the firmware is heading in the right direction and the router is more stable than before, however it has not completely removed the reboot issue. It is now staying up for between 2-4 days before a reboot (again happening randomly, whether the router is in use or not, i.e overnight).

So it does appear to be a firmware issue rather than a Hardware problem. I'm happy to provide any additional info and also run any newer versions of firmware to test if this helps..

Thanks

#33

Kevin_Z

2021-01-27 01:27:01

Posts: 21755

Helpful: 5137

Solutions: 2565

Stories: 21

Registered: 2018-12-24

Re:New Archer VR2100 keeps restarting every few hours

2021-01-27 01:27:01

@The-Geek

Thank you very much for getting back with valued info, we appreciate it.

Kindly report this back to the engineers directly, I think they will be happy to continue the debug with you to solve the 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.

#34

adrem7

LV1

2021-02-24 16:23:32

Posts: 1

Helpful: 0

Solutions: 0

Stories: 0

Registered: 2021-02-24

Re:New Archer VR2100 keeps restarting every few hours

2021-02-24 16:23:32

@Kevin_Z

I am getting this issue as well. UK based, Vodafone. Latest firmware.

Can you explain what you mean by "report back to the engineers directly"?

Just got this router a month ago and assumed it was line issues so has taken me this long, dealing with the ISP etc. to realise it might be a router issue. If you could point me to where to go next to get this resolved I'd really appreciate it.

Are you talking about TP-L customer support or something?

Thanks in advance.

#35

naz_eg

LV2

2021-02-24 16:35:11

Posts: 48

Helpful: 10

Solutions: 0

Stories: 0

Registered: 2020-11-20

Re:New Archer VR2100 keeps restarting every few hours

2021-02-24 16:35:11

@adrem7

https://community.tp-link.com/en/home/forum/topic/225790?replyId=567288&utm_source=Subscription&utm_medium=email

#36

Kevin_Z

2021-02-25 03:26:42 - last edited 2021-02-25 03:27:10

Posts: 21755

Helpful: 5137

Solutions: 2565

Stories: 21

Registered: 2018-12-24

Re:New Archer VR2100 keeps restarting every few hours

2021-02-25 03:26:42 - last edited 2021-02-25 03:27:10

@adrem7

Have you upgraded to the latest beta firmware we provided? Kindly give it a go and report back, thanks.

https://static.tp-link.com/beta/2021/202102/20210222/Archer_VR2100V1_210219.zip

#37

New Archer VR2100 keeps restarting every few hours

New Archer VR2100 keeps restarting every few hours

Information

Voters 0

Tags