so when i try to play on tf2 servers i get over 300 ping . before i had normal ping and now my ping is on seizures
any help?
any help?
Try google dns and see if the problem still exists
https://developers.google.com/speed/public-dns/docs/using
scroll down to "windows" section for the guide
https://developers.google.com/speed/public-dns/docs/using
scroll down to "windows" section for the guide
do 'ping -t www.google.com' in a cmd as admin. if it's still high then there's either a major routing problem or your line (to your house or neighbourhood) is congested
then most likely someone's downloading a shit-tonne of hentai and they live very close to you
AfsTry google dns and see if the problem still exists
https://developers.google.com/speed/public-dns/docs/using
scroll down to "windows" section for the guide
DNS wouldn't affect his ping to game servers AT ALL
gemmdo 'ping -t www.google.com' in a cmd as admin. if it's still high then there's either a major routing problem or your line (to your house or neighbourhood) is congested
You don't need to open cmd as an admin to ping anything and -t would only cause it to just keep pinging. This is useless.
What you should do is find out if your connection issue is specific to a certain locale (IE: Chicago servers? Dallas? New York?). Once you figure that out see if it's a specific server provider(s). If there's multiple you should do a tracert to a gameserver for each provider and see if there are any hops in common. Send that off to your ISP and show them your routing issue, and just-in-case send it off to a server provider and see if the routing issue is with their ISP.
https://developers.google.com/speed/public-dns/docs/using
scroll down to "windows" section for the guide[/quote]
DNS wouldn't affect his ping to game servers AT ALL
[quote=gemm]do 'ping -t www.google.com' in a cmd as admin. if it's still high then there's either a major routing problem or your line (to your house or neighbourhood) is congested[/quote]
You don't need to open cmd as an admin to ping anything and -t would only cause it to just keep pinging. This is useless.
What you should do is find out if your connection issue is specific to a certain locale (IE: Chicago servers? Dallas? New York?). Once you figure that out see if it's a specific server provider(s). If there's multiple you should do a tracert to a gameserver for each provider and see if there are any hops in common. Send that off to your ISP and show them your routing issue, and just-in-case send it off to a server provider and see if the routing issue is with their ISP.
-t does make it keep pinging and is useful because it helps you see a little about how your ping moves over time. doing it once is unreliable as the internet is unstable
just pinging google is of course not that reliable in itself, pinging lots of game servers is the best way. however since he has 150 to google, it's a fair assumption that the issue is close to him and not a problem with traffic routing causing congestion further down the line. traceroutes provide minimal help in this case
about admin, seems i got confused a little. a while ago i tried placing a .bat file on my desktop to ping -t google and it wouldn't recognise the command i think because my desktops on a different drive to my OS (and where the ping program is)
just pinging google is of course not that reliable in itself, pinging lots of game servers is the best way. however since he has 150 to google, it's a fair assumption that the issue is close to him and not a problem with traffic routing causing congestion further down the line. traceroutes provide minimal help in this case
about admin, seems i got confused a little. a while ago i tried placing a .bat file on my desktop to ping -t google and it wouldn't recognise the command i think because my desktops on a different drive to my OS (and where the ping program is)