Insanely high ping with Ethernet cable (GAMING)

Toggle sidebar Toggle sidebar
G

Gunerol

Commendable
Feb 12, 2017
7
0
1,510
Hi,

I've had this problem for so long and I've tried EVERYTHING I can think of!
I had a problem with rubber-banding in games like CS:GO and high ping (500+) while I was running a high-spec wireless adapter for my computer.

So, I got a pair of £90 Ethernet adapters and switched to wired!
It worked perfectly for around an hour and then just went back to the usual rubber-banding.

The internet sometimes cuts out completely, but is solved by restarting the adapter, so that isnt much of a problem, but what is frustrating is that my ISP (virgin media UK) package is the fastest they have, with fibre optic cable and I'm still getting ridiculous lag in games such as Battlefield 1. At times, it's completely fine with no rubber-banding at low ping or high pings, but other times, it's completely un-playable.


I have tried TCP optimizer with no luck.
I have Driver Booster 4 to keep all my drivers up to date so I doubt it's to do with that.

Here's me pinging google.co.uk if it might help.
This pinging was quite normal, but every other time I test, the time sometimes goes above 700ms and below 200ms
EWBFJI.jpg


My specs (I don't know if this will help):
CPU: i5 6600
GPU: R9 390
RAM: 16GB DDR4
Motherboard: GIGABYTE Z170-GAMING K3

Any help appreciated!

Many thanks.

[SOME TESTS THAT PEOPLE HAVE SUGGESTED]
Google.co.uk
Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Go Away>tracert google.co.uk

Tracing route to google.co.uk [216.58.198.227]
over a maximum of 30 hops:

1 12 ms 12 ms 12 ms 10.158.68.1
2 13 ms 12 ms 12 ms bmly-core-2b-xe-003-0.network.virginmedia.net [8
0.1.224.85]
3 * * * Request timed out.
4 13 ms 13 ms 16 ms tele-ic-7-ae2-0.network.virginmedia.net [62.253.
175.34]
5 18 ms 49 ms 18 ms 74.125.52.226
6 21 ms 20 ms 20 ms 108.170.246.193
7 19 ms 21 ms 19 ms 209.85.241.83
8 14 ms 15 ms 17 ms lhr26s04-in-f3.1e100.net [216.58.198.227]

Trace complete.


8.8.8.8

C:\Users\Go Away>tracert 8.8.8.8

Tracing route to google-public-dns-a.google.com [8.8.8.8]
over a maximum of 30 hops:

1 16 ms 16 ms 16 ms 10.158.68.1
2 16 ms 14 ms 16 ms bmly-core-2b-xe-002-0.network.virginmedia.net [8
0.1.227.181]
3 * * * Request timed out.
4 15 ms 17 ms 18 ms tele-ic-7-ae2-0.network.virginmedia.net [62.253.
175.34]
5 18 ms 20 ms 18 ms 74.125.48.190
6 490 ms 34 ms 763 ms 108.170.246.225
7 27 ms 27 ms 28 ms 72.14.239.153
8 23 ms 18 ms 16 ms google-public-dns-a.google.com [8.8.8.8]

Trace complete.
 
Solution
C

Before going much further, can you confirm how many computers or other devices ar sharing your connection, or at least confirm no one else is downloading while you play?

Looking at lines 2 and 4, we can assume line 3 is also a node within Virgin's networks. That line shows request timed out. This could be caused by a node that is unresponsive or by the node deliberately not responding to ICMP (ping) traffic. The thing is, if I were the ISP, my ability to diagnose certain problems would be greatly diminished by turning that off for internal nodes. If that node becomes overloaded at times, it could cause high latency for you. I think that is unusual, but may not...
Sort by date Sort by votes
@Suztera Yep, power line adapters.
My router is in the loft for the reasons of CCTV cameras so it's not possible to do that 🙁
I know that many of my friends have powerline adapters with no problems
 
Upvote 0 Downvote


Powerline depends on the electrical wiring of your property and there are many factors that can affect them as well.
Problem is the power line adapters/electrical wiring of your property, not your system or the ISP.
 
Upvote 0 Downvote
Do you have your own router or is it managed by your ISP? Perhaps the "modem" unit your ISP provided is also the router.

At any rate, assuming the modem and router are ruled out as problems, I would look to a problem within the ISP's networks. Try running a traceroute to a known address and look at the 4th column values, and if any of them below the first two or three entries are in the order of hundreds of milliseconds, chances are it's a problem in your ISP's network routing and they have to resolve it for you.

In Win 10 cmd.exe window, command would be something like "tracert google.co.uk"
It will run for a few seconds and you'll see lines of information showing the timing between network hops between you and "google.co.uk".

Sample from my own system in Florida, USA (with my local addresses edited out):

Java: 
C:\Program Files\VCG\MeshLab>tracert google.com

Tracing route to google.com [X.X.X.X]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  X.X.X.X
  2     7 ms     6 ms     7 ms  X.X.X.X
  3     8 ms     7 ms     6 ms X-X-X-X.net.bhntampa.com [X.X.X.X]
  4    15 ms     9 ms    12 ms  ten0-9-0-3.orld71-car2.bhn.net [71.44.61.70]
  5     9 ms    12 ms    10 ms  72-31-188-136.net.bhntampa.com [72.31.188.136]
  6    10 ms    15 ms    15 ms  10.bu-ether15.orldfljo00w-bcr00.tbone.rr.com [66.109.6.98]
  7    23 ms    22 ms    23 ms  bu-ether18.atlngamq47w-bcr01.tbone.rr.com [66.109.1.72]
  8    20 ms    18 ms    19 ms  205.197.180.41
  9    20 ms    21 ms    20 ms  205.197.180.54
 10    19 ms    19 ms    24 ms  216.239.51.47
 11    37 ms    32 ms    23 ms  216.239.51.243
 12    18 ms    19 ms    30 ms  72.14.234.121
 13     *     ^C
 
Upvote 1 Downvote
Well this thread has a completely misleading heading. The problem is not ethernet, a PURE ethernet connection is as simple and trouble-free than anything, so you got a PowerLine in between, WELL! you just hit the rule of the WEAKEST LINK. PowerLine is your issue, and as others responded, what works for your friends may not work at yours.

If you suspect the ISP, then hook it up directly right behind the ISP Gateway, here you are talking directly to the ISP with nothing in between. Doesn't work here, your ISP's fault (or their Gateway box).
 
  • Like
Reactions: Thepersonwhoneedshelp
Upvote -2 Downvote


Except the OP clearly stated he was running 500+ pings when using a high-spec wireless adapter too. Granted, there are many variables with wifi as well.
 
Upvote 1 Downvote


User said it worked fine for an hour, if the links were the problem why it'd take them an hour to fail? Makes little sense, also, wireless has the same problem so the problem could be in the cable modem or in the fiber wire
 
Upvote 1 Downvote
Until you can test with a directly connected ethernet cable you are going to get nowhere. This is especially true if you try to tell the ISP some silly in game ping number that is affected by things that are not network. Very few games actually use a real ping command and even those that do do not isolate the thread that is running it so the game client load can affect it.

The ISP will claim they have tested their stuff to your router and see no problems.....even if this is not really true. You at that point only have 2 options, you work to prove they are wrong or you cancel your service

I would use 8.8.8.8 rather than the google.com ip. It is a google dns server and tends to never have any issues. Note there are multiple servers that share the 8.8.8.8 ip around the world.

The ISP should accept a long ping showing these poor latency. You can run a tracert to the ip also but most level 1 ISP techs will not understand it.

Still no matter what you do you must be ready for the idiot ISP guys. If they can they will blame anything and everything in your house. If you have wireless or powerline they will blame those for obvious reasons. Be sure you even try multiple ethernet cables. You know ...turning off and on your pc will fix it too :)
 
Upvote 1 Downvote
@Elysian890 The modem is provided by the ISP a year ago as their best one (comes with the bundle).
English weather during this time of the year is around 8oC +/- 10
yeah, it's up n running 24/7 except when I restart it when the lag becomes unbearable.
 
Upvote 0 Downvote

Please see my tests if you know what's the problem !

Many thanks
 
Upvote 0 Downvote
Both the tracert show no problems really. There is a slight spike to some node in the middle but that may not mean anything.

What this trace does is pretty much say it is the game itself causing the issues and it is not really a network problem.

It may or may not be true you must run many more tracert or better ping each node in the trace. Still if the problem is not in the first couple hops it means it is far from your house. The ones in that trace show problems in googles network....what can you possibly do to get that fixed you are not their customer.

Pretty much the only ones you can get fixed easy are problems with hop 1 which is your router and hop 2 which is the ISP first router. I suppose you could run constant pings to those hoping to see your problem but it very well could be the game and not a network issue.
 
Upvote 0 Downvote

Before going much further, can you confirm how many computers or other devices ar sharing your connection, or at least confirm no one else is downloading while you play?

Looking at lines 2 and 4, we can assume line 3 is also a node within Virgin's networks. That line shows request timed out. This could be caused by a node that is unresponsive or by the node deliberately not responding to ICMP (ping) traffic. The thing is, if I were the ISP, my ability to diagnose certain problems would be greatly diminished by turning that off for internal nodes. If that node becomes overloaded at times, it could cause high latency for you. I think that is unusual, but may not be the ultimate cause of your problem if turning off ICMP responses was deliberate on their part. All other lines look fine, including, by the way, your own devices (router/modem router).

I don't think the games are the problem unless you are somehow connecting to game servers well outside your region. If you are still experiencing high ping a the time you get these trace results, at least they show the issue is likely not within your home and the ISP may have to address.

I do agree with another post that said that typical "level 1" support staff at the ISP may not understand traceroute results. I've had similar high ping problems in the past and at least with my ISP, I was able to do the following:
1. Called ISP support
2. Informed the representative of the basic high ping issue.
3. Also immediately informed them I have already taken steps to diagnose, including power-cycling all equipment, and connecting directly to the modem/router device. I understand this was not actually practical for you.
4. Informed them that I had network trace information pointing to an issue within their network, and politely requested to speak to a network technician. I basically said I was sure with the info. I had, their tech. would be able to make sense of it and quickly resolve the issue.

I was connected to a network tech. I explained my situation and traceroute results. He confirmed the same on his end, made some changes and asked to to reboot my cable modem. Problem fixed in a matter of minutes.
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom