Sometimes tracert completes, sometimes I get this.

Hey Failure,

Mines 192.168


Tracing route to fragmaster.net [85.114.140.116]
over a maximum of 30 hops:

1 * * * Request timed out.
2 26 ms 27 ms 25 ms loopbacl100.sclarbras08.hay.connect.com.au [210.
8.1.241]
3 25 ms 26 ms 26 ms ge9-1.sclardist02.aapt.net.au [202.10.13.10]
4 26 ms 26 ms 26 ms te3-1.sclarbrdr01.aapt.net.au [202.10.14.5]
5 81 ms 81 ms 81 ms xe7-0-0-320.sybr5.global-gateway.net.nz [202.50.
238.213]
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 235 ms 233 ms 236 ms ge-1-7.r00.lsanca19.us.bb.gin.ntt.net [204.1.253
.49]
10 223 ms 223 ms 240 ms ae-4.r21.lsanca03.us.bb.gin.ntt.net [129.250.6.4
1]
11 287 ms 289 ms 292 ms as-2.r20.asbnva02.us.bb.gin.ntt.net [129.250.5.2
5]
12 294 ms 296 ms 289 ms ae-3.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.1
28]
13 386 ms 387 ms 384 ms as-0.r23.amstnl02.nl.bb.gin.ntt.net [129.250.2.1
59]
14 399 ms 400 ms 400 ms p64-3-0-0.r21.frnkge03.de.bb.gin.ntt.net [129.25
0.3.48]
15 408 ms 412 ms 413 ms xe-3-1.r01.frnkge03.de.bb.gin.ntt.net [129.250.2
.13]
16 400 ms 403 ms 387 ms arcor-1.r01.frnkge03.de.bb.gin.ntt.net [213.198.
72.166]
17 376 ms 389 ms 389 ms ffm-145-254-16-65.arcor-ip.net [145.254.16.65]
18 406 ms 401 ms 402 ms kln-145-254-9-214.arcor-ip.net [145.254.9.214]
19 399 ms 397 ms 396 ms trgw-vodafone-10gig.dus1-de.fibre1.net [92.79.23
9.174]
20 418 ms 414 ms 405 ms lcgw-10g-fdip1.dus2-de.fibre1.net [62.141.47.130
]
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * *

arrow karts, that is your local IP address, he needs your internet one. try www.myipaddress.com and post that one instead
if i'm blocked today, ill post another tracert when i get home tonight!

Omg lol. useless......

ok so its 59.101

Quote from Arrow Karts 8 :

ok so its 59.101

Allright,
that range was formerly assigned to india, apparently it has been re-assigned to Australia.
I fixed that, you now should be able to connect.
The others, well, I need more tracert results please since the posted IP ranges are not being blocked.
Shadoww, when an IP range is being blocked, a tracert will never complete, so in your case it must be something else.

both times i have tried and both times i have been able to connect heh. ill try each day since you changed that setting Failure. maybe that could be it for a few of us who were getting IP changes.

Cheers Failure!! Was on yesterday no issues

have tried everyday since this setting was changed and im safe to say i can connect and see the servers 24/7 now. thankyou so much, this frustration is over now off to race, BIG THANKS AGAIN!! =D

Quote from FM-Failure :

Shadoww, when an IP range is being blocked, a tracert will never complete, so in your case it must be something else.

I have no idea what this could change, but after switching from ISP's DNS to OpenDNS everything works again.