[G] Simple Ping Test CMD file - Page 2

Post a Reply

Prev 1 2 All

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

Netherlands10342 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

Vietnam9047 Posts

August 21 2015 11:21 GMT

#34

can you make something like this for LOTV?