TP-Link Archer MR200 4G LTE Moden Disconnecting Constantly From Broadband
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.TP-Link Archer MR200 4G LTE Moden Disconnecting Constantly From Broadband
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hi Everyone
Just purchased the archer MR200 in South Africa. Inserted a Vodacom LTE simcard and it worked perfectly as per the box states. The only problem i am facing is that the Simcard broadband connection keeps dropping every 1-2 hours if not in use. If the router is sending packets then there are no issues at all, its when the router is idle it disconnects 4g and does not reconnect when required. I have downloaded the system log files and can see where it disconnects, but the debug log is not giving me the information that will help me make and informed decision on which setting is causing this or if there is a hardware problem.
To my knowledge this is not how the router or any router should work. I have setup a profile for the simcard on the router and still not working as expected, check the the carrier / mobile cellular network provider and all my settings are as they should be.
Log:
2016-01-01 02:00:34 [5] 4G: init LTE module, set flowstat [enableDataLimit 1, enablePaymentDay 1, paymentDay 1, limitation 5368709120, warningPercent 90]
2016-01-01 02:00:34 [5] 4G: LTE Module: profile num [2], default profile [1], active profile [1]
2016-01-01 02:00:34 [5] 4G: DM: profile num [2], default profile [1], active profile [1]
2016-01-01 02:00:35 [5] System: Enable IPv4 SPI Firewall
2016-01-01 02:00:35 [5] System: Enable IPv6 SPI Firewall
2016-01-01 02:00:35 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2016-01-01 02:00:37 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2016-01-01 02:00:40 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2016-01-01 02:00:42 [5] 4G: LTE internet connected.
2016-01-01 02:00:49 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2016-01-01 02:00:53 [5] DHCPD: Recv DISCOVER from B4:F1:DA:A7:CF:0A
2016-01-01 02:00:53 [5] DHCPD: Send OFFER with ip 192.168.1.100
2016-01-01 02:00:53 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2016-01-01 02:00:54 [5] DHCPD: Send ACK to 192.168.1.100
2016-01-01 02:00:55 [5] DHCPD: Recv REQUEST from A0:88:69:F6:BC:79
2016-01-01 02:00:56 [5] DHCPD: Send ACK to 192.168.1.101
2016-01-01 02:01:22 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2016-01-01 02:01:22 [5] DHCPD: Send OFFER with ip 192.168.1.102
2016-01-01 02:01:22 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2016-01-01 02:01:23 [5] DHCPD: Send ACK to 192.168.1.102
2016-01-01 02:01:23 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2016-01-01 02:01:23 [5] DHCPD: Send ACK to 192.168.1.102
2016-01-01 02:01:47 [5] DHCPD: Recv REQUEST from A0:88:69:F6:BC:79
2016-01-01 02:01:47 [5] DHCPD: Send ACK to 192.168.1.101
2016-01-01 02:02:10 [5] DHCPD: Recv REQUEST from A0:88:69:F6:BC:79
2016-01-01 02:02:10 [5] DHCPD: Send ACK to 192.168.1.101
2016-01-01 02:02:45 [5] DHCPD: Recv REQUEST from A0:88:69:F6:BC:79
2016-01-01 02:02:45 [5] DHCPD: Send ACK to 192.168.1.101
2016-01-01 02:06:17 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2016-01-01 02:06:17 [5] DHCPD: Send OFFER with ip 192.168.1.102
2016-01-01 02:06:17 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2016-01-01 02:06:18 [5] DHCPD: Send ACK to 192.168.1.102
2016-01-01 02:06:18 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2016-01-01 02:06:18 [5] DHCPD: Send ACK to 192.168.1.102
2016-01-01 02:43:40 [6] 4G: USER: The network disconnected, start autoconnect!
2016-01-01 02:43:40 [6] 4G: USER: Get user's profile now.
2016-01-01 02:43:40 [6] 4G: USER: GetCurrProf result is: ipver:0 staticApn:0 authType:1 pkgName:WayneVodacomeLTE profname:WayneVodacomeLTE apn:internet usr: psw:
2016-01-01 02:43:40 [6] 4G: ERROR: 0x0000000E QMI_ERR_CALL_FAILED
2016-01-01 02:43:40 [6] 4G: ERROR: Call end reason = 3.
2016-01-01 02:43:40 [6] 4G: ERROR: Verbose Call end reason = 2001, type = 3.
2016-01-01 02:43:40 [6] 4G: USER: Fail to connect to the network, start autoconnect!
2016-01-01 02:43:40 [6] 4G: USER: Get user's profile now.
2016-01-01 02:43:40 [6] 4G: USER: GetCurrProf result is: ipver:0 staticApn:0 authType:1 pkgName:WayneVodacomeLTE profname:WayneVodacomeLTE apn:internet usr: psw:
2016-01-01 02:43:43 [5] 4G: lte internet disconnected.
2016-01-01 02:43:44 [6] 4G: USER: Connected to the network!
2016-01-01 02:43:48 [5] 4G: LTE internet connected.
2019-10-24 16:08:48 [6] 4G: USER: The network disconnected, start autoconnect!
2019-10-24 16:08:48 [6] 4G: USER: Get user's profile now.
2019-10-24 16:08:48 [6] 4G: USER: GetCurrProf result is: ipver:0 staticApn:0 authType:1 pkgName:WayneVodacomeLTE profname:WayneVodacomeLTE apn:internet usr: psw:
2019-10-24 16:08:48 [6] 4G: ERROR: 0x0000000E QMI_ERR_CALL_FAILED
2019-10-24 16:08:48 [6] 4G: ERROR: Call end reason = 3.
2019-10-24 16:08:48 [6] 4G: ERROR: Verbose Call end reason = 2001, type = 3.
2019-10-24 16:08:49 [6] 4G: USER: Fail to connect to the network, start autoconnect!
2019-10-24 16:08:49 [6] 4G: USER: Get user's profile now.
2019-10-24 16:08:49 [6] 4G: USER: GetCurrProf result is: ipver:0 staticApn:0 authType:1 pkgName:WayneVodacomeLTE profname:WayneVodacomeLTE apn:internet usr: psw:
2019-10-24 16:08:52 [5] 4G: lte internet disconnected.
2019-10-24 16:08:53 [6] 4G: USER: Connected to the network!
2019-10-24 16:08:58 [5] 4G: LTE internet connected.
2019-10-25 06:38:49 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2019-10-25 06:38:50 [5] DHCPD: Send ACK to 192.168.1.100
2019-10-25 06:44:37 [5] DHCPD: Recv REQUEST from 30:45:96:EF:1A:48
2019-10-25 06:44:38 [5] DHCPD: Send ACK to 192.168.1.106
2019-10-25 06:44:38 [5] DHCPD: Recv REQUEST from 30:45:96:EF:1A:48
2019-10-25 06:44:38 [5] DHCPD: Send ACK to 192.168.1.106
2019-10-25 06:57:56 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2019-10-25 06:57:56 [5] DHCPD: Send OFFER with ip 192.168.1.102
2019-10-25 06:57:56 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 06:57:57 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 06:57:57 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 06:57:57 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:15:27 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2019-10-25 07:15:28 [5] DHCPD: Send ACK to 192.168.1.100
2019-10-25 07:18:47 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2019-10-25 07:18:47 [5] DHCPD: Send OFFER with ip 192.168.1.102
2019-10-25 07:18:47 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:18:48 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:26:02 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2019-10-25 07:26:02 [5] DHCPD: Send OFFER with ip 192.168.1.102
2019-10-25 07:26:02 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:26:03 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:26:03 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:26:03 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:27:33 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2019-10-25 07:27:34 [5] DHCPD: Send ACK to 192.168.1.100
2019-10-25 07:27:36 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2019-10-25 07:27:36 [5] DHCPD: Send ACK to 192.168.1.100
2019-10-25 07:28:45 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2019-10-25 07:28:45 [5] DHCPD: Send OFFER with ip 192.168.1.102
2019-10-25 07:28:45 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:28:46 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:28:46 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:28:46 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:30:29 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2019-10-25 07:30:29 [5] DHCPD: Send OFFER with ip 192.168.1.102
2019-10-25 07:30:29 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:30:29 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:30:29 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:30:30 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:32:45 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2019-10-25 07:32:45 [5] DHCPD: Send ACK to 192.168.1.100
2019-10-25 07:43:41 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2019-10-25 07:43:41 [5] DHCPD: Send OFFER with ip 192.168.1.102
2019-10-25 07:43:41 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:43:42 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:43:42 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:43:42 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:45:14 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2019-10-25 07:45:14 [5] DHCPD: Send OFFER with ip 192.168.1.102
2019-10-25 07:45:14 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:45:14 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:45:14 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:45:15 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:52:05 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2019-10-25 07:52:05 [5] DHCPD: Send OFFER with ip 192.168.1.102
2019-10-25 07:52:05 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:52:05 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 07:52:05 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 07:52:06 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 08:01:39 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2019-10-25 08:01:40 [5] DHCPD: Send ACK to 192.168.1.100
2019-10-25 08:02:09 [5] DHCPD: Recv DISCOVER from 24:FB:65:FA:A9:66
2019-10-25 08:02:09 [5] DHCPD: Send OFFER with ip 192.168.1.102
2019-10-25 08:02:09 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 08:02:09 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 08:02:09 [5] DHCPD: Recv REQUEST from 24:FB:65:FA:A9:66
2019-10-25 08:02:10 [5] DHCPD: Send ACK to 192.168.1.102
2019-10-25 08:27:53 [5] DHCPD: Recv REQUEST from 40:BC:60:81:BD:04
2019-10-25 08:27:53 [5] DHCPD: REQUEST ip 6401a8c0 already reserved by B4:F1:DA:A7:CF:0A
2019-10-25 08:27:53 [5] DHCPD: Send NAK
2019-10-25 08:27:55 [5] DHCPD: Recv REQUEST from 40:BC:60:81:BD:04
2019-10-25 08:27:55 [5] DHCPD: REQUEST ip 6401a8c0 already reserved by B4:F1:DA:A7:CF:0A
2019-10-25 08:27:55 [5] DHCPD: Send NAK
2019-10-25 08:27:55 [5] DHCPD: Recv DISCOVER from 40:BC:60:81:BD:04
2019-10-25 08:27:55 [5] DHCPD: Send OFFER with ip 192.168.1.103
2019-10-25 08:27:56 [5] DHCPD: Recv REQUEST from 40:BC:60:81:BD:04
2019-10-25 08:27:56 [5] DHCPD: Send ACK to 192.168.1.103
2019-10-25 08:55:51 [5] DHCPD: Recv REQUEST from 40:BC:60:81:BD:04
2019-10-25 08:55:51 [5] DHCPD: Send ACK to 192.168.1.103
2019-10-25 08:58:56 [5] DHCPD: Recv REQUEST from A0:A8:CD:39:1A:1B
2019-10-25 08:58:56 [5] DHCPD: Send ACK to 192.168.1.107
2019-10-25 09:01:18 [5] DHCPD: Recv REQUEST from B4:F1:DA:A7:CF:0A
2019-10-25 09:01:18 [5] DHCPD: Send ACK to 192.168.1.100
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Dusan I tried this and nothing worked, I even had to go digging for an old Huaewi router i have and i don't have issues meaning the router is the problem. I'm just suprised with the lack of interest shown by TP-link, no definite solutions, let alone comment.
- Copy Link
- Report Inappropriate Content
Hello everyone,
By way of update on my side
- MR200 kept disconnecting frequently and it was not doing what it is supposed to do
- strength of 4G / 4G+ / LTE signal had been thoroughly tested
- I have been "suffering" with this product for 9 months now and we have decided to give up on MR200
- MR600 seems to receive proportionally fewer complaints than lower models such as MR200 and MR400, although it is not quite clear why
- interactions and files received from tech support seem to indicate that the firmware and testing tools for the MR600 are more recent and more effective
- given the help of the tech support team so far, while we can certainly be critical, they did reply, so I have
i) used the product warranty to return the MR200 (awaiting refund)
ii) given a 2nd chance to TP-Link by buying the more expensive and hopefully better MR600.
The first initial connection shows download speed with MR600 that are at leat 25% faster than before (did 5 speed tests).
I will try to make it work in a reliable way (i.e. without connection interruptions) and will update my finding further on the MR600 forum thread.
Best,
- Copy Link
- Report Inappropriate Content
@ProjectQuad
Yest , thank you for information provided and looking foreward your experiance with higher model.
I am hestitating about buying new product from this company . I am not sure wether this is good idea .
If you took in mind they are not able to do some software fix to this it is kind shame.
Its main ( MR200) purpose is to provide modulation from 4G to consumable data stream . Because of this it does not fullfill the main functionality it is not such as some additional feature.
And if the company can solve such elementary job - I mean make the main function be stable and workable or provide fix for it I think people should put hands off from such company and decide for product of another one.
The same I did with A*US brand. Me , and my 3 friend we bought device in same category . Notebook suffered with issue that it accidentaly / randomly turns off.
What the f*ck of moroons are they they were not able to "find" a root cause. They changed (I do not belvie that) 2times motheboard and third time GPU They said ...lol
At the end of the warratny they said that the another component (CPU) is wrong and this component is no longer in waranty (3y of replacing motheboard , aging etc... )
So i make own opinion on this ... and of such companies and me and also friends do not buy product from such brand.
Than after month of investigation and logical steps (tests on this device ) I found out something is wrong with the HDD . I replaced that with SSD and it is still fully functional today. No random shutdowns.
What I want to point out its they shoud at least do some firmware fix (because what every time I need to do is to go the tplinkmodem.net page and swtich off and on connect slider) and it works again so it is simple , they should do some fix but they did not , dont and will not ... (at least some stupid autorefresh) or give fucking firmware files public someone can do the fix at least.
So my opinion is if something like this happend people should end up with such company.
Act of "buying" means you belive the idea of the company and you want they to prosperity and you put them some value in and get some cointer - value from them and give them in order to continue , prosper , make a profit , whatever - do the better and better products and satisfy customers ... But I feel there something different going on...
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 13255
Replies: 13
Voters 0
No one has voted for it yet.