Tracert's

**Braddoc** · 03-23-10, 02:38 AM

digital...

forget every other hop along the way. looking at your last hop, (the most important one), you are getting awesome response times. trace route is a funny cat, because the packet is actually dropped, then re-created by that router, and sent back to the host. the router's PRIMARY job is to ROUTE. responding to an ICMP TTL Exceeded message is secondary. therefore, any other router along that path may respond with higher response times than a normal packet would traverse the path in.

on a side note, an in-game ping of 25-32 is LOW. there is no reason for you to be having problems with that low of a ping time in-game. check for other things that are pegging your CPU. it's still possible that it would be on the server side, but usually, the server controllers would receive many complaints about the lag. not just one person.

good luck.

**digital** · 03-23-10, 07:47 AM

my ping last night on conquest server 1 & 2 was hovering between 300 to 500ms ping.

**Captain Coors** · 03-25-10, 08:47 PM

I could sure use some advice with my tracert to the sourcebox. The past week my ping jumped up 30ms because of hop 11 below, and I'm not sure why and if I can do anything about it.

My tracerts to the other dallas servers like the l4d2 and bc2 box are fine as normal....60 ping compared to 90ish for source, which used to be 60s.

Thanks

SOURCE:

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.1.1
2 * * * Request timed out.
3 7 ms 10 ms 7 ms ge-1-11-ur01.pimaco.az.pima.comcast.net [68.86.2
01.41]
4 8 ms 6 ms 7 ms te-8-1-ar01.pimaco.az.pima.comcast.net [68.87.17
2.1]
5 14 ms 13 ms 13 ms te-0-6-0-4-cr01.santateresa.tx.ibone.comcast.net
[68.86.91.33]
6 25 ms 25 ms 26 ms pos-1-8-0-0-cr01.losangeles.ca.ibone.comcast.net
[68.86.86.13]
7 26 ms 26 ms 26 ms xe-10-2-0.edge3.LosAngeles1.Level3.net [4.71.136
.5]
8 35 ms 36 ms 35 ms ae-72-70.ebr2.LosAngeles1.Level3.net [4.69.144.1
15]
9 66 ms 72 ms 71 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
10 60 ms 59 ms 59 ms ae-1-60.edge3.Dallas1.Level3.net [4.69.145.8]
11 93 ms 94 ms 94 ms DATABANK-HO.edge3.Dallas1.Level3.net [4.71.170.6
]
12 92 ms 94 ms 93 ms dbce10glt.layeredtech.com [66.18.0.142]
13 * * * Request timed out.
14 94 ms 93 ms 93 ms 146.44.233.72.static.reverse.ltdomains.com [72.2
33.44.146]

Trace complete.

L4D2 (Normal)

Tracing route to 66.150.221.85 over a maximum of 30 hops

1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 21 ms 9 ms 6 ms ge-1-11-ur01.pimaco.az.pima.comcast.net [68.86.2
01.41]
4 6 ms 6 ms 6 ms te-8-1-ar01.pimaco.az.pima.comcast.net [68.87.17
2.1]
5 14 ms 13 ms 14 ms te-0-6-0-4-cr01.santateresa.tx.ibone.comcast.net
[68.86.91.33]
6 35 ms 33 ms 35 ms pos-1-8-0-0-cr01.losangeles.ca.ibone.comcast.net
[68.86.86.13]
7 27 ms 29 ms 26 ms xe-11-1-0.edge3.LosAngeles1.Level3.net [63.208.2
31.125]
8 26 ms 32 ms 36 ms ae-82-80.ebr2.LosAngeles1.Level3.net [4.69.144.1
79]
9 61 ms 68 ms 71 ms ae-3-3.ebr3.Dallas1.Level3.net [4.69.132.78]
10 59 ms 92 ms 60 ms ae-1-60.edge2.Dallas3.Level3.net [4.69.145.12]
11 60 ms 59 ms 62 ms INTERNAP-NE.edge2.Dallas3.Level3.net [4.59.36.66
]
12 61 ms 59 ms 59 ms border1.ge4-1-bbnet2.ext1a.dal.pnap.net [216.52.
191.84]
13 59 ms 60 ms 61 ms 66.150.221.85

**Captain Coors** · 04-03-10, 05:41 PM

Bump - any takers on advice for me regarding my issue above?

I'm still having this weird 30ms jump on this dallas to dallas hop for the tf2 servers

10 60 ms 59 ms 59 ms ae-1-60.edge3.Dallas1.Level3.net [4.69.145.8]
11 93 ms 94 ms 94 ms DATABANK-HO.edge3.Dallas1.Level3.net [4.71.170.6]

Pinging normal to the other dallas servers, this tracert to the L4D servers is fine on the dallas to dallas hop.
10 59 ms 92 ms 60 ms ae-1-60.edge2.Dallas3.Level3.net [4.69.145.12]
11 60 ms 59 ms 62 ms INTERNAP-NE.edge2.Dallas3.Level3.net [4.59.36.66]

**space.cowboy** · 07-20-10, 09:03 PM

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

1 43 ms 3 ms 1 ms . [192.168.2.1]
2 * * * Request timed out.
3 42 ms 22 ms 17 ms 68-113-206-86.static.ftwo.tx.charter.com [68.113
.206.86]
4 20 ms 15 ms 9 ms bbr01ftwotx-tge-0-0-5-0.ftwo.tx.charter.com [96.
34.2.32]
5 31 ms 34 ms 13 ms so-6-1-0.edge4.Dallas1.Level3.net [4.71.216.25]

6 105 ms 16 ms 23 ms ae-2-70.edge3.Dallas1.Level3.net [4.69.145.72]
7 26 ms 20 ms 13 ms DATABANK-HO.edge3.Dallas1.Level3.net [4.71.170.6
]
8 143 ms 17 ms 16 ms dbce10glt.layeredtech.com [66.18.0.142]
9 * * * Request timed out.
10 * * * Request timed out.
11 20 ms 17 ms 11 ms 146.44.233.72.static.reverse.ltdomains.com [72.2
33.44.146]

This is after my internet was upgraded recently. Any suggestions?

**GReYVee** · 07-21-10, 03:05 PM

Originally Posted by space.cowboy

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

1 43 ms 3 ms 1 ms . [192.168.2.1]
2 * * * Request timed out.
3 42 ms 22 ms 17 ms 68-113-206-86.static.ftwo.tx.charter.com [68.113
.206.86]
4 20 ms 15 ms 9 ms bbr01ftwotx-tge-0-0-5-0.ftwo.tx.charter.com [96.
34.2.32]
5 31 ms 34 ms 13 ms so-6-1-0.edge4.Dallas1.Level3.net [4.71.216.25]

6 105 ms 16 ms 23 ms ae-2-70.edge3.Dallas1.Level3.net [4.69.145.72]
7 26 ms 20 ms 13 ms DATABANK-HO.edge3.Dallas1.Level3.net [4.71.170.6
]
8 143 ms 17 ms 16 ms dbce10glt.layeredtech.com [66.18.0.142]
9 * * * Request timed out.
10 * * * Request timed out.
11 20 ms 17 ms 11 ms 146.44.233.72.static.reverse.ltdomains.com [72.2
33.44.146]

This is after my internet was upgraded recently. Any suggestions?

First concern is the latency spike to your router. First hop should always be within the 1-2 ms range unless you are wireless.
43ms would account for the variance offnet and we need to start right there.

Let's start with a strong ping test

ping 192.168.2.1 -n 100 <-- router
ping 192.168.100.1 -n 100 <-- cable modem
ping 68.113.206.86 -n 100 <-- first public hop

this will at least tell us if your connection issue is fixable locally.

**space.cowboy** · 07-21-10, 03:39 PM

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Bryan>ping 192.168.2.1

Pinging 192.168.2.1 with 32 bytes of data:
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64
Reply from 192.168.2.1: bytes=32 time<1ms TTL=64

Ping statistics for 192.168.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

C:\Users\Bryan>ping 192.168.100.1

Pinging 192.168.100.1 with 32 bytes of data:
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63
Reply from 192.168.100.1: bytes=32 time=1ms TTL=63

Ping statistics for 192.168.100.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms

C:\Users\Bryan>ping 68.113.206.86

Pinging 68.113.206.86 with 32 bytes of data:
Reply from 68.113.206.86: bytes=32 time=31ms TTL=253
Reply from 68.113.206.86: bytes=32 time=21ms TTL=253
Reply from 68.113.206.86: bytes=32 time=17ms TTL=253
Reply from 68.113.206.86: bytes=32 time=33ms TTL=253

Ping statistics for 68.113.206.86:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 33ms, Average = 25ms

C:\Users\Bryan>

**space.cowboy** · 07-21-10, 03:41 PM

I usually run on wireless. Since I've had this trouble though, I've been running a cable directly to the router, as well as taking out the router and running direct to the modem.

**GReYVee** · 07-22-10, 09:51 AM

Originally Posted by space.cowboy

I usually run on wireless. Since I've had this trouble though, I've been running a cable directly to the router, as well as taking out the router and running direct to the modem.

Hmm. Did some inbound testing to you as well. Although there is the occasional spike in latency (brief 50ms jitter), the connection looks generally stable. What type of symptoms have you been experiencing?

**space.cowboy** · 07-22-10, 12:08 PM

Originally Posted by GReYVee

Hmm. Did some inbound testing to you as well. Although there is the occasional spike in latency (brief 50ms jitter), the connection looks generally stable. What type of symptoms have you been experiencing?

My connection is generally fast. I've been timing out a lot recently though, which I have never been prone to. Sometimes, I can play 20 or 30 minutes without timing out if nobody in the house is on the internet. If somebody else is on the internet though, I go pretty rapidly through periods of playing fine, then lagging out, then fine again, until I finally completely time out.

We've recently upgraded our internet from 8 meg to 16 meg downstream. When I was on the 8, I could be playing my games, somebody could be playing on the internet with the playstation in the other room, and my brother would be on WoW and I wouldn't be able to tell any difference in the connection. Since the upgrade, I've been barely able to play with nobody else on the internet without it timing out, and completely unable while another is using the internet as well.