[G] Simple Ping Test CMD file

Vrtigo

Australia31 Posts

July 22 2013 01:16 GMT

Hi TL,

This is by no means anything exciting or new but something that I have found useful and would like to share. It is simply a CMD file that will ping all 4 of the SC2 battle.net servers in succession so that you can check your ping before deciding on a server to log in to.

I only made this because, living in Australia, I play on multiple servers. While the SEA server is okay for 1v1, depending on the time of day you can wait up to an hour in queue for team games. Unfortunately, internet in my area is pretty bad and pings to KR, NA and EU can be anywhere from 175 to 480 ms depending on internet load and time of day. I became annoyed by having to manually ping each server individually so made a CMD file to do it for me.

I decided to share this because I often see people asking how to check their latency and I am sure there are many other server-hopping people out there like myself.

To make this work simply copy the text in the spoiler tag below into notepad (or similar), click on File --> Save As --> File name: Pingtest.cmd --> Save as type: All Files --> click SAVE. Then, simply double click to see your ping. Your ping to each server is the line BEFORE the * * * that will appear when the hop times out.

+ Show Spoiler +

CD\
ECHO OFF
CLS
ECHO Testing Ping to battle.net servers in: Korea, SEA, NA and EU
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO KOREA server
tracert 211.234.110.1
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO SEA server
tracert 202.9.67.254
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO NA server 1/2
tracert 12.129.202.154
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO NA server 2/2
tracert 63.240.104.93
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO EU server 1/2
tracert 195.12.232.102
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO EU server 2/2
tracert 195.12.232.70
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO Ping test is complete. Press any key to exit.
PAUSE

NB:
1) Feel free to re-organise the file so that it pings servers closer to you first; it can take a while to sequentially ping ALL battle.net servers
2) If you only want to ping the first few servers simply press "pause" when you have had enough and scroll up to see the results. If you do not pause it will continually jump to the bottom as new pings are received.

I hope some of you find this useful.

GL HF!

-Vrtigo

EDIT: Changed the CMD file to ping the actual battle.net game servers and not the battle.net websites as it previously did. Thanks to both R1CH and qwyn for pointing that out to me.

Taefox

1533 Posts

July 22 2013 01:21 GMT

Very useful stuff for me as well ^_^ Thanks a lot

voss

Australia146 Posts

July 22 2013 02:31 GMT

Thanks for this,
just used it and found that my SEA ping is about the same as NA

BlackPanther

United States872 Posts

July 22 2013 02:34 GMT

YESSSSSSSSSSSSSSSSSSSSSSSSSSSSS!!!!!!!!!!!

Thank you sir!

Mahanaim

Korea (South)1002 Posts

July 22 2013 03:14 GMT

Let's try!
Thanks!

Fuchsteufelswild

Australia2028 Posts

July 22 2013 03:20 GMT

So what do I do if the only result I get is for SEA and all other requests (including trying to trace the SEA server) fail?
+ Show Spoiler +

KOREA server

Tracing route to kr.logon.battle.net [121.254.200.130]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * 214 ms 219 ms 1.213.105.245
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

NA server

Tracing route to us.battle.net [12.129.242.40]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

EU server

Tracing route to eu.battle.net [80.239.186.40]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

SEA server

Tracing route to sea.battle.net [202.9.66.38]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

Ping test is complete. Press any key to exit.
Press any key to continue . . .

R1CH

Netherlands10341 Posts

July 22 2013 03:32 GMT

This just measures the time to their webservers which are not in the same place as the game servers.

Qwyn

United States2779 Posts

July 22 2013 04:14 GMT

Lol, I was going to tell you that you're tracing to their webservers and then I scroll down and R1CH already posted it.

Vrtigo

Australia31 Posts

July 22 2013 07:35 GMT

Argh darn, guess I was misinformed by the articles I read on how to ping servers. I have found I.P. addresses for Blizzard SC2 servers HERE so if I replace the web domains with those I.P. addresses then it should work as intended?

If so I will alter the text tomorrow for those who would find it helpful. I am assuming with 2 servers in both NA and EU you would automatically be connected to the one with the lowest ping?

Thanks,

-Vrtigo

Vrtigo

Australia31 Posts

July 24 2013 08:30 GMT

#10

Have fixed the original post to go to actual gamer servers as opposed to webservers.

Does anyone know how SC2 decides which of the two EU / NA servers you get connected to? Is it based on ping or location?

Garnet

Vietnam9033 Posts

July 27 2013 01:59 GMT

#11

If I want to ping to the Dota 2 servers, do I just replace the IP adresses?

Ragnarork

France9034 Posts

July 27 2013 09:57 GMT

#12

On July 27 2013 10:59 Garnet wrote:
If I want to ping to the Dota 2 servers, do I just replace the IP adresses?

Assuming you find their gameserver's IP adress, yep.

A simple way to do that would be I think to start DotA, launch a game, and then start a cmd.exe in administrator mode.

Then, type "netstat -b" and look for the entries annotated dota.exe and "ESTABLISHED". IP adress would be in the 3rd column.

Complain

Israel29 Posts

July 27 2013 10:18 GMT

#13

when i open up the pingtest it says below every server : "tracert is not recognized as an internal or external command,operable program or batch file".

help please :D

edit: tried to run as an admin , same error.

Proseat

Germany5113 Posts

July 27 2013 15:54 GMT

#14

On July 27 2013 19:18 Complain wrote:
when i open up the pingtest it says below every server : "tracert is not recognized as an internal or external command,operable program or batch file".

help please :D

edit: tried to run as an admin , same error.

What Windows version are you on? Home or Pro? Maybe a PATH variable problem.

You could always use a free tool like the following instead. Just put each IP in the Host field and press Start, ping values are in the last four columns (Best, Avrg, Worst, Last).

http://winmtr.net/how-to/

Results for me from Berlin on Kabel D:

KR: 259 Best / 270 Avrg
SEA: 358 Best / 367 Avrg
NA1: 170 Best / 175 Avrg
NA2: 121 Best / 127 Avrg
EU1: 23 Best / 27 Avrg
EU2: 33 Best / 42 Avrg

Shield

Bulgaria4824 Posts

July 27 2013 17:11 GMT

#15

This may help you: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_programs/tracert-is-not-recognised-as-an-internal-or/c8559ce6-122b-4d46-8d62-b266c1911f05?msgId=d1fbe781-11d0-4020-a991-5137aa21d6d1

Anyway, here's a revised script based on OP's one. Differences? Servers are stored as variables at the beginning, so it's easier to keep IPs up-to-date. Some spaces between servers. Nothing functional is changed, only readability.

+ Show Spoiler +


CD\
ECHO OFF

:: Server IPs stored as variables
SET KOREA_SERVER=211.234.110.1
SET SEA_SERVER=202.9.67.254
SET NA_SERVER1=12.129.202.154
SET NA_SERVER2=63.240.104.93
SET EU_SERVER1=195.12.232.102
SET EU_SERVER2=195.12.232.70
::

CLS

ECHO Testing Ping to battle.net servers in: Korea, SEA, NA and EU
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.

ECHO KOREA server
tracert %KOREA_SERVER%
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.

ECHO SEA server
tracert %SEA_SERVER%
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.

ECHO NA server 1/2
tracert %NA_SERVER1%
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.

ECHO NA server 2/2
tracert %NA_SERVER2%
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.

ECHO EU server 1/2
tracert %EU_SERVER1%
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.

ECHO EU server 2/2
tracert %EU_SERVER2%
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.
ECHO.

ECHO Ping test is complete. Press any key to exit.
PAUSE

Yrr

Germany804 Posts

July 27 2013 18:09 GMT

#16

Works great, thx.

I have 60ms to EU, 200 to AM and 500 to KR from the south of Germany.
While AM is playable KR is definitely not.

( bush

321 Posts

July 27 2013 18:25 GMT

#17

Results are kinda sad for me ;/

350 ms to Korea, 400 to SEA, 200 to AM and 250 to EU
T_T

effecto

France142 Posts

July 27 2013 18:29 GMT

#18

Didn't know that, ver cool thank you !

Executerror

New Zealand28 Posts

July 27 2013 18:57 GMT

#19

Thanks for the script. Once it's pinging into asterisk, you can press Ctrl+C and reply "n" to Terminate batch job (Y/N)? This will save your time. From NZ ping. SEA 155ms, KR 204ms, NA 224/250ms, EU 335/344ms. Cheers.

Garnet

Vietnam9033 Posts

July 29 2013 23:45 GMT

#20

On July 27 2013 18:57 Ragnarork wrote:

Show nested quote +

are "hg-in-f113:http" and "hkg03s16-in-f5:https" IP addresses? Cause that's what it shows for "dota.exe".

Shield

Bulgaria4824 Posts

July 30 2013 00:07 GMT

#21

On July 30 2013 08:45 Garnet wrote:

Show nested quote +

are "hg-in-f113:http" and "hkg03s16-in-f5:https" IP addresses? Cause that's what it shows for "dota.exe".

Nope. IP addresses are numerical, at least IPv4 which we use now. So if you don't want to get confused, just remember for now that IP looks like 205.134.165.10. Maximum integer can be 255. Minimum is 0.

To get your external IP, just open this website: http://cmyip.com/
It will tell you what your IP is so you can have a better idea how an IP looks like.

R1CH

Netherlands10341 Posts

July 30 2013 14:33 GMT

#22

Dota uses UDP, so it won't show in netstat.

maxi0wnz

Australia1 Post

August 19 2013 10:19 GMT

#23

So can someone explain how this works? Im getting alot of request timed outs, but don't have ping issues on sea/kr (Havent tried NA/EU) as i live in Australia (Using IINET living in Central Queensland if anyone's interested)

+ Show Spoiler +

Testing Ping to battle.net servers in: Korea, SEA, NA and EU

KOREA server

Tracing route to 211.234.110.1 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 29 ms 28 ms 38 ms nexthop.qld.iinet.net.au [203.215.9.250]
3 28 ms 27 ms 29 ms ae7.cr1.bne4.on.ii.net [150.101.33.158]
4 67 ms 46 ms 45 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
5 189 ms 186 ms 190 ms te0-0-0.bdr2.nrt1.on.ii.net [203.16.211.58]
6 190 ms 189 ms 189 ms pos0-3-0.bdr1.hkg2.on.ii.net [203.16.211.6]
7 193 ms 195 ms 192 ms lg-RGE.hkix.net [202.40.160.240]
8 227 ms 226 ms 228 ms 1.208.147.165
9 203 ms 203 ms 204 ms 61.43.224.210
10 202 ms 202 ms 202 ms 1.208.105.245
11 213 ms 202 ms 205 ms 211.233.95.58
12 199 ms 201 ms 204 ms 211.172.248.82
13 * * * Request timed out.
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.

Trace complete.

SEA server

Tracing route to 202.9.67.254 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 46 ms 89 ms 119 ms nexthop.qld.iinet.net.au [203.215.9.250]
3 65 ms 77 ms 83 ms ae7.cr1.bne4.on.ii.net [150.101.33.158]
4 50 ms 59 ms 66 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
5 58 ms 53 ms 54 ms ae3.cr1.mel8.on.ii.net [150.101.33.27]
6 54 ms 65 ms 54 ms ae0.cr1.mel4.on.ii.net [150.101.33.10]
7 65 ms 74 ms 107 ms ae1.cr1.adl2.on.ii.net [150.101.33.41]
8 124 ms 99 ms 93 ms ae2.cr1.per2.on.ii.net [150.101.33.39]
9 105 ms 99 ms 158 ms ae0.cr1.per1.on.ii.net [150.101.33.12]
10 148 ms 139 ms 141 ms te0-3-0.cor1.per1.on.ii.net [150.101.33.99]
11 157 ms 140 ms 140 ms po0-3-0.bdr1.sin1.on.ii.net [203.16.211.229]
12 * 55497.sgw.equinix.com [202.79.197.79] reports: Destination net un
reachable.

Trace complete.

NA server 1/2

Tracing route to 12.129.202.154 over a maximum of 30 hops

1 <1 ms 2 ms 1 ms 192.168.0.1
2 27 ms 27 ms 27 ms nexthop.qld.iinet.net.au [203.215.9.250]
3 * 28 ms 26 ms ae7.cr1.bne4.on.ii.net [150.101.33.158]
4 117 ms 75 ms 70 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
5 193 ms 195 ms 194 ms te0-1-1-2.bd1.lax1.on.ii.net [203.16.213.65]
6 191 ms 189 ms 189 ms sl-st30-la-.sprintlink.net [144.223.30.1]
7 189 ms 189 ms 201 ms 144.232.4.129
8 221 ms 219 ms 222 ms 192.205.32.145
9 228 ms 270 ms 289 ms cr2.la2ca.ip.att.net [12.123.30.190]
10 233 ms 193 ms 208 ms gar29.la2ca.ip.att.net [12.122.129.241]
11 276 ms 224 ms 203 ms 12.122.251.190
12 190 ms 230 ms 192 ms 206.16.68.46
13 * * * Request timed out.
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.

Trace complete.

NA server 2/2

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.0.1
2 28 ms 29 ms 80 ms nexthop.qld.iinet.net.au [203.215.9.250]
3 29 ms 28 ms 31 ms ae7.cr1.bne4.on.ii.net [150.101.33.158]
4 46 ms 46 ms 46 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
5 203 ms 194 ms 193 ms te0-0-0-1.br1.lax1.on.ii.net [203.16.213.69]
6 193 ms 193 ms 266 ms sl-st30-la-.sprintlink.net [144.223.30.1]
7 234 ms 259 ms 190 ms 144.232.4.129
8 225 ms 223 ms 223 ms 192.205.32.145
9 261 ms 261 ms 275 ms cr1.la2ca.ip.att.net [12.123.30.18]
10 261 ms 260 ms 259 ms cr1.slkut.ip.att.net [12.122.30.29]
11 315 ms 290 ms 267 ms cr2.dvmco.ip.att.net [12.122.30.26]
12 277 ms 263 ms 264 ms cr1.cgcil.ip.att.net [12.122.31.86]
13 573 ms 739 ms 272 ms cr2.cgcil.ip.att.net [12.122.2.54]
14 270 ms 266 ms 268 ms cr1.n54ny.ip.att.net [12.122.1.1]
15 285 ms 286 ms 286 ms gar1.nw2nj.ip.att.net [12.122.131.81]
16 257 ms 258 ms 257 ms 12.122.251.6
17 258 ms 259 ms 263 ms mdf001c7613r0003-gig-12-1.nyc3.attens.net [63.24
0.65.22]
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.

Trace complete.

EU server 1/2

Tracing route to 195-12-232-102.customer.teliacarrier.com [195.12.232.102]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 25 ms 26 ms 28 ms nexthop.qld.iinet.net.au [203.215.9.250]
3 27 ms 26 ms 26 ms ae7.cr1.bne4.on.ii.net [150.101.33.158]
4 46 ms 47 ms 44 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
5 * 376 ms 245 ms te0-1-1-2.br2.lax1.on.ii.net [203.16.213.190]
6 192 ms 194 ms 193 ms las-bb1-link.telia.net [62.115.33.121]
7 284 ms 283 ms 286 ms ash-bb3-link.telia.net [80.91.251.253]
8 378 ms 349 ms 352 ms ffm-bb1-link.telia.net [80.91.246.59]
9 352 ms 352 ms 353 ms ffm-b10-link.telia.net [80.91.247.185]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

EU server 2/2

Tracing route to 195-12-232-70.customer.teliacarrier.com [195.12.232.70]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 30 ms 27 ms 28 ms nexthop.qld.iinet.net.au [203.215.9.250]
3 27 ms 27 ms 28 ms ae7.cr1.bne4.on.ii.net [150.101.33.158]
4 46 ms 53 ms 45 ms ae1.br1.syd4.on.ii.net [150.101.33.18]
5 223 ms 198 ms 193 ms te0-1-1-2.br2.lax1.on.ii.net [203.16.213.190]
6 194 ms 196 ms 200 ms las-bb1-link.telia.net [62.115.33.121]
7 258 ms 252 ms 310 ms ash-bb3-link.telia.net [80.91.252.157]
8 346 ms 494 ms 347 ms prs-bb1-link.telia.net [80.91.251.99]
9 375 ms 375 ms 398 ms prs-b8-link.telia.net [213.155.132.225]
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

Ping test is complete. Press any key to exit.
Press any key to continue . . .

WonnaPlay

Netherlands912 Posts

August 19 2013 10:32 GMT

#24

On August 19 2013 19:19 maxi0wnz wrote:
So can someone explain how this works? Im getting alot of request timed outs, but don't have ping issues on sea/kr (Havent tried NA/EU) as i live in Australia (Using IINET living in Central Queensland if anyone's interested)

+ Show Spoiler +

Trace route will search for the server you are trying to access through all the steps needed for your connection to the requested server.
For example, you live in US and you want to traceroute to Europe.
The traceroute will look something like this (this is just an example) :
1 - route from your PC to your modem
2 - route from your modem to your webhost
3 - route from your webhost to a server in US
4 - route from the server in US to a server in EU
5 - route from the server in EU to the webhost of requested server
6 - route from the webhost of requested server to actual server*

By now you've reached the server you wanted to ping. Since no more steps are needed there is no more server to contact, which will result in all other entries to time out.
Traceroute goes over 30 hops by default, but you dont always need to make 30 hops.

7 - timeout
8 - timeout
9 - ""
etc.

Usually the further you have to go (distance), the more hops traceroute needs to make before reaching the destination server.

Edit :

Thought, i'd also mention this;

The last entry which will give a response is your actual ping to the server.
In your case this would be : KR server +-200ms , SEA server +-150 ms, EU server +-350 ms

Marou

Germany1371 Posts

August 19 2013 10:37 GMT

#25

Guys listen to R1CH, all of those methods are not giving you the ping you will have in game...

Marcinko

South Africa1014 Posts

August 19 2013 10:44 GMT

#26

You are my hero, been looking for something like this for a while.

Thank you.

yuuG

Malaysia23 Posts

August 21 2013 12:30 GMT

#27

what does it mean if i get something like this?

+ Show Spoiler +

Testing Ping to battle.net servers in: Korea, SEA, NA and EU

KOREA server

Tracing route to 211.234.110.1 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms l7router [192.168.0.1]
2 3 ms 4 ms 3 ms 115.132.110.178
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

SEA server

Tracing route to 202.9.67.254 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms l7router [192.168.0.1]
2 3 ms 5 ms 5 ms 115.132.110.178
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

NA server 1/2

Tracing route to 12.129.202.154 over a maximum of 30 hops

1 1 ms 1 ms 1 ms l7router [192.168.0.1]
2 4 ms 4 ms 3 ms 115.132.110.178
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
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.

Trace complete.

NA server 2/2

Tracing route to 63.240.104.93 over a maximum of 30 hops

1 <1 ms 1 ms 1 ms l7router [192.168.0.1]
2 5 ms 3 ms 3 ms 115.132.110.190
3 * * * Request timed out.
4 * * * Request timed out.
5 * *

doesn't seem right...

I'm from SEA with 9mb down/up

Doko

Argentina1737 Posts

August 21 2013 12:58 GMT

#28

Should do

tracert -d -w 1000 ip

-d = no need to resolve hostnames
-w 1000 = set timeout to 1000. anything above that it means its probably firewalled anyway.

DenTenker

United States606 Posts

August 21 2013 16:12 GMT

#29

Awesome! I always wondered what my pings were to the different servers. Thanks!

yuuG

Malaysia23 Posts

August 23 2013 09:09 GMT

#30

On August 21 2013 21:58 Doko wrote:
Should do

tracert -d -w 1000 ip

-d = no need to resolve hostnames
-w 1000 = set timeout to 1000. anything above that it means its probably firewalled anyway.

i tried that, still got the same thing

any ideas?

Doko

Argentina1737 Posts

August 23 2013 15:40 GMT

#31

On August 23 2013 18:09 yuuG wrote:

Show nested quote +

i tried that, still got the same thing

any ideas?

What I posed was not meant to fix your problem, it was just to speed up the trace.

It seems that after that 3rd jump the routers are just dropping the diagnostic packets. Unsure on your network configuration and I'm not that savy as to say what the problem might be.

grs

Germany2339 Posts

August 23 2013 15:47 GMT

#32

Ermh...this is so wrong in many regards.
1. Why do you do a "tracert" instead of a simple "ping" if you just want the ping time?
2. The Ping time to the server is *NOT* shown before the first * * * respeonse. The * * * response is just a server that denies ICMP packets (the protocol behind ping and tracert). --> Conclusion: You will not see the Ping time to Blizzard servers.
3. Even if you would get the command through w/o a single server denying ICMP, that is still not the same value as the ingame connection. You might get a conclusion out of it like higher = worse // lower = better, but that is the best you could get.

In the end: This is pointless and just sends people like the last posters on tech research that will not help him and just steals their time.

Nerdrage

United States55 Posts

September 13 2013 09:56 GMT

#33

Thanks for this, i did something similar using battle.net support tracert instructions. got the same results.

Do you know why the SEA server says destination net unreachable at about hop 7? Did they block it or something?

Garnet

Vietnam9033 Posts

August 21 2015 11:21 GMT

#34

can you make something like this for LOTV?