TP-LINK TL-WN851ND Connection & Ping Problems Only in Dota 2 Games

Toggle sidebar Toggle sidebar
H

Haden

Reputable
May 13, 2015
23
0
4,510
Specs:

Wireless adapter: TP-LINK TL-WN851ND
Router: NETGEAR Genie
Modem: the one supplied by our internet/phone/cable company, idk
My PC is brand new, and custom, and this problem was on my old PC, so it isn't like my motherboard or anything.

Question:

Hey, guys, I use a TP-LINK TL-WN851ND wireless adapter, and I have great internet. 50 download, like 20 upload, and like 85 ping across the US.

But for some reason, when I use a Valve server (whom uses Amazon servers, I believe) I always get 100+ ping, sometimes 300+. It's extremely unstable, and laggy, but I don't know why. And it's only in Dota 2/CS:GO servers.

Is there anything I can do? I use a 2.4GHz wireless adapter, the TP-LINK, and I have a cheap $15 5GHz wireless adapter, that I use on my 5GHz network and it is just as laggy. What is going wrong?
 
Sort by date Sort by votes
B

bill001g

Titan
Aug 9, 2012
28,322
2,755
125,640
Wireless tends to be the common cause of issues like this. You want to first test with a ethernet cable so you do not spend a lot of time trying to fix the wrong thing. Some games are much more susceptible to wireless issues than others.

In a way you have to hope it is a issue with your wireless, if there is something wrong with the path between your house and just a small group of servers that means it is deep inside your ISP or the server ISP network and there is little a home user can do.
 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,322
2,755
125,640
Tracert is a line mode command that is part of the OS and pathping is a very common utility.

I would start with tracert since you don't have to download anything.

This I suspect is going to be quite a challenge because the command is not some magic thing that will tell you what the problem is you need to be able to interpret the screens. It is very concerning that you do not even know the command exists so you have much to learn.

There are a bunch of wiki things on how to use tracert to determine problems.
 
Upvote 0 Downvote
H

Haden

Reputable
May 13, 2015
23
0
4,510
I believe I found the problem. I used TRACERT to the Dota 2 US East Servers (I'm NC)
Look for 2 the highlighted lines...

C:\Users\UserAccount>ping 208.78.164.1 -t Pinging 208.78.164.1 with 32 bytes of data: Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=58ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=996ms TTL=52
Reply from 208.78.164.1: bytes=32 time=45ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=44ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=46ms TTL=52
Reply from 208.78.164.1: bytes=32 time=38ms TTL=52
Reply from 208.78.164.1: bytes=32 time=45ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=53ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=59ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=38ms TTL=52
Reply from 208.78.164.1: bytes=32 time=43ms TTL=52
Reply from 208.78.164.1: bytes=32 time=43ms TTL=52
Reply from 208.78.164.1: bytes=32 time=45ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=49ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=45ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=43ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=45ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=54ms TTL=52
Reply from 208.78.164.1: bytes=32 time=43ms TTL=52
Reply from 208.78.164.1: bytes=32 time=38ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=44ms TTL=52
Reply from 208.78.164.1: bytes=32 time=55ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=43ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=45ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=51ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=624ms TTL=52
Reply from 208.78.164.1: bytes=32 time=38ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=53ms TTL=52
Reply from 208.78.164.1: bytes=32 time=47ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=38ms TTL=52
Reply from 208.78.164.1: bytes=32 time=38ms TTL=52
Reply from 208.78.164.1: bytes=32 time=49ms TTL=52
Reply from 208.78.164.1: bytes=32 time=38ms TTL=52
Reply from 208.78.164.1: bytes=32 time=43ms TTL=52
Reply from 208.78.164.1: bytes=32 time=44ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=39ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=41ms TTL=52
Reply from 208.78.164.1: bytes=32 time=40ms TTL=52
Reply from 208.78.164.1: bytes=32 time=42ms TTL=52
 
Upvote 0 Downvote
H

Haden

Reputable
May 13, 2015
23
0
4,510
Oh here is the actual 30 hops TRACERT:



Tracing route to 208.78.165.136 over a maximum of

1 <1 ms <1 ms <1 ms 192.168.1.1
2 1 ms 3 ms 1 ms 192.168.0.1
3 * * * Request timed out.
4 14 ms 12 ms 12 ms user-76-73-147-153
5 12 ms 12 ms 11 ms user-24-96-198-65.
6 12 ms 12 ms 12 ms user-24-96-153-105
7 16 ms 13 ms 11 ms user-24-96-198-174
8 12 ms 18 ms 20 ms user-24-96-153-38.
9 28 ms 28 ms 35 ms user-24-96-153-9.k
10 55 ms 43 ms 44 ms user-24-96-153-14.
11 45 ms 50 ms 60 ms eqnx-v4-1.iad.valv
12 45 ms 47 ms 41 ms 192.168.120.22
13 39 ms 43 ms 39 ms 192.168.120.2
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.
 
Upvote 0 Downvote
B

bill001g

Titan
Aug 9, 2012
28,322
2,755
125,640
Most people would kill for a ping that stable. You have no packet loss and if you ignore the 2 packet your variation (ie jitter) between ping packets is less than 10ms. A couple of ping spikes here and there will have little effect. Bad ones have 5-10 of these high pings in a row.

It is strange you do not see tracert to the end but that is likely a firewall at the remote end.

It is going to be very hard to find this since it happens so seldom. What you basically do is ping every hop in the trace from different command windows trying to find the one that it starts in. This is what pathping does. The main difference is pathping send lots of data and can interfere with other software. So if pathping show nothing what you are better off doing is running pings in lots of command windows and running your game. When you see a big issue in the game you quickly stop all the ping commands and see if one tells you something.


Still lets just assume the problem is in hop 10 of your trace. Who can you call and complain to. You can with some digging find which ISP owns that router but its not like you can call them up and even talk to them you are not their customer your ISP is their customer and there may actually be a number of ISP in between.

Your problem very well could be something else that just appears to be a network problem. Run the resource monitor and see if anything else is happening on the machine when you see the ping spikes. Sometimes the machine lies to you because it is busy doing something else and network gets delayed. Now if you see these ping spikes on multiple devices in your house all at the same time that points to a actual network issues.





 
Upvote 0 Downvote
H

Haden

Reputable
May 13, 2015
23
0
4,510
Yes, I love my internet, and my wireless adapter. But 120+ ping is unplayable. Well it wasn't before, but I'm getting spikes. I emailed TP-LINK, we'll see their response. What can I do besides that? Valve says it isn't on their end,
 
Upvote 0 Downvote
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom