Tracert's

**WickedTribe** · 07-30-09, 02:46 PM

Alright, I'm not sure how this works or what it tells you. Should I just run it immediately after I get a spike or crash? Can I run it while the game is running, or will that effect its outcome?

**WileECyte** · 07-30-09, 03:02 PM

You can run it while in game or right after crashes. 2142 doesn't generate a lot of network traffic.

The hops it is showing are the routers (and other network devices) that are between your PC and TTP.
Generally, if you look at the numbers listed in ms (milliseconds) They should ideally be under 100 ms. If you see one of the hops with numbers that are out of whack that can indicate where your connection issues are. If there isn't one that is outrageously off... it could be another issue...

This would be a good thing to keep around because this is what a 'good' traceroute looks like. the 3 values for each hop are all relatively close, numerically, and 60 ms from Boston to Texas isn't horrible.

If you can't find something that's out of whack, another test you can do is a ping test.

In a Windows command window run 'ping -t 50 207.210.254.226' This will send 50 ping packets to TTP's server. The key thing to look at is packet loss. If there's packet loss, that can be indicative of a network problem that isn't always reflected in your actual ping...

**WickedTribe** · 07-30-09, 03:14 PM

Thanks WhileE.

**trailhunter** · 07-30-09, 05:19 PM

BF2142

Had a few lag spikes and a couple crashes. Other than that, the new server seemed to be pretty smooth later in the evening.
6 less hops for me. :9

Old server tracert.

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 34 ms 33 ms 34 ms 10.34.29.1
3 34 ms 33 ms 32 ms so-0-3-0-0.CHI01-CORE-RTR1.verizon-gni.net [130.
81.36.108]
4 33 ms 33 ms 33 ms as0-0.CHI01-BB-RTR1.verizon-gni.net [130.81.20.5
6]
5 35 ms 34 ms 33 ms 0.ge-6-3-0.XL3.CHI13.ALTER.NET [152.63.65.129]
6 33 ms 34 ms 33 ms 0.so-6-0-0.BR2.CHI13.ALTER.NET [152.63.73.25]
7 33 ms 33 ms 33 ms sl-st21-chi-3-0-0.sprintlink.net [144.232.18.141
]
8 35 ms 35 ms 35 ms sl-crs1-chi-0-10-2-0.sprintlink.net [144.232.20.
90]
9 46 ms 46 ms 46 ms sl-crs2-kc-0-14-3-0.sprintlink.net [144.232.24.2
05]
10 59 ms 61 ms 60 ms 144.232.8.63
11 60 ms 60 ms 60 ms sl-st30-dal-0-12-0-0.sprintlink.net [144.232.20.
252]
12 58 ms 58 ms 58 ms sl-lodst3-231662-0.sprintlink.net [144.223.244.1
94]
13 59 ms 58 ms 58 ms 66.18.0.138.databank.com [66.18.0.138]
14 * * * Request timed out.
15 * * * Request timed out.
16 58 ms 58 ms 58 ms 90.220.232.72.static.reverse.ltdomains.com [72.2
32.220.90]

Trace complete.

New server tracert.

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

1 <1 ms <1 ms <1 ms 192.168.0.1
2 34 ms 34 ms 34 ms 10.34.29.1
3 33 ms 33 ms 33 ms so-0-3-0-0.CHI01-CORE-RTR1.verizon-gni.net [130.
81.36.108]
4 34 ms 33 ms 33 ms as0-0.CHI01-BB-RTR1.verizon-gni.net [130.81.20.5
6]
5 48 ms 34 ms 33 ms so-6-0-0-0.CHI80-PEER-RTR1.verizon-gni.net [130.
81.16.11]
6 33 ms 33 ms 43 ms 130.81.15.166
7 56 ms 56 ms 56 ms hagg-03-ge-0-0-0-460.dlfw.twtelecom.net [64.129.
234.4]
8 56 ms 56 ms 56 ms 206.123.64.34
9 58 ms 63 ms 57 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]

10 58 ms 58 ms 58 ms unknown.dfw.colocrossing.com [207.210.254.226]

Trace complete.

**...bigdog...** · 07-31-09, 09:27 AM

not just smooth....it's 6 less hops. That's great!

**Jonas Quin** · 07-31-09, 03:32 PM

New 2142 server sorry don't have my old one, it was in a doc that is now missing... :5

Traceroute has started ...

traceroute to 207.210.254.226 (207.210.254.226), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 4.191 ms 1.610 ms 1.495 ms
2 10.101.160.1 (10.101.160.1) 7.988 ms 8.902 ms 8.044 ms
3 static.unknown.charter.com (96.34.96.136) 10.352 ms 15.836 ms 9.036 ms
4 96.34.2.24 (96.34.2.24) 10.436 ms 11.304 ms 16.013 ms
5 los-edge-01.inet.qwest.net (208.46.190.193) 9.648 ms 11.619 ms 11.820 ms
6 los-core-01.inet.qwest.net (205.171.32.33) 11.723 ms 11.218 ms 22.171 ms
7 lap-brdr-03.inet.qwest.net (67.14.22.74) 11.222 ms * *
8 63.146.27.78 (63.146.27.78) 16.192 ms 11.642 ms 63.146.27.74 (63.146.27.74) 12.620 ms
9 scor-02-rif1.roch.twtelecom.net (66.192.240.194) 63.721 ms 48.322 ms 47.366 ms
10 206.123.64.34 (206.123.64.34) 47.799 ms 47.665 ms 47.602 ms
11 xe-0-47.cr.dfw.colocrossing.com (65.99.208.122) 50.240 ms 51.984 ms 51.078 ms
12 unknown.dfw.colocrossing.com (207.210.254.226) 51.066 ms 50.178 ms 48.910 ms

**...bigdog...** · 07-31-09, 04:25 PM

12 hops is good stuff.

**yayupp** · 07-31-09, 04:32 PM

BF 2142 Server

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

C:\Documents and Settings\Trenty>tracert 207.210.254.226:17567
Unable to resolve target system name 207.210.254.226:17567.

C:\Documents and Settings\Trenty>tracert 207.210.254.226

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

1 <1 ms 3 ms 4294967294 ms WL.domain.com [192.168.2.1]
2 1 ms 3 ms <1 ms 192.168.1.1
3 12 ms 12 ms 9 ms lkdltxcobr1.monrlacoro3.centurytel.net [69.29.189.4]
4 11 ms 12 ms 9 ms 207-119-249-232.hardware.centurytel.net [207.119.249.232]
5 13 ms 12 ms 12 ms 206.51.71.93
6 11 ms 9 ms 11 ms ip65-47-204-9.z204-47-65.customer.algx.net [65.47.204.9]
7 13 ms 14 ms 11 ms 207.88.15.46.ptr.us.xo.net [207.88.15.46]
8 13 ms 24 ms 14 ms 64.132.69.121
9 12 ms 15 ms 14 ms hagg-03-ge-0-0-0-460.dlfw.twtelecom.net [64.129.234.4]
10 11 ms 14 ms 14 ms 206.123.64.34
11 17 ms 17 ms 17 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]
12 13 ms 17 ms 11 ms unknown.dfw.colocrossing.com [207.210.254.226]

Trace complete.

C:\Documents and Settings\Trenty>

**~~Cpt.Reiskis~~** · 07-31-09, 05:16 PM

new bf2 server:

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

C:\Documents and Settings\Me>tracert 207.210.254.226

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

1 * * * Request timed out.
2 19 ms 7 ms 7 ms te-1-4-ur08.mtprospect.il.chicago.comcast.net [68.85.131.169]
3 4294967294 ms 9 ms 9 ms be-50-ar01.area4.il.chicago.comcast.net [68.87.230.53]
4 9 ms 4294967295 ms 11 ms pos-1-13-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.49]
5 4294967295 ms 11 ms 20 ms peer-02-ae0-104.chcg.twtelecom.net [68.86.88.246]
6 24 ms 25 ms 35 ms scor-02-rif1.roch.twtelecom.net [66.192.240.194]
7 23 ms 32 ms 31 ms 206.123.64.34
8 33 ms 49 ms 22 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]
9 23 ms 21 ms 34 ms unknown.dfw.colocrossing.com [207.210.254.226]

Trace complete.

Ping went down, by about 10

**WileECyte** · 08-03-09, 10:29 PM

I'm seeing wildly swing pings in game. My ping to the old server was always about 20ms... tonight, I was lucky to see less than 100ms and it would spike to 900+ ms. Made for a very miserable experience.

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

1 2 ms 1 ms 1 ms DD-WRT [192.168.1.1]
2 8 ms 9 ms 9 ms 10.4.32.1
3 9 ms 10 ms * gig2-24.dllatxrch-rtr1.tx.rr.com [70.125.218.232
]
4 11 ms 13 ms 9 ms gig5-0-0.dllatxchn-rtr6.tx.rr.com [70.125.217.11
1]
5 17 ms 11 ms 10 ms gig2-0-0.dllatxl3-rtr1.texas.rr.com [24.93.37.10
0]
6 13 ms 11 ms 12 ms ae-4-0.cr0.dfw10.tbone.rr.com [66.109.6.88]
7 17 ms 15 ms 14 ms ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
8 17 ms 16 ms 13 ms 64.132.69.65
9 18 ms 16 ms 15 ms hagg-03-ge-0-0-0-460.dlfw.twtelecom.net [64.129.
234.4]
10 59 ms 57 ms 56 ms 206.123.64.34
11 61 ms 58 ms 62 ms xe-0-47.cr.dfw.colocrossing.com [65.99.208.122]

12 58 ms 58 ms 56 ms unknown.dfw.colocrossing.com [207.210.254.226]

Trace complete.

Big jump from hop 9 to 10 and very uncharacteristic of my connectivity being within 20 miles of the server itself.