Constant 2k Ping when playing games with ETHERNET!

[Leakan8]

I need some help PLEASE! I an directly plugged to the internet using an Ethernet cable. I use two 25 ft. ethernet cables put together with an adapter. I NEVER get 2000 ping but lately i cannot play any games. I usually run 45ms in game but now it ranges from 500ms to 2400ms. MY IP is fine at 192.168, I've checked all problems, I even have 34 mbps with 12 for download speeds and 12ms when tested on Speedtest.net. I do not know what the problem is.

I do not know how to fix my 2000 ping! Can someone help?

 

[dgingeri]

First, test the latency to these targets:
1. local gateway
2. another local system, if possible
3. the gaming servers you use
4. other gaming servers you don't normally use
5. a public service, such as Google's DNS, 8.8.8.8

This will narrow down where the latency hits, and where the cause would be.

 

[Leakan8]

First, test the latency to these targets:
1. local gateway
2. another local system, if possible
3. the gaming servers you use
4. other gaming servers you don't normally use
5. a public service, such as Google's DNS, 8.8.8.8

This will narrow down where the latency hits, and where the cause would be.

I have no idea what that means. I am no computer geek. Could you please simply your solution in a way that I would understand it? Here are my results by the way.

 

[dgingeri]

Latency is just the ms it takes for a ping to return, or really any delay to an operation, so everything has latency. In this case, I'm just looking for the response time in the network.

For this, open the command prompt and just type "ping" and a destination, either by IP address or name. The DNS server will convert the name to the IP address if it is valid and list it with the ping. The response will come back with a time to respond and a TTL. Don't get them mixed up. It's like this:

c:\>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 32ms, Average = 32ms

To find out your gateway, type in "ipconfig /all" and look for your gateway setting there. You may have multiple listings, so be careful to get the one associated with your wired network adapter.

 

[captaincharisma]

what kind of adapter are you using?

 

[Leakan8]

what kind of adapter are you using?

It is just an adapter to connect one 25ft ethernet cable to the other 25ft ethernet cable to create one 50ft connection to my PC.

 

[Leakan8]

Latency is just the ms it takes for a ping to return, or really any delay to an operation, so everything has latency. In this case, I'm just looking for the response time in the network.

For this, open the command prompt and just type "ping" and a destination, either by IP address or name. The DNS server will convert the name to the IP address if it is valid and list it with the ping. The response will come back with a time to respond and a TTL. Don't get them mixed up. It's like this:

c:\>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 32ms, Average = 32ms

To find out your gateway, type in "ipconfig /all" and look for your gateway setting there. You may have multiple listings, so be careful to get the one associated with your wired network adapter.

I'm still not understand what to do. I am in Command Prompt and I have all my listings and one that says "Ethernet Adapter Ethernet:" This is what i got when i put ping and the host name. inging Clifford [fe80::ed9f:f2fe:dbf6:a258%5] with 32 bytes of data:
Reply from fe80::ed9f:f2fe:dbf6:a258%5: time<1ms
Reply from fe80::ed9f:f2fe:dbf6:a258%5: time<1ms

 

[dgingeri]

Latency is just the ms it takes for a ping to return, or really any delay to an operation, so everything has latency. In this case, I'm just looking for the response time in the network.

For this, open the command prompt and just type "ping" and a destination, either by IP address or name. The DNS server will convert the name to the IP address if it is valid and list it with the ping. The response will come back with a time to respond and a TTL. Don't get them mixed up. It's like this:

c:\>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 32ms, Average = 32ms

To find out your gateway, type in "ipconfig /all" and look for your gateway setting there. You may have multiple listings, so be careful to get the one associated with your wired network adapter.

I'm still not understand what to do. I am in Command Prompt and I have all my listings and one that says "Ethernet Adapter Ethernet:"

Yes, that's the info you're looking for. Under that listing is a setting called "default gateway". ping that first. It should be <1ms for a ping time. If the trouble is with your PC, it will be longer.

 

[Leakan8]

Latency is just the ms it takes for a ping to return, or really any delay to an operation, so everything has latency. In this case, I'm just looking for the response time in the network.

For this, open the command prompt and just type "ping" and a destination, either by IP address or name. The DNS server will convert the name to the IP address if it is valid and list it with the ping. The response will come back with a time to respond and a TTL. Don't get them mixed up. It's like this:

c:\>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41
Reply from 8.8.8.8: bytes=32 time=32ms TTL=41

Ping statistics for 8.8.8.8:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 32ms, Maximum = 32ms, Average = 32ms

To find out your gateway, type in "ipconfig /all" and look for your gateway setting there. You may have multiple listings, so be careful to get the one associated with your wired network adapter.

I'm still not understand what to do. I am in Command Prompt and I have all my listings and one that says "Ethernet Adapter Ethernet:"

Yes, that's the info you're looking for. Under that listing is a setting called "default gateway". ping that first. It should be <1ms for a ping time. If the trouble is with your PC, it will be longer.

Pinging 192.168.1.1 with 32 bytes of data:
Reply from 192.168.1.1: bytes=32 time<1ms TTL=239
Reply from 192.168.1.1: bytes=32 time<1ms TTL=239
Reply from 192.168.1.1: bytes=32 time<1ms TTL=239

This is what i got.

 

[dgingeri]

OK, so the trouble isn't with your PC directly. It could still be in software. Do you know the game server name or IP address? If not, what game is it?

 

[Leakan8]

OK, so the trouble isn't with your PC directly. It could still be in software. Do you know the game server name or IP address? If not, what game is it?

The game is League of Legends. I do not know their server name or IP address.

 

[dgingeri]

OK, I was able to find out that the LoL router to the gaming servers is 208.76.153.129. Ping that, as the actual game servers won't directly respond to pings, so I'm told.

 

[dgingeri]

Oh, cancel that, there have been some changes since that posting. Now, they have 2 servers that do respond to pings that are used to directly measure game response: 104.160.131.1 and 104.160.131.3

 

[Leakan8]

Oh, cancel that, there have been some changes since that posting. Now, they have 2 servers that do respond to pings that are used to directly measure game response: 104.160.131.1 and 104.160.131.3

Pinging 104.160.131.1 with 32 bytes of data:
Reply from 104.160.131.1: bytes=32 time=29ms TTL=60
Reply from 104.160.131.1: bytes=32 time=27ms TTL=60
Reply from 104.160.131.1: bytes=32 time=31ms TTL=60


Pinging 104.160.131.3 with 32 bytes of data:
Reply from 104.160.131.3: bytes=32 time=37ms TTL=59
Reply from 104.160.131.3: bytes=32 time=40ms TTL=59
Reply from 104.160.131.3: bytes=32 time=48ms TTL=59

 

[dgingeri]

Those look pretty quick. It doesn't look like the network/internet is responsible. It might be server side. the servers might just be too busy to repsond quickly enough. I get this problem with Star Trek Online rather often as the server gets overloaded.

When you next run into this issue, immediately log out of the game and ping those two addresses to see what the actual network response time is. You can also use "tracert" to find the response time for every step in between your computer and the game servers. That might be helpful.

 

[Leakan8]

Those look pretty quick. It doesn't look like the network/internet is responsible. It might be server side. the servers might just be too busy to repsond quickly enough. I get this problem with Star Trek Online rather often as the server gets overloaded.

When you next run into this issue, immediately log out of the game and ping those two addresses to see what the actual network response time is. You can also use "tracert" to find the response time for every step in between your computer and the game servers. That might be helpful.

So for now there is nothing really wrong? Also is tracert a program?

 

[dgingeri]

tracert is like ping, but it measures the latency of every router between the source and the destination, to try to narrow down the source of trouble.

 

[Leakan8]

tracert is like ping, but it measures the latency of every router between the source and the destination, to try to narrow down the source of trouble.

Thank you for your help!