test content
Logo
What is the Arc Client?
Install Arc
can not contact nettest server
lunarisy
Member Posts: 0 Arc User
Its been a week since i can not contact net test server. Is there any IP block?
Post edited by lunarisy on
0
lunarisy
Member Posts: 0 Arc User
Comments
What are the results when you do the traceroute?
You may need to contact your ISP as they may have it blocked for some reason. We should know more when you answer those two questions though.
contacting nettest server..timed out
hit return to exit
any specifict address for me to trace route?
I contacted my ISP and they haven't block anything.
If you can;t reach it, they very well may have.
From a command prompt, can you try the following two commands please:
ping 208.95.185.41
tracert 208.95.185.41
That number is what's known as the IP address for the patch server.
ping 208.95.185.41
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 208.85.185.41:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
tracert 208.95.185.41
1 <1 ms <1 ms <1 ms 192.168.1.1
2 24 ms 23 ms 25 ms 1.static.118-96-160.astinet.telkom.net.id [118.96.160.1]
3 24 ms 23 ms 25 ms 209.subnet125-160-11.speedy.telkom.net.id [125.160.11.209]
4 23 ms 23 ms 25 ms 61.94.114.121
5 74 ms 57 ms 59 ms 41.subnet118-98-59.astinet.telkom.net.id [118.98.59.41]
6 51 ms 53 ms 51 ms 42.subnet118-98-59.astinet.telkom.net.id [118.98.59.42]
7 87 ms 165 ms 85 ms 203.208.131.89
8 84 ms 87 ms 85 ms 203.208.166.61
9 250 ms 245 ms 267 ms so-2-0-3-0.plapx-cr3.ix.singtel.com [203.208.149.58]
10 247 ms 225 ms 231 ms POS4-0-0.access1.ix.singtel.com [203.208.182.214]
11 243 ms 239 ms 235 ms te4-8.ccr02.sjc04.atlas.cogentco.com [154.54.10.169]
12 237 ms 239 ms 243 ms te0-0-0-6.ccr22.sfo01.atlas.cogentco.com [154.54.0.177]
13 284 ms 289 ms 285 ms te0-4-0-6.ccr22.mci01.atlas.cogentco.com [154.54.45.73]
14 288 ms 287 ms 285 ms te0-5-0-4.ccr22.ord01.atlas.cogentco.com [154.54.45.150]
15 313 ms 311 ms 321 ms te0-2-0-5.ccr22.bos01.atlas.cogentco.com [154.54.43.74]
16 * * 317 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
17 326 ms 325 ms 321 ms 38.111.40.114
18 318 ms 319 ms 317 ms 208.95.185.41
hit return to exit
somehow i can ping the server now
Pinging 208.95.185.41 with 32 bytes of data:
Reply from 208.95.185.41: bytes=32 time=343ms TTL=47
Reply from 208.95.185.41: bytes=32 time=326ms TTL=47
Reply from 208.95.185.41: bytes=32 time=332ms TTL=47
Reply from 208.95.185.41: bytes=32 time=348ms TTL=47
Ping statistics for 208.95.185.41:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 326ms, Maximum = 348ms, Average = 337ms
Tracing route to 208.95.185.41 over a maximum of 30 hops
1 13 ms <1 ms <1 ms 192.168.1.1
2 26 ms 25 ms 23 ms 1.static.118-96-160.astinet.telkom.net.id [118.96.160.1]
3 24 ms 27 ms 25 ms 209.subnet125-160-11.speedy.telkom.net.id[125.160.11.209]
4 23 ms 21 ms 24 ms 61.94.114.121
5 59 ms 60 ms 58 ms 41.subnet118-98-59.astinet.telkom.net.id [118.98.59.41]
6 50 ms 56 ms 53 ms 42.subnet118-98-59.astinet.telkom.net.id [118.98.59.42]
7 93 ms 87 ms 85 ms 203.208.131.89
8 88 ms 85 ms 83 ms 203.208.166.161
9 245 ms 227 ms 226 ms 203.208.172.226
10 247 ms 249 ms 247 ms 203.208.154.178
11 238 ms 237 ms 261 ms te4-8.ccr02.sjc04.atlas.cogentco.com [154.54.10.169]
12 247 ms 259 ms 249 ms te0-0-0-6.ccr22.sfo01.atlas.cogentco.com [154.54.0.177]
13 292 ms 311 ms 285 ms te0-4-0-6.ccr22.mci01.atlas.cogentco.com [154.54.45.73]
14 300 ms 313 ms 301 ms te0-5-0-4.ccr22.ord01.atlas.cogentco.com[154.54.45.150]
15 316 ms 341 ms 355 ms te0-2-0-5.ccr22.bos01.atlas.cogentco.com [154.54.43.74]
16 323 ms 345 ms 341 ms te4-2.ccr01.bos06.atlas.cogentco.com [66.28.4.254]
17 342 ms 321 ms 314 ms 38.111.40.114
18 317 ms 341 ms 354 ms 208.95.185.41
Trace complete.