![]() ![]() Don't give up when they say "We don't see any problems." Try and use normal conditions - if you have a single 5 minute period that's off the charts bad, but it only happened once, that's not a great centerpiece for building your case (way too easy for your provider to discredit). Don't find the very worst case in PingPlotter and send that to Charter.In a LAN environment, this should be clean. If you have two computers, PingPlotter to your other computer and see if you get packet loss / latency. Fixing problems in your own network can sometimes be the easiest solution to a problem. We often see hardware failure or wiring failure in home networks that end users don't think about - bad routers, cabling, hubs, power supplies, power noise, etc. Don't rule out problems inside your own network.If possible, pick a final destination that you're having problems with (a VoIP server, Terminal Services server, game server, etc).Always start with the final destination of PingPlotter for packet loss / latency problems.If you're seeing 50% packet loss in PingPlotter, but your VoIP calls are mostly good, then PingPlotter data and actual network conditions aren't supporting each other, so you need to look at PingPlotter settings to try and make those match. Sometimes, you'll see packet loss in PingPlotter that is an artifact of network configuration and doesn't represent the actual problem well. Always correlate other problems to verify that the PingPlotter data you're collecting is actually representative of the problems you're experiencing.When putting together a case, show them samples from both good times and bad (ideally in the same picture, if possible). In general, the following techniques apply to every provider: It would be great to have your suggestions.We don't have any specific guidance for Charter here (maybe someone from outside does?), but DSL Reports usually has a lot of discussion on different providers and discussion on comments from end users and stories of conversations and successes and failures. More impressive still, at 5 packet loss the throughput over Speedify is well over double that of regular TCP. change the cable between modem and router Speedify’s Performance on Minimizing High Latency and Packet Loss on Comcast Internet In the tests we’ve ran with Speedify, even on a single link you’re largely shielded from damages caused by losing over 1 of the packets.change MTU (1500, 1400, 1300) of the connection between the modem and the router.These are what I tried so far but still ping is so high. ![]() I'm sorry if it sounds so dumb but I think it's the root cause. Accidentally, I removed the ethernet cable of the router and it instantly decreased latency to 70ms (from 3-5 second)! I connected to laptop to the modem with an ethernet cable directly but the ping was so high. I have stable connection to internet, connection to router is fine (latency is less than a millisecond) and the same for the modem (latency is less than a millisecond). I checked almost any moving part in the network. At first, I thought there's something wrong with the ISP but they checked and told me everything seems fine from their side. Recently, I have very high latency (something around 3-5s on pinging 8.8.8.8, similar on other destinations). The router is connected to the modem by an ethernet cable and nothing else is connected to the modem. The modem is responsible for internet connection and the router provides an access point. I have a D-Link ADSL modem (2740u) and TP-Link C7 wireless router.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |