Network Request time out Packet loss
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.Network Request time out Packet loss
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Hello, I'm having trouble with my newly bought router which is the Archer c80, my internet is very unstable and when i ping get a lots of request time out, when i connect my old router, tl-wr840n i have very stable internet and ping but when i switched the C80 it's so unstable, here is a ping a i recently done.
Pinging 172.16.0.1 with 64 bytes of data:
Request timed out (seq=0).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=1).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=2).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=3).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=4).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=5).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=6).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=7).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=8).
Request timed out (seq=9).
Request timed out (seq=10).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=11).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=12).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=13).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=14).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=15).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=16).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=17).
Request timed out (seq=18).
Request timed out (seq=19).
Request timed out (seq=20).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=21).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=22).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=23).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=24).
Request timed out (seq=25).
Request timed out (seq=26).
Request timed out (seq=27).
Request timed out (seq=28).
Request timed out (seq=29).
Request timed out (seq=30).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=31).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=32).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=33).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=34).
Reply from 172.16.0.1: bytes=64 time=16ms TTL=64 (seq=35).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=36).
Request timed out (seq=37).
Request timed out (seq=38).
Request timed out (seq=39).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=40).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=41).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=42).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=43).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=44).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=45).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=46).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=47).
Reply from 172.16.0.1: bytes=64 time=16ms TTL=64 (seq=48).
Reply from 172.16.0.1: bytes=64 time=1ms TTL=64 (seq=49).
Ping statistics for 172.16.0.1:
Packets: Sent = 50, Received = 35, Lost = 15 (30% loss).
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 16ms, Average = 0ms
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
@Sunshine the default gateway is still the same as the old and new router, our isp is pldt, our isp is a private group that uses pppoe connection
- Copy Link
- Report Inappropriate Content
@Sunshine the problem is still the same, I still get a packet loss, I've already changed the MAC address and copied the old router's MAC but still the same packet loss. I'll be providing the details you've been askin
TL-WR840N
Archer C80 (this is the settings before I changed the MAC Address)
The problem is still there, I think the c80's firmware is the problem here. Please fix this
- Copy Link
- Report Inappropriate Content
@Sunshine so earlier at lunch I noticed that the ISP team is conducting a maintenance and they disabled the internet but the router is still connected to its default gateway that means they didn't turn off their PPPoe satellite, at this time the connection with my wan default gateway is very stable, just like my old router, no packet loss was seen. What could this be? Does the archer c80 has problem with handling packets that are going through it?
- Copy Link
- Report Inappropriate Content
hi @Sunshine,
A ping, or other test, should always be performed with a cable.
Wi-Fi is not stable enough to get a correct reading 
Regards,
Thom
- Copy Link
- Report Inappropriate Content
@Thom_NL i already did it with wired through the router and still the same results, i get packet loss
- Copy Link
- Report Inappropriate Content
Hi, thank you very much for the update.
To assist you efficiently, I've forwarded your case to the TP-Link support engineers, who will contact you with your registered email address later. Please pay attention to your email box for follow-up.
- Copy Link
- Report Inappropriate Content
@Sunshine do i talk to them through the email?
- Copy Link
- Report Inappropriate Content
Yes, they will check your case and reply via email, since it is now Friday evening now on our end, I guess they will follow up your case next week.
Please let us know once the issue can be located or resolved.
- Copy Link
- Report Inappropriate Content
@Sunshine Okay, I will let you know
- Copy Link
- Report Inappropriate Content
Information
Helpful: 0
Views: 2216
Replies: 19
Voters 0
No one has voted for it yet.