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.
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?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
It's weird. I had an Asus DSL-N17U router before but never had any issue like this. My problem was started after change it to VR2100 so i don't think there's a problem with the cables.
- Copy Link
- Report Inappropriate Content
I have also been suffering regular reboots and have been working with TP-Link Support trying different Firmware etc's however the situation has not changed and the router is rebooting on average once per day still even when using the latest (now published) firmware. I have even put the router in 'wireless router mode' and used my original BT router as a modem only however the VR2100 still restarts when only being used as a wireless router. So this proves that the problem is nothing to do with the Internet line. I assume its a firmware/hardware issue with my VR2100.
I've just restarted the RMA process with support and will let you all know how I get on....
- Copy Link
- Report Inappropriate Content
I've just come accross another thread, https://community.tp-link.com/en/home/forum/topic/243110?page=2
that says, this issue is fixed in the latest beta version dated 2021-01-06
I am happy to try that if available..
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
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.
- Copy Link
- Report Inappropriate Content
Hi again, unfortunately i had 2 DSL drops (or reboot, i couldn't see the lights) since the latest beta firmware :(
- Copy Link
- Report Inappropriate Content
Can you please show us the firmware version on the VR2100? When you mean dropouts, can you confirm if none of your devices can access the internet via the VR2100? No wireless devices can see the signal? Will this hand/reboot recover automatically? How long does it take?
Who is your ISP?
- Copy Link
- Report Inappropriate Content
I can confirm none of my devices can access the internet when it drops. I don't remember the wifi status exactly but the wifi was online on the last drop. It takes 1-2 min to get back and my ISP is Vodafone Net.
- Copy Link
- Report Inappropriate Content
That's bad. Can you report this to the engineer directly via email? I remember they have helped with the debug previously?
- Copy Link
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 6481
Replies: 36
Voters 0
No one has voted for it yet.