Tracert's

**ems_goof** · 08-15-08, 12:08 PM

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Jim>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 23 ms <1 ms <1 ms 192.168.1.1
2 6 ms 5 ms 5 ms 73.128.251.1
3 7 ms 7 ms 7 ms ge-3-13-ur01.owingsmills.md.bad.comcast.net [68.
85.170.241]
4 9 ms 10 ms 7 ms te-8-4-ar01.howardcounty.md.bad.comcast.net [68.
87.136.1]
5 9 ms 9 ms 8 ms po-10-ar02.whitemarsh.md.bad.comcast.net [68.87.
129.34]
6 12 ms 11 ms 11 ms te-0-3-0-4-cr01.philadelphia.pa.ibone.comcast.ne
t [68.86.90.81]
7 13 ms 13 ms 14 ms pos-0-8-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.85.10]
8 15 ms 14 ms 16 ms 64.132.69.77
9 95 ms 102 ms 77 ms hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.
234.20]
10 50 ms 49 ms 49 ms aw_ce_10g.databank.com [63.164.96.66]
11 103 ms 77 ms 102 ms pod22i_aw.layeredtech.com [63.164.96.234]
12 * * * Request timed out.
13 52 ms 102 ms 102 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

C:\Documents and Settings\Jim>

After a 5 minute ping on a couple servers, here's the results:
Ping statistics for 64.129.234.20:
Packets: Sent = 300, Received = 300, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 77ms, Maximum = 159ms, Average = 94ms

Ping statistics for 63.164.96.234:
Packets: Sent = 300, Received = 300, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 205ms, Average = 72ms

Ping statistics for 72.232.220.90:
Packets: Sent = 300, Received = 300, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 49ms, Maximum = 109ms, Average = 70ms

C:\Documents and Settings\Jim>

I've been getting drops from BF2, BF2 PR, and BF2142 for a little while now. It's driving me crazy.

However, when I send a trace to the TG BF2 PR server, I get the following:
Tracing route to bf2sb.tacticalgamer.com [64.34.161.157]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 8 ms 10 ms 6 ms 73.128.251.1
3 8 ms 8 ms 7 ms ge-3-13-ur01.owingsmills.md.bad.comcast.net [68.
85.170.241]
4 21 ms 6 ms 7 ms te-8-4-ar01.howardcounty.md.bad.comcast.net [68.
87.136.1]
5 12 ms 8 ms 7 ms po-10-ar02.whitemarsh.md.bad.comcast.net [68.87.
129.34]
6 11 ms 12 ms 12 ms pos-0-6-0-0-crs01.401nbroadst.pa.panjde.comcast.
net [68.86.90.17]
7 14 ms 13 ms 13 ms pos-0-9-0-0-cr01.newyork.ny.ibone.comcast.net [6
8.86.85.14]
8 14 ms 12 ms 13 ms xe-10-1-0.edge1.NewYork2.Level3.net [4.78.169.45
]
9 14 ms 15 ms 18 ms vlan69.csw1.NewYork1.Level3.net [4.68.16.62]
10 24 ms 13 ms 14 ms ae-63-63.ebr3.NewYork1.Level3.net [4.69.134.97]

11 16 ms 17 ms 17 ms ae-3.ebr3.Washington1.Level3.net [4.69.132.89]
12 28 ms 21 ms 15 ms ae-63-63.csw1.Washington1.Level3.net [4.69.134.1
62]
13 25 ms 21 ms 21 ms ae-1-69.edge2.Washington3.Level3.net [4.68.17.12
]
14 19 ms 15 ms 17 ms PEER-1-NETW.edge2.Washington3.Level3.net [4.71.2
34.6]
15 18 ms 17 ms 18 ms 10ge.ten1-1.wdc-sp2-cor-1.peer1.net [216.187.116
.253]
16 19 ms 23 ms 19 ms 216.187.116.238
17 23 ms 17 ms 18 ms bf2sb.tacticalgamer.com [64.34.161.157]

Trace complete.

I can't even stay connected for 5 minutes on any PR servers, or BF2142 servers. Thoughts?

**...bigdog...** · 08-15-08, 04:08 PM

pings look ok.....but you're getting dropped?

**ems_goof** · 08-15-08, 04:37 PM

Constantly. I get a "Lost Connection to Server" message. Only on the EA games I have though - BF2, PR, and 2142. 2142 is the worst (can't even get through 1 round). The others have intermittent spikes, then drop all together, without warning.

**Pineapple!** · 09-02-08, 02:21 PM

Tracing route to 82.3.1343.static.theplanet.com [67.19.3.130]
over a maximum of 30 hops:

1 * * * Request timed out.
2 25 ms 12 ms 12 ms ge-0-1-0-150.aggr01.crchtx.grandecom.net [216.82.202.134]
3 27 ms 27 ms 28 ms so-2-0-3-0.core02.smrctx.grandecom.net [24.155.121.31]
4 47 ms 56 ms 46 ms so-1-2-0.core02.dllstx.grandecom.net [24.155.121.226]
5 48 ms 61 ms 50 ms eq-dallas-1000M.theplanet.com [206.223.118.3]
6 80 ms 46 ms 47 ms te9-2.dsr01.dllstx3.theplanet.com [70.87.253.14]
7 95 ms 224 ms 215 ms po31.dsr01.dllstx4.theplanet.com [70.87.253.74]
8 52 ms 67 ms 48 ms gi1-0-1.car01.dllstx4.theplanet.com [67.19.255.2]
9 86 ms 50 ms 47 ms 82.3.1343.static.theplanet.com [67.19.3.130]

**...bigdog...** · 09-02-08, 04:50 PM

Originally Posted by Pineapple!

Tracing route to 82.3.1343.static.theplanet.com [67.19.3.130]
over a maximum of 30 hops:

1 * * * Request timed out.
2 25 ms 12 ms 12 ms ge-0-1-0-150.aggr01.crchtx.grandecom.net [216.82.202.134]
3 27 ms 27 ms 28 ms so-2-0-3-0.core02.smrctx.grandecom.net [24.155.121.31]
4 47 ms 56 ms 46 ms so-1-2-0.core02.dllstx.grandecom.net [24.155.121.226]
5 48 ms 61 ms 50 ms eq-dallas-1000M.theplanet.com [206.223.118.3]
6 80 ms 46 ms 47 ms te9-2.dsr01.dllstx3.theplanet.com [70.87.253.14]
7 95 ms 224 ms 215 ms po31.dsr01.dllstx4.theplanet.com [70.87.253.74]
8 52 ms 67 ms 48 ms gi1-0-1.car01.dllstx4.theplanet.com [67.19.255.2]
9 86 ms 50 ms 47 ms 82.3.1343.static.theplanet.com [67.19.3.130]

it should be expected that, with all the hurricane damage, there are going to be some network issues. Looks like thePlanet in dallas is having some trouble....run some more traces later today/tomorrow, and we'll see how it looks.

**Tamato24** · 10-05-08, 11:12 AM

Ok, here are my results to the TTP bf2 ranked server

C:\Users\Neil>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 Wireless_Broadband_Router.home [192.168.1.1]
2 9 ms 6 ms 7 ms 98.109.77.1
3 6 ms 6 ms 7 ms G3-0-0-799.LCR-07.NWRKNJ.verizon-gni.net [130.81
.109.122]
4 36 ms 17 ms 17 ms so-6-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81
.10.90]
5 19 ms 19 ms 19 ms eqix.asbn.twtelecom.net [206.223.115.36]
6 56 ms 56 ms 57 ms hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.
234.20]
7 58 ms 56 ms 57 ms aw_ce_10g.databank.com [63.164.96.66]
8 56 ms 59 ms 57 ms pod22e_aw.layeredtech.com [63.164.96.178]
9 * * * Request timed out.
10 58 ms 56 ms 57 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

I'm still getting a lot of connection issues. I think something is wrong with the unusually high numbers. I'm in NJ using Verizon Fios. It happens sporadically, sometimes 1, 2,3, or even 4 times in a round. Sometimes every other round. Any ideas how to fix?

**nsRaven** · 10-05-08, 07:45 PM

Finally a chance to really get some playtime in and I end up with connection problems. It keeps dying at random intervals. First tracert, looks good, connection had just died and I started this a couple minutes after when it came back on. Second tracert, immediately after the first. The connection apparently died again and then came back mid-process. I ran a third tracert immediately after the second and the connection was dead again so I only got 30 hops of nothing to show for it.

Extra info: When the connection is dead I can ping the router and the modem so its not my stuff, but I can't ping Charter's gateway that I'm connected to. Some days almost no problem, other days pretty much non stop and dead for varying amounts of time. Time to start complaining?

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

  1    2 ms    1 ms    1 ms  192.168.1.1
  2    22 ms    8 ms    11 ms  10.216.128.1
  3    25 ms    10 ms    8 ms  71-95-227-57.dhcp.rvsd.ca.charter.com [71.95.227
.57]
  4    25 ms    15 ms    15 ms  66-215-0-150.static.lsan.ca.charter.com [66.215.
0.150]
  5    37 ms    19 ms    17 ms  los-edge-01.inet.qwest.net [208.46.190.193]
  6    42 ms    17 ms    24 ms  los-core-02.inet.qwest.net [205.171.32.37]
  7    69 ms    55 ms    55 ms  dal-edge-14.inet.qwest.net [67.14.2.65]
  8    63 ms    53 ms    61 ms  205.171.62.42
  9    69 ms    52 ms    50 ms  vlan905.core5.dfw1.rackspace.com [67.192.56.229]

10    60 ms    54 ms    66 ms  67.192.56.39
11    63 ms    58 ms    56 ms  151327-web1.texasteamplayers.com [67.192.131.130
]

Trace complete.

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

  1    13 ms    1 ms    1 ms  192.168.1.1
  2    *        *        *    Request timed out.
  3    *        *        *    Request timed out.
  4    *        *        *    Request timed out.
  5    *        *      75 ms  los-edge-01.inet.qwest.net [208.46.190.193]
  6    31 ms    44 ms    17 ms  los-core-02.inet.qwest.net [205.171.32.37]
  7    64 ms  101 ms    58 ms  dal-edge-14.inet.qwest.net [67.14.2.65]
  8  129 ms    52 ms    56 ms  205.171.62.42
  9    62 ms    65 ms    52 ms  vlan905.core5.dfw1.rackspace.com [67.192.56.229]

10    62 ms    53 ms    56 ms  67.192.56.39
11    58 ms    51 ms    54 ms  151327-web1.texasteamplayers.com [67.192.131.130
]

Trace complete.

**Muqtar SGT_Clintok** · 11-08-08, 03:48 PM

Trace to the new Top 5 server on Saturday, November 8th.

C:\Documents and Settings\Clint>tracert 206.123.95.74

Tracing route to unknown.dallas.colocrossing.com [206.123.95.74]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms Wireless_Broadband_Router.home [192.168.1.1]
2 11 ms 4 ms 4 ms 96.231.199.1
3 6 ms 5 ms 4 ms G11-1-561.LCR-05.WASHDC.verizon-gni.net [130.81.97.102]
4 26 ms 7 ms 18 ms so-6-0-0-0.PEER-RTR1.ASH.verizon-gni.net [130.81.10.90]
5 7 ms 7 ms 7 ms eqix.asbn.twtelecom.net [206.223.115.36]
6 43 ms 43 ms 43 ms hagg-03-ge-1-0-0-459.dlfw.twtelecom.net [64.129.234.20]
7 44 ms 49 ms 43 ms ge-1-1.core1.colo4dallas.net [206.123.64.26]
8 49 ms 49 ms 50 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]
9 50 ms 49 ms 50 ms unknown.dallas.colocrossing.com [206.123.95.74]
Trace complete.

Damn I love FIOS

**ninja|oaklandr** · 11-17-08, 10:22 PM

My numbers look good, but I keep getting kicked from the new BF2 vanilla for high ping. In game it shows me with 1023 ping.

A few other servers I tried worked fine.

C:\Documents and Settings\***>tracert 206.123.95.74

Tracing route to unknown.dallas.colocrossing.com [206.123.95.74]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 7 ms 5 ms 10.78.48.1
3 8 ms 7 ms 7 ms gig10-1-3.snantx6000-rtr1.satx.rr.com [24.28.133.152]
4 13 ms 13 ms 13 ms gig2-1-0.dllatxl3-rtr1.texas.rr.com [72.179.205.8]
5 16 ms 13 ms 14 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
6 15 ms 16 ms 14 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
7 18 ms 15 ms 15 ms 64.132.69.65
8 17 ms 18 ms 15 ms scor-02-rif1.roch.twtelecom.net [66.192.240.194]
9 14 ms 16 ms 14 ms ge-1-1.core1.colo4dallas.net [206.123.64.26]
10 16 ms 15 ms 15 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]
11 15 ms 15 ms 18 ms unknown.dallas.colocrossing.com [206.123.95.74]

Trace complete.

**Braddoc** · 11-18-08, 12:07 AM

Originally Posted by ninja|oaklandr

My numbers look good, but I keep getting kicked from the new BF2 vanilla for high ping. In game it shows me with 1023 ping.

A few other servers I tried worked fine.

C:\Documents and Settings\***>tracert 206.123.95.74

Tracing route to unknown.dallas.colocrossing.com [206.123.95.74]
over a maximum of 30 hops:

1 1 ms <1 ms <1 ms 192.168.1.1
2 13 ms 7 ms 5 ms 10.78.48.1
3 8 ms 7 ms 7 ms gig10-1-3.snantx6000-rtr1.satx.rr.com [24.28.133.152]
4 13 ms 13 ms 13 ms gig2-1-0.dllatxl3-rtr1.texas.rr.com [72.179.205.8]
5 16 ms 13 ms 14 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
6 15 ms 16 ms 14 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
7 18 ms 15 ms 15 ms 64.132.69.65
8 17 ms 18 ms 15 ms scor-02-rif1.roch.twtelecom.net [66.192.240.194]
9 14 ms 16 ms 14 ms ge-1-1.core1.colo4dallas.net [206.123.64.26]
10 16 ms 15 ms 15 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]
11 15 ms 15 ms 18 ms unknown.dallas.colocrossing.com [206.123.95.74]

Trace complete.

awesome numbers. the problem could intermittent. i suggest doing a "ping -t -l 1 206.123.95.74" before entering the game to see if there are any timeouts to the server. the -t option makes it ping non-stop (until you ctrl-c it), and the "-l 1" option makes the packet as small as possible so as to not take away too much bandwidth from either the server or your connection. if you get a high ping in-game, try to scroll back after getting kicked as far as possible to see if you either get timed out pings, or high TTL pings.