Tracert's

**Consultant** · 08-29-07, 03:04 PM

Originally Posted by ...bigdog...

that's complete shit.....but it's coming from the sprint link routers...not our california dream host ISP.

hmmmmm.

Sprint is complete shit, in general, from my experience with their "Business class" service.

I'll run another one when I get home. That'll be on Comcast gear.

**Consultant** · 08-29-07, 07:39 PM

here's one from my comcast connection

Tracing route to texasteamplayers.com [208.113.198.183]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms texasteamplayers.com [208.113.198.183]
2 6 ms 7 ms 6 ms 73.10.224.1
3 6 ms * 7 ms ge-2-2-ur01.etharpest.fl.tallah.comcast.net [68.
85.237.45]
4 6 ms * 15 ms te-8-1-ur01.pershingst.fl.tallah.comcast.net [68
.85.236.41]
5 7 ms * 7 ms te-8-1-ur01.capitalcircl.fl.tallah.comcast.net [
68.85.236.38]
6 6 ms * 9 ms te-9-2-ar02.tallahassee.fl.tallah.comcast.net [6
8.85.236.33]
7 7 ms 10 ms * 68.85.236.102
8 39 ms 39 ms 39 ms te-0-7-0-0-cr01.miami.fl.ibone.comcast.net [68.8
6.84.89]
9 43 ms 43 ms 41 ms 64.209.97.14
10 41 ms 41 ms 41 ms 64.209.97.13
11 73 ms 323 ms 207 ms 64.209.105.26
12 70 ms 72 ms 71 ms texasteamplayers.com [208.113.198.183]

Trace complete.

**Consultant** · 08-29-07, 07:41 PM

here's one to the CS Server...

are all the *'s why I can't seem to hit people when I aim at them?

Tracing route to a2.29.344a.static.theplanet.com [74.52.41.162]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms a2.29.344a.static.theplanet.com [74.52.41.162]
2 7 ms 7 ms 6 ms 73.10.224.1
3 9 ms * 6 ms ge-2-2-ur01.etharpest.fl.tallah.comcast.net [68.
85.237.45]
4 7 ms * 8 ms te-8-1-ur01.pershingst.fl.tallah.comcast.net [68
.85.236.41]
5 7 ms * 6 ms te-8-1-ur01.capitalcircl.fl.tallah.comcast.net [
68.85.236.38]
6 9 ms * 10 ms te-9-2-ar02.tallahassee.fl.tallah.comcast.net [6
8.85.236.33]
7 8 ms * 7 ms 68.85.236.102
8 39 ms 42 ms 39 ms te-0-7-0-0-cr01.miami.fl.ibone.comcast.net [68.8
6.84.89]
9 43 ms 62 ms 42 ms 64.209.107.54
10 45 ms 42 ms 42 ms 64.209.107.53
11 41 ms 43 ms 40 ms The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net
[64.208.170.198]
12 41 ms 54 ms 41 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

13 149 ms 207 ms 70 ms 72.fd.5746.static.theplanet.com [70.87.253.114]

14 43 ms 42 ms 41 ms vl1.car02.dllstx6.theplanet.com [12.96.160.23]
15 44 ms 39 ms 39 ms a2.29.344a.static.theplanet.com [74.52.41.162]

Trace complete.

**...bigdog...** · 08-29-07, 11:04 PM

perhaps. try doing a tracert several times in a row....see if it does it every time.

but none of those * are in things we can control. those are your ISP, and the hops it's taking to get to the game server.

**Braddoc** · 08-30-07, 10:03 AM

Originally Posted by Consultant

here's one to the CS Server...

are all the *'s why I can't seem to hit people when I aim at them?

Tracing route to a2.29.344a.static.theplanet.com [74.52.41.162]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms a2.29.344a.static.theplanet.com [74.52.41.162]
2 7 ms 7 ms 6 ms 73.10.224.1
3 9 ms * 6 ms ge-2-2-ur01.etharpest.fl.tallah.comcast.net [68.
85.237.45]
4 7 ms * 8 ms te-8-1-ur01.pershingst.fl.tallah.comcast.net [68
.85.236.41]
5 7 ms * 6 ms te-8-1-ur01.capitalcircl.fl.tallah.comcast.net [
68.85.236.38]
6 9 ms * 10 ms te-9-2-ar02.tallahassee.fl.tallah.comcast.net [6
8.85.236.33]
7 8 ms * 7 ms 68.85.236.102
8 39 ms 42 ms 39 ms te-0-7-0-0-cr01.miami.fl.ibone.comcast.net [68.8
6.84.89]
9 43 ms 62 ms 42 ms 64.209.107.54
10 45 ms 42 ms 42 ms 64.209.107.53
11 41 ms 43 ms 40 ms The-Planet.GigabitEthernet7-3.ar2.DAL2.gblx.net
[64.208.170.198]
12 41 ms 54 ms 41 ms te7-2.dsr01.dllstx3.theplanet.com [70.87.253.10]

13 149 ms 207 ms 70 ms 72.fd.5746.static.theplanet.com [70.87.253.114]

14 43 ms 42 ms 41 ms vl1.car02.dllstx6.theplanet.com [12.96.160.23]
15 44 ms 39 ms 39 ms a2.29.344a.static.theplanet.com [74.52.41.162]

Trace complete.

the * means that the icmp response (either a "time exceeded" or "echo reply" message) never made it back to your host in a reasonable amount of time (the default timeout). this can happen for a number of reasons. it /could/ mean that the packet got lost along the way, or it took too long to get back. but it could also be that that router (the one with the *) was too busy to send a response. some routers are set to only return ICMP responses when their network overhead is low.

tracert is a valuable tool for finding which hosts a packet travels to its final destination. it's NOT a valuable tool for determining the average round trip time for an ICMP echo request (a ping) to the final destination. the response times you see in a traceroute are the round trip time it took for your ping request to get to that host, that host decrements the TTL value by one, realizes that the TTL is now zero, discards that packet, generates an "ICMP time exceeded" packet and sends it back to you.

if you want to determine your average round trip time to the server, then ping the server directly. remember that you are sending data (by default 60 bytes, 32 bytes of data, and 28 bytes of IP + ICMP headers) to the server. this eats up others bandwidth, so don't abuse it. i suggest running a certain amount of pings (like 60) with 1 byte of data. this will give you an average of how long it takes the packets to get to the server once per second over a minute. here's the command:
>ping -n 60 -l 1 {hostname}

**3.89** · 09-18-07, 03:13 PM

here is mine! i hope i did it right!

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>
C:\Documents and Settings\Administrator>tracert 74.52.41.164:27017
Unable to resolve target system name 74.52.41.164:27017.

C:\Documents and Settings\Administrator>tracert www.texasteamplayers.com

Tracing route to www.texasteamplayers.com [208.113.198.183]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 129.62.100.1
2 <1 ms <1 ms <1 ms rfg2a-dmz.baylor.edu [129.62.201.34]
3 <1 ms <1 ms <1 ms 129.62.201.1
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.

C:\Documents and Settings\Administrator>

**...bigdog...** · 09-18-07, 03:21 PM

hey clown....how about you try doing it to the IP ADDRESS OF ONE OF OUR GAME SERVERS.

sigh....

**3.89** · 09-18-07, 03:25 PM

i did....clown.....it didnt work! i posted it in the other thread!

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert 74.52.41.164:27017
Unable to resolve target system name 74.52.41.164:27017.

C:\Documents and Settings\Administrator>

there