tracert result on server

[Swaith]

http://img137.imageshack.us/f/tracertresult.jpg/

thats a tracert result for the server

[Swaith]

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\pete>/tracert 69.197.189.132
'/tracert' is not recognized as an internal or external command,
operable program or batch file.

C:\Users\pete>tracert 69.197.189.132

Tracing route to 69.197.189.132 over a maximum of 30 hops

1 41 ms 87 ms 11 ms [blocked]
2 26 ms 31 ms 14 ms nmal-geam-1a-ge91.network.virginmedia.net [81.96
.225.5]
3 29 ms 59 ms 14 ms croy-core-1a-pc111.network.virginmedia.net [62.3
0.242.37]
4 42 ms 11 ms 44 ms brnt-bb-1a-ae2-0.network.virginmedia.net [195.18
2.178.82]
5 11 ms 22 ms 11 ms nrth-bb-1b-as4-0.network.virginmedia.net [212.43
.162.218]
6 40 ms 39 ms 13 ms nrth-tmr-2-ae6-0.network.virginmedia.net [213.10
5.159.34]
7 13 ms 47 ms 14 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
8 24 ms 22 ms 16 ms 10gigabitethernet1-1.core1.lon1.he.net [195.66.2
24.21]
9 95 ms 98 ms 141 ms 10gigabitethernet4-4.core1.nyc4.he.net [72.52.92
.241]
10 121 ms 121 ms 132 ms 10gigabitethernet1-2.core1.chi1.he.net [72.52.92
.102]
11 144 ms 133 ms 147 ms 10gigabitethernet1-1.core1.mci1.he.net [72.52.92
.2]
12 191 ms 157 ms 146 ms 10gigabitethernet1-1.core1.mci2.he.net [184.105.
213.2]
13 137 ms 160 ms 154 ms wholesale-internet-inc.10gigabitethernet1-4.core
1.mci2.he.net [216.66.79.10]
14 144 ms 150 ms 129 ms 69.30.209.7
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.

C:\Users\pete>

--------

for reference

[FunkyGroove]

wait...what?

[bonehead]

Ok, so you know what path your packets take.... and? haha.

[wraith1200]

My packets take the same route and die at the same point.

[bonehead]

Well they should die at the same point... they shouldn't take the same route though, haha. Mine take the same route for about the second half of the trip, but the first half is all different in trying to get from College Station, TX to Dallas, TX.

I don't know what it is supposed to be showing me though other than the different routers I pass through.

[wraith1200]

What that is showing is it is losing connection when it shouldn't.

[bonehead]

How is it showing that? It seems to end up at the right place...

[wraith1200]

It is showing it because it shouldn't be timing out

[bonehead]

Sure it should. It traces the packets up to a maximum of 30 hops. If it only needs 13 hops to get to its destination, the remaining 17 will time out as the program waits for a response that isn't coming because the packet isn't moving anymore. The other possibility is that Xenon servers has their network set up to deny tracert and traceroute requests, so it times out as soon as it hits their actual router. Either way, it terminates in what appears to be Kansas City after bouncing around from server to server at Wholesale Internet, Inc. My guess is that Xenon just has tracert blocked because it can be used maliciously.

[Swaith]

sorry thats incorrect a correct tracert should end at its destination IP it only shows the first 30 jumps because it really shouldnt take any more then that, what this shows is that somwere along the way the packets hit a wall of timeout and essentially take longer then 1000 m/s to get across or in the case above completely drop out, the lag we are all hitting is coming from this horrendous packet loss. essentialy it means instead of like 13 jumps of 13-50 ms which makes roughly half a second for a server reply its taking well OVER a full second, 30 x 1000 ms is around 30 seconds or something, on a game this slaughters it, il show you one for google one moment

[Swaith]

Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

tracert www.google.com

Tracing route to www.l.google.com [173.194.37.104]
over a maximum of 30 hops:

1 33 ms 11 ms 43 ms [Blocked]
2 58 ms 12 ms 31 ms nmal-geam-1a-ge91.network.virginmedia.net [81.96
.225.5]
3 28 ms 19 ms 31 ms croy-core-1a-pc111.network.virginmedia.net [62.3
0.242.37]
4 9 ms 10 ms 9 ms brnt-bb-1a-ae2-0.network.virginmedia.net [195.18
2.178.82]
5 87 ms 17 ms 16 ms manc-bb-1b-as5-0.network.virginmedia.net [62.252
.192.90]
6 23 ms 24 ms 45 ms tele-ic-3-ae0-0.network.virginmedia.net [212.43.
163.70]
7 39 ms 23 ms 21 ms 162-14-250-212.static.virginmedia.com [212.250.1
4.162]
8 21 ms 20 ms 57 ms 209.85.252.76
9 37 ms 62 ms 18 ms 209.85.251.58
10 47 ms 20 ms 20 ms lhr14s02-in-f104.1e100.net [173.194.37.104]

Trace complete.

tracert www.google.co.uk

Tracing route to www.l.google.com [173.194.37.104]
over a maximum of 30 hops:

1 8 ms 18 ms 38 ms [Blocked]
2 14 ms 11 ms 30 ms nmal-geam-1a-ge91.network.virginmedia.net [81.96
.225.5]
3 20 ms 33 ms 33 ms croy-core-1a-pc111.network.virginmedia.net [62.3
0.242.37]
4 35 ms 64 ms 11 ms brnt-bb-1a-ae2-0.network.virginmedia.net [195.18
2.178.82]
5 43 ms 87 ms 19 ms manc-bb-1b-as5-0.network.virginmedia.net [62.252
.192.90]
6 47 ms 49 ms 39 ms tele-ic-3-ae0-0.network.virginmedia.net [212.43.
163.70]
7 39 ms 23 ms 49 ms 162-14-250-212.static.virginmedia.com [212.250.1
4.162]
8 47 ms 55 ms 39 ms 209.85.252.76
9 17 ms 35 ms 44 ms 209.85.251.58
10 128 ms 51 ms 41 ms lhr14s02-in-f104.1e100.net [173.194.37.104]

Trace complete.



there you go, see 10 jumps to a .com address from the uk and its around 10-40 ms per jump thats 400ms at worse, well under half a second. it takes longer for me ironically to get to .co.uk

gota run but there you go

[bonehead]

Right. But it isn't necessarily packet loss either, as it very well could be that as soon as it reaches the server company the request times out because they deny tracert requests. There are definitely people who do that. It may be worthwhile to ask the company if they do that and if not, see if they have any ideas as to why we seem to all have the same problems.

[Swaith]

its possible to deny tracerout requests but not over so many jumps unless they own have a countrys jumps, if the last one times out i can understand but for it to drop out on the same location mid jump and timeout without resolution is quite suspect i mean of course it could be the case dont get me wrong but for about 15 jumps to all do that on a regular tracert on a public server connection is a tad strange, particularly when that dissables all requested traffic and would dissable any connections not using a server specific ID and port no.

either way its just an example :D i didnt realise you were familiar with it, its something that i find a rare few interested enough in to look up ^^

as a pass time for instance were having a debate at my house as to what the opposite of thirsty is, without looking it up whats your take? i knows its off topic but its plaguing me, the closest we have is hydrated but then i figure thats wrong as hydrated's opposite is de-hydrated isnt it?

-----EDIT-----

hate to eat humble pie, but looking at a more tailored tracert you may very well be right

my custom tracert of 200 jumps for 2000 m/s timout ends on an ip that when looked up ends in kansas city

69.30.209.7 US UNITED STATES MISSOURI KANSAS CITY WHOLESALE INTERNET INC

which i assume is the host, so you may very well be correct and it may not be packet loss, even though i have epic time on my tracert near 1000 m/s per packet

i bow to your tracert wisedom :D

[bonehead]

I wouldn't christen me correct yet. I am not an expert, I just wanted to make sure we weren't jumping to conclusions. There was more than one possible explanation, so I wanted to make sure we didn't just assume one of them to be correct. If I turned out to be right, it was more out of luck.

[CannonFodderTed]

Ill be honest... I got halfway through this thread and I stopped reading because the nerd level went way over my head.

0.o

[Swaith]

Lol no worries cannon, essentially to get from your computer to a server the data is sent bundled up in whats refered to as packets. these packets get passed from connection to connection until they hit their destination. what you see above is a packet with a tracer on it.

it simply sends my computer a responce when it reaches each different server it jumps with. telling me how long it took to get there, how long its 3 burst shot responce took to get to me, the server's IP address (which in tandem with websites can tell you the server location) and how many jumps it needs to make to get somewhere

normal results hit 30-40 m/s a response and average out in my country between 6-10 jumps

this packet got lost in kansas and stopped responding was what i was telling him,

[animeaxe]

I rarely use a simple tracert anymore because most companies with any security concerns block tracert requests these days.

If you really wanted to try to get a more definitive answer to the question you seem to asking you could try spoofing a trusted IP, but I'm not even going to begin speculating on where you'd get one for Xenon or wherever the tracert stops.

[Swaith]

wow necro ;D this thread was to help find the issue as to why the service stopped where it wasnt supposed to, it turns out it wasnt the problem but wth, as for the tracert it landed in the same area as the server was alleged to be so we thought it relevant for a tad, i know most servers block tracerts but with a custom one you can still get thru, for instance simply monitoring a true game packet as its sent and following the results give the same sort of thing but that requires decompiling encrypted packets and monitoring em, something i presume would autoban me from every minecraft server :D