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.
New Archer VR2100 keeps restarting every few hours
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?

 

 

  0      
  0      
#1
Options
1 Accepted Solution
Re:New Archer VR2100 keeps restarting every few hours-Solution
2021-01-19 06:50:55 - last edited 2021-06-22 02:56:47

Hello all, sorry to hear that you experience an auto-reboot on the VR2100.

 

If the auto-reboot issue, unfortunately, persists on the latest firmware, please kindly check if the latest beta firmware we provided in the below thread:

(Updated on 2021-06-22)

https://community.tp-link.com/en/home/forum/topic/262804

 

This is the guide to update this beta firmware manually:

https://www.tp-link.com/support/faq/1756/

 

I hope this helps, good day.

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 EasyMesh Is Available When Wi-Fi Routers Work in AP Mode as A Controller. Archer AX55V2 Supports WireGuard VPN, EasyMesh Ethernet Backhaul, IoT Network, Speed Limit,and More 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.
Recommended Solution
  0  
  0  
#26
Options
36 Reply
Re:New Archer VR2100 keeps restarting every few hours
2020-06-28 19:02:33
Oh, and this seems similar to this issue here: https://community.tp-link.com/en/home/forum/topic/100196
  0  
  0  
#2
Options
Re:New Archer VR2100 keeps restarting every few hours
2020-06-28 23:54:04

@deKay 

 

Yes, I'm seeing the same issue on my VR2100 (same firmware and build)

  0  
  0  
#3
Options
Re:New Archer VR2100 keeps restarting every few hours
2020-06-29 06:41:57

@DelESC how old is yours?

  0  
  0  
#4
Options
Re:New Archer VR2100 keeps restarting every few hours
2020-06-29 12:19:03

@deKay 

Just a few weeks old

 

  0  
  0  
#5
Options
Re:New Archer VR2100 keeps restarting every few hours
2020-06-29 12:45:44 - last edited 2020-06-29 12:46:31

29/06/2020 10:39:02 PM [6] DHCPC: Unicasting a release of 124.149.41.81 to 124.149.32.1

29/06/2020 10:39:02 PM [5] System: DSL Link Down

 

 

I've set my log for DEBUG and so far all I can see is the release of the ISP IP

  0  
  0  
#6
Options
Re:New Archer VR2100 keeps restarting every few hours
2020-07-01 19:33:34

Still happening. Seems more frequent at times I'm *not* using the internet - it only happened once during the day when I was remotely working, but happened three times this evening and three times over night last night.

 

Not sure if that means anything.

  0  
  0  
#7
Options
Re:New Archer VR2100 keeps restarting every few hours
2020-07-06 08:33:35

I'm concerned the issue is linked to the numerous "DSL Training" entries in the logs. The router is somehow detecting that my DSL connection is still in BT's 14 day training period, when it is not.

 

BT tell me everything is fine with the line, which I believe as my old Home Hub is fine.

 

I currently have the TP-Link router plugged into the BT Master Socket, but the connection is still dropping out.

 

I get the impression I've bought a lemon.

  1  
  1  
#8
Options
Re:New Archer VR2100 keeps restarting every few hours
2020-07-08 06:48:28

I've had enough and am returning the router.

  0  
  0  
#9
Options
Re:New Archer VR2100 keeps restarting every few hours
2020-07-11 23:58:01

@deKay 

 

Hi , I just downloaded and installed the firmware on the website which is an older build than the one that came with the router.

I'll let you know if I see any further disconnections.

 

  1  
  1  
#10
Options
Re:New Archer VR2100 keeps restarting every few hours
2020-07-13 13:41:54

I have a similar issue with my new VR2100.  Its not happening every few hours, but at least twice a week, it will simply crash and restart itself for no apparent reason.  Running the firmware it was supplied with, which as mentioned, is not the same as the one available via the TP-Link website.  Will be interested to hear the results of running with that FW instead.

Cheers,

 

Paul

 

  0  
  0  
#11
Options

Information

Helpful: 0

Views: 6435

Replies: 36

Related Articles