@Kevin_Z

Thanks for responding.

The model is Archer C2300 (EU).

Kevin_Z wrote:

"What is the light status of the Archer AC2300 at that time?"

Currently it's light status is white, internet is connected. Reboot always fixes the issue.

What light color should I expect when the internet is disconnected? Red?

Kevin_Z wrote:

"At the same time, with your computer connected to the modem directly, can you access internet?"

I will have to wait for this issue to happen again in order to provide you with the information you requested. It happens sometimes once a week and sometimes once a month. I didn't quite keep note of the exact timeline. I will try to plug the PC directly to the socket (it's a fiber ethernet socket, no modem) next time.

I did call the ISP one time, and they had reported the router didn't sync with the connection and to reboot it.

I tried to look into the system logs on the router inferface and could not find anything useful. I've enabled debug mode yesterday in the hope that would have some useful info.

Which of the many log options there should I be looking at?

Have a nice day too, and a great year!

Kevin_Z wrote

 

When Archer C2300 stops working, please connect computer to the modem directly and test the network connection; it it works properly, you can connect computer back to the Archer C2300 and login to the web UI to clone the MAC address.

@Kevin_Z

I will do that.

By clone the MAC address, you meant take a screenshot of the router status?

There was nothing in the instructions you linked to about cloning the MAC address.

@Kevin_Z 

It just happened again.

Here's what I did:

1) Took a screenshot while net was disconnected - net light on router was red.

2) Connected PC directly to link - works fine.

3) Reconnected link back to router and pc to router - works again. Took screenshot again for comparison.

4) Saved log

Seems at least this time just reconnecting the cable to the router brought connectivity back. In the past I rebooted instead. Could be that was not needed before either.

From what I can see in the log it's failing to renew IP address:

After reconnecting cable (from last to first):

2020-01-05 21:51:32 dhcpc[26274]: <6> 293050 Obtaining Dynamic IP X.X.X..141 succeeded.
2020-01-05 21:51:32 dhcpc[26274]: <7> 293035 Receiving DHCP ACK from server X.X.X..1 with address X.X.X..141 and lease time 600
2020-01-05 21:51:29 dhcpc[26274]: <7> 293032 Sending DHCP Request to server X.X.X..1 for selecting address X.X.X..141
2020-01-05 21:51:29 dhcpc[26274]: <7> 293031 Receiving DHCP Offer from server X.X.X..1 with address X.X.X..141
2020-01-05 21:51:29 dhcpc[26274]: <7> 293030 Sending DHCP Discover
2020-01-05 21:50:23 ddns[25397]: <6> 214014 Dynamic dns dyndns logout
2020-01-05 21:50:22 nat[25051]: <6> 211501 Initialization succeeded
2020-01-05 21:50:22 nat[25051]: <6> 211501 Initialization succeeded

Sync lost:

2020-01-05 21:30:43 dhcpc[5043]: <7> 293033 Sending DHCP Request to server X.X.X.1 for renewing address X.X.X.197
2020-01-05 21:25:43 dhcpc[5043]: <6> 293050 Obtaining Dynamic IP X.X.X.197 succeeded.
2020-01-05 21:25:43 dhcpc[5043]: <7> 293035 Receiving DHCP ACK from server X.X.X.1 with address X.X.X.197 and lease time 600
2020-01-05 21:25:40 dhcpc[5043]: <7> 293033 Sending DHCP Request to server X.X.X.1 for renewing address X.X.X.197

Where can I share the files with you? I'm not interested to post them openly here.

Thanks.

I have the same problem I thought it was my ISP. But after contacting them several times to tell me there isn't any problem with the service. I just now  did a search to see if anyone else has the same problem. I haven't made any changes to the router. The only thing I've done is enabled on Windows to have my notifications from my mobile phone sent to my PC. And if this in some way causes the router to disconnect "randomly" I don't have to restart the router to get internet again. I only have to refresh the DNS or IP using the function on the router. So it seems to me I have the exact same problem as the thread starter. This problem started about two months I got disconnected three or four times. The same has been happening this month. So to recap. The fact that my problem is a identical to the one who wrote this thread indicates that the problem is indeed with this router model and I want a fix ASAP.

@LinkMe 

A I got nowhere posting here, I instead had a long back and forth with the TP-Link support which was very responsive.

In my case at least, the solution was to move back to the original firmware (you need to gradually downgrade it down). I was hoping TP would release a fixed new version that includes the benefits of the later firmwares but as this router is now in Rev B it seemed they are uninterested in fixing the Rev A firmware.

I had another case of disconnection about a month after downgrading and have contacted them again and received a modified firmware to try, but I never got round to trying it as I was waiting for this to become an issue again to be sure it wasn't just a one-off. It hasn't happened so I'm still on the downgraded firmware till it becomes an issue again.

I'm happy to post the process I was prompt to do if you think you'd want to try it too.

@thornton 

Interesting. I would really like to avoid downgrading to an earlier version. I can't understand how this just starting to happen when I haven't changed anything and the same (latest) firmware running sense I bought it. And That firmware is already old in my opinion it's from 2018. If it continues to happen I will try it or I will demand they give me a unit that doesn't suffer from this crap

@LinkMe 

I was not very happy to downgrade either, but it was either that or get a different router. It was cheaper to downgrade :p

I asked several times that the latest firmware will get fixed (as you said it's already quite old as it is), and was always answered it's unlkely to happen as the current model is Rev B and they have no immidiete plans to add new support for the Rev A models. They also claimed the latest firmware doesn't have a lot of added value anyway. Though the smb improvements looked to be something important to me.

From what I've gathered our cases were not isolated ones. It is quite odd like you said, it would just start happening after some use time it was fine. It was unbearable having

link sync loss a few times a week.

It is likely the next router I'll buy will not TP-Link.

thornton wrote

 

It is likely the next router I'll buy will not TP-Link.

@thornton 

Exactly! I hate companies that doesn't own their mistakes. Instead they move on with a new product. So we will do the same 😂🤦