Tracert's

**scuba_steve** · 03-04-08, 07:34 PM

check the gamerail thread, I have an tracert with it active there too ---- it didnt stop the choppyness. And I know its not my computer itself

**sjt17** · 03-04-08, 07:35 PM

Yeah - saw that, it sucks....

I guess with gamerail you have to be kinda close to the gamerail hub - I bet up where you are, the problem is you're just physically to far away -

Still, that hop you had with gamerail was still to long at 129? I'd bring that up with them.

**Braddoc** · 03-05-08, 10:45 AM

Originally Posted by scuba_steve

C:\Users\Gary>tracert 72.233.44.146

Tracing route to 146.44.233.72.static.reverse.ltdomains.com [72.233.44.146]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 21 ms 19 ms 20 ms 24.65.196.1
3 30 ms 19 ms * rc1ar-ge5-0-0-16.ed.shawcable.net [64.59.189.162]
4 134 ms 85 ms 76 ms rc1sc-pos11-0-0.wp.shawcable.net [66.163.77.189]
5 33 ms 42 ms 26 ms rc2nr-ge15-0-0.wp.shawcable.net [66.163.73.185]
6 55 ms 58 ms 50 ms rc2ch-pos7-0.il.shawcable.net [66.163.76.174]
7 51 ms 51 ms 61 ms rd2ec-pos1-0.il.shawcable.net [66.163.65.14]
8 77 ms 75 ms 54 ms eqix.chcg.twtelecom.net [206.223.119.36]
9 * * * Request timed out.
10 96 ms 73 ms 71 ms 209.163.157.254
11 79 ms 111 ms 65 ms 63.164.96.databank.com [63.164.96.58]
12 97 ms 144 ms 81 ms 63.164.96.databank.com [63.164.96.190]
13 79 ms 80 ms 88 ms 146.44.233.72.static.reverse.ltdomains.com [72.233.44.146]

Trace complete.

i see that you are missing a ping on your 3rd hop. this, from my perspective, is completely unacceptable. the first hop is your router/firewall (i assume), the second, should be the other side of your cable modem connection, and the third should be their first hop router towards the internet. hell, even the fourth hop has a large latency spike. there are a number of reasons why it wouldn't respond, but i'm thinking that there is a problem right on the other side of your cable connection.

scroll back a few pages to my post where i talk about how to ping a particular host about 300 times. this will give you good feeling where the problem is. basically, you want to find where you first see the problem. do the 5 minute (300 count) ping tests to the first few hops, starting with your router (hop 1), to try to determine where you are losing packets and having high latency. if it happens to be that you lose packets at hop 1, change out your network cable and try again. if it's with the first 3, i'd call the cable company and bitch, because something's definitely not right.

**Veovis** · 03-06-08, 11:38 AM

Just finished moving to Houston, finally got internet installed today.

WOO-FUCKING-HOO! Check this tracert:

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

1 * * * Request timed out.
2 8 ms 10 ms 6 ms ge-2-25-ur01.alvin.tx.houston.comcast.net [68.85
.248.89]
3 10 ms 11 ms 8 ms te-8-4-ar01.bearcreek.tx.houston.comcast.net [68
.85.244.65]
4 11 ms 21 ms 12 ms po-12-ar01.royalton.tx.houston.comcast.net [68.8
5.244.50]
5 13 ms 13 ms 14 ms po-11-ar02.royalton.tx.houston.comcast.net [68.8
5.244.98]
6 13 ms 12 ms 16 ms po-17-ar02.greenspoint.tx.houston.comcast.net [6
8.85.244.130]
7 * * 27 ms COMCAST-IP.edge3.Dallas1.Level3.net [4.71.198.14
]
8 28 ms 25 ms 18 ms xe-11-2-0.edge3.Dallas1.Level3.net [4.71.198.13]

9 * 18 ms 17 ms ae-13-69.car3.Dallas1.Level3.net [4.68.19.5]
10 19 ms 18 ms 19 ms level3-gw.dlstx.ip.att.net [192.205.34.137]
11 20 ms 21 ms 18 ms tbr1.dlstx.ip.att.net [12.122.86.206]
12 18 ms 19 ms 18 ms gar10.dlstx.ip.att.net [12.122.100.41]
13 21 ms 20 ms 21 ms 12.87.41.178
14 25 ms 20 ms 19 ms vlan905.core5.dfw1.rackspace.com [67.192.56.229]

15 20 ms 22 ms 19 ms 67.192.56.39
16 21 ms 20 ms 27 ms 151327-web1.texasteamplayers.com [67.192.131.130
]

Trace complete.

**CivilWars** · 03-06-08, 11:49 AM

Veovis,

Do you have an old one from FL? How much difference?

**Veovis** · 03-06-08, 11:57 AM

I never saved any, sorry. I think I usually pinged about 60 from there with a smooth route the whole way, but I can't be positive. Sorry again.

**CivilWars** · 03-06-08, 11:58 AM

No worries.

**scuba_steve** · 03-07-08, 03:09 PM

Originally Posted by Braddoc

Originally Posted by scuba_steve

C:\Users\Gary>tracert 72.233.44.146

Tracing route to 146.44.233.72.static.reverse.ltdomains.com [72.233.44.146]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.2.1
2 21 ms 19 ms 20 ms 24.65.196.1
3 30 ms 19 ms * rc1ar-ge5-0-0-16.ed.shawcable.net [64.59.189.162]
4 134 ms 85 ms 76 ms rc1sc-pos11-0-0.wp.shawcable.net [66.163.77.189]
5 33 ms 42 ms 26 ms rc2nr-ge15-0-0.wp.shawcable.net [66.163.73.185]
6 55 ms 58 ms 50 ms rc2ch-pos7-0.il.shawcable.net [66.163.76.174]
7 51 ms 51 ms 61 ms rd2ec-pos1-0.il.shawcable.net [66.163.65.14]
8 77 ms 75 ms 54 ms eqix.chcg.twtelecom.net [206.223.119.36]
9 * * * Request timed out.
10 96 ms 73 ms 71 ms 209.163.157.254
11 79 ms 111 ms 65 ms 63.164.96.databank.com [63.164.96.58]
12 97 ms 144 ms 81 ms 63.164.96.databank.com [63.164.96.190]
13 79 ms 80 ms 88 ms 146.44.233.72.static.reverse.ltdomains.com [72.233.44.146]

Trace complete.

i see that you are missing a ping on your 3rd hop. this, from my perspective, is completely unacceptable. the first hop is your router/firewall (i assume), the second, should be the other side of your cable modem connection, and the third should be their first hop router towards the internet. hell, even the fourth hop has a large latency spike. there are a number of reasons why it wouldn't respond, but i'm thinking that there is a problem right on the other side of your cable connection.

scroll back a few pages to my post where i talk about how to ping a particular host about 300 times. this will give you good feeling where the problem is. basically, you want to find where you first see the problem. do the 5 minute (300 count) ping tests to the first few hops, starting with your router (hop 1), to try to determine where you are losing packets and having high latency. if it happens to be that you lose packets at hop 1, change out your network cable and try again. if it's with the first 3, i'd call the cable company and bitch, because something's definitely not right.

heres the results from the 3rd hop - what does it mean/What do I do?

Ping statistics for 64.59.189.162:
Packets: Sent = 300, Received = 295, Lost = 5 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 7ms, Maximum = 2702ms, Average = 107ms

Most of the pings were low - then random spikes up to the 2000's and many random timeout's

Hop 4 - much of the same

Ping statistics for 66.163.77.189:
Packets: Sent = 300, Received = 297, Lost = 3 (1% loss),
Approximate round trip times in milli-seconds:
Minimum = 23ms, Maximum = 2793ms, Average = 85ms

**scuba_steve** · 03-07-08, 06:41 PM

I just got a new modem (They swapped mine for a new one for free) and my problem appears to be fixed for now

**Allane** · 03-08-08, 10:03 AM

Hm, I woke up early this morning, and hopped on the BF2 server for a bit of early gaming, and I found that my ping was exceedingly high. Yesterday, it was perfectly fine. Here's a tracert.

C:\Documents and Settings\Administrator>tracert 72.232.220.90

Tracing route to 90.220.232.72.static.reverse.ltdomains.com [72.232.220.90]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 * * * Request timed out.
3 8 ms 7 ms * ge-2-2-ur01.aurora.co.denver.comcast.net [68.86.
105.49]
4 9 ms 7 ms 7 ms te-8-3-ar01.aurora.co.denver.comcast.net [68.86.
103.37]
5 9 ms 9 ms 9 ms pos-0-15-0-0-cr01.denver.co.ibone.comcast.net [6
8.86.85.129]
6 * 53 ms 52 ms te-0-1-0-7-cr01.sanjose.ca.ibone.comcast.net [68
.86.84.125]
7 56 ms 57 ms 58 ms te-1-1-pr01.11greatoaks.ca.ibone.comcast.net [68
.86.84.126]
8 55 ms 55 ms 55 ms 68.86.88.250
9 * * * Request timed out.
10 194 ms * 195 ms 209.163.157.254
11 195 ms 194 ms * 63.164.96.databank.com [63.164.96.66]
12 206 ms * * lt-pod2a.lt.com [63.164.96.226]
13 * * * Request timed out.
14 194 ms 194 ms * 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]
15 197 ms 198 ms 196 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.
As you can see, I timed out in several places, and those that I didn't time out on, I had insanely high pings. I have done nothing to our connection, seeing as last night the ping was very much fine.