CS S server lagged

**...bigdog...** · 08-27-05, 06:04 PM

please post your tracert's. open a dos window, and type in teh following:

tracert 72.36.157.88

here's one from JAN

my tracert looks better than fine it looks perfect but i still have a ping of 250+

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 9 ms <1 ms <1 ms 129.119.183.1
2 5 ms <1 ms 1 ms bi-dg.smu.edu [129.119.0.129]
3 4 ms 2 ms 1 ms cisco2.smu.edu [129.119.0.249]
4 2 ms 1 ms 1 ms ntg-gw1-ge-1-2-0.northtexasgigapop.org [206.223.
141.89]
5 6 ms 7 ms 9 ms dllstx2wcx2-gige5-0-0.wcg.net [64.200.204.37]
6 2 ms 2 ms 6 ms 64.200.232.45
7 2 ms 3 ms 2 ms bcr2-so-3-3-0.Dallas.savvis.net [208.172.129.225
]
8 7 ms 4 ms 5 ms bcs2-so-3-0-0-500.Dallas.savvis.net [204.70.193.
22]
9 5 ms 3 ms 3 ms ohr1-pos-1-0.FortWorthda1.savvis.net [208.172.12
9.230]
10 4 ms 3 ms 3 ms 216.39.64.18
11 3 ms 4 ms 7 ms 216.39.69.206
12 * * * Request timed out.
13 3 ms 5 ms 3 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

**BigHub** · 08-27-05, 08:11 PM

Here is mine...

C:\Documents and Settings\Jono Hubbard>tracert 72.36.157.88

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 1 ms 1 ms 1 ms 192.168.0.1
2 10 ms 10 ms 9 ms ip70-191-173-1.fv.dl.cox.net [70.191.173.1]
3 22 ms 9 ms 9 ms cdm-208-180-23-153.bcst.cox-internet.com [208.18
0.23.153]
4 11 ms 8 ms 9 ms cdm-208-180-23-133.bcst.cox-internet.com [208.18
0.23.133]
5 151 ms 12 ms 13 ms dllsbbrc02-gew0402.ma.dl.cox-internet.com [66.76
.45.149]
6 19 ms 14 ms 23 ms 68.1.206.45
7 17 ms 16 ms 15 ms so-3-3-0-0.gar2.Dallas1.Level3.net [4.78.234.5]

8 18 ms 42 ms 15 ms ge-1-2-52.car4.Dallas1.Level3.net [4.68.122.39]

9 15 ms 14 ms 13 ms savvis-level3-ge.Dallas1.Level3.net [4.68.111.86
]
10 15 ms 14 ms 13 ms dpr1-ae1.DallasEquinix.savvis.net [204.70.134.13
]
11 16 ms 15 ms 18 ms ohr2-pos-1-0.FortWorthda1.savvis.net [204.70.134
.18]
12 19 ms 12 ms 16 ms 216.39.64.10
13 16 ms 15 ms 15 ms 216.39.69.134
14 * * * Request timed out.
15 19 ms 16 ms 18 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

**Ãƒâ€¦Ã‚Â®Ãƒâ€¡TÃƒÅ’Ã‚Â¢_V** · 08-28-05, 03:07 AM

this is the one I got:

Code:

Tracing route to 88.157.36.72.reverse.layeredtech.com &#91;72.36.157.88&#93;
over a maximum of 30 hops&#58;

  1     6 ms     7 ms     7 ms  10.248.144.1
  2     7 ms     7 ms     7 ms  68.1.200.245
  3    19 ms    19 ms    19 ms  dllsdsrc02-pos0701.rd.dl.cox.net &#91;68.1.206.21&#93;
  4    17 ms    17 ms    17 ms  so-3-3-0-0.gar2.Dallas1.Level3.net &#91;4.78.234.5&#93;

  5    18 ms    19 ms    18 ms  ge-1-2-56.car4.Dallas1.Level3.net &#91;4.68.122.167&#93;

  6    18 ms    19 ms    21 ms  savvis-level3-ge.Dallas1.Level3.net &#91;4.68.111.86
&#93;
  7    19 ms    19 ms    19 ms  dpr1-ae1.DallasEquinix.savvis.net &#91;204.70.134.13
&#93;
  8    20 ms    19 ms    19 ms  ohr2-pos-1-0.FortWorthda1.savvis.net &#91;204.70.134
.18&#93;
  9    21 ms    19 ms    19 ms  216.39.64.10
 10    19 ms    19 ms    19 ms  216.39.69.134
 11     *        *        *     Request timed out.
 12    20 ms    23 ms    21 ms  88.157.36.72.reverse.layeredtech.com &#91;72.36.157.
88&#93;

Trace complete.

**skervy** · 08-28-05, 04:16 AM

C:\>tracert 72.36.157.88

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.0.1
2 7 ms 8 ms 8 ms adsl-70-240-191-254.dsl.hstntx.swbell.net [70.24
0.191.254]
3 8 ms 7 ms 8 ms dist2-vlan60.hstntx.sbcglobal.net [151.164.11.18
9]
4 8 ms 8 ms 7 ms bb1-g8-2-2.hstntx.sbcglobal.net [151.164.244.129
]
5 8 ms 8 ms 8 ms core1-p6-0.crhstx.sbcglobal.net [151.164.188.1]

6 13 ms 13 ms 13 ms core3-p3-0.crdltx.sbcglobal.net [151.164.240.189
]
7 12 ms 13 ms 12 ms core1-p9-0.crdltx.sbcglobal.net [151.164.242.118
]
8 14 ms 14 ms 14 ms bb1-p2-0.rcsntx.sbcglobal.net [151.164.40.38]
9 14 ms 13 ms 13 ms bb2-p4-0.rcsntx.sbcglobal.net [151.164.191.118]

10 15 ms 15 ms 15 ms ex1-p12-0.eqdltx.sbcglobal.net [151.164.44.45]
11 15 ms 15 ms 15 ms 151.164.249.222
12 16 ms 16 ms 15 ms ohr2-pos-1-0.FortWorthda1.savvis.net [204.70.134
.18]
13 16 ms 16 ms 16 ms 216.39.64.27
14 16 ms 16 ms 16 ms 216.39.69.134
15 * * * Request timed out.
16 17 ms 16 ms 16 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

**geeseven** · 08-28-05, 09:28 AM

Code:

C&#58;\tracert 72.36.157.88

Tracing route to 88.157.36.72.reverse.layeredtech.com &#91;72.36.157.88&#93;
over a maximum of 30 hops&#58;

  1     9 ms     8 ms     7 ms  10.49.224.1
  2     8 ms     7 ms     7 ms  gig2-1.hstntxala-rtr1.houston.rr.com &#91;24.28.100.
97&#93;
  3     8 ms    10 ms     9 ms  srp13-0.hstntxtid-rtr1.houston.rr.com &#91;24.28.100
.17&#93;
  4     7 ms    16 ms    10 ms  pos9-0.hstntxtid-rtr4.texas.rr.com &#91;24.93.34.94&#93;

  5     9 ms     9 ms    16 ms  son0-1-0.hstqtxl3-rtr1.texas.rr.com &#91;24.93.33.16
5&#93;
  6    17 ms    10 ms     9 ms  pop1-hou-P0-1.atdn.net &#91;66.185.133.145&#93;
  7    18 ms    10 ms    19 ms  bb1-hou-P2-0.atdn.net &#91;66.185.150.148&#93;
  8    19 ms    18 ms    17 ms  bb1-dls-P6-0.atdn.net &#91;66.185.152.132&#93;
  9    18 ms    17 ms    19 ms  pop1-dls-P0-0.atdn.net &#91;66.185.133.81&#93;
 10    19 ms    19 ms    26 ms  204.70.134.21
 11    24 ms    18 ms    21 ms  ohr2-pos-1-0.FortWorthda1.savvis.net &#91;204.70.134
.18&#93;
 12    26 ms    19 ms    19 ms  216.39.64.27
 13    19 ms    20 ms    19 ms  216.39.69.134
 14     *        *        *     Request timed out.
 15    18 ms    44 ms    20 ms  88.157.36.72.reverse.layeredtech.com &#91;72.36.157.
88&#93;

Trace complete.

**32Degrees** · 08-29-05, 01:13 AM

Question...y do u need peoples tracert...although it might explain how i get a 35ms in Chic and a 45ms in NY and then i connect to a Dal and its 78ms.

**...bigdog...** · 08-29-05, 01:29 AM

providing the trace shows us the routing path our ISPs and AoW's ISP are using to get us from A to B. Frequently, these routings, especially those on the AoW side of things, can be changed in order to get those local to the server better connections, pings, etc.

sometimes, you do a trace, and see that your connection from houston to dallas will take you to chicago and atlanta first, before you get back to dallas........that's messed up. We've seen it before, and by providing the traces, we got it fixed.

**32Degrees** · 08-29-05, 09:04 AM

Well i dont know how to copy and paste the Tracert but i now know y i ping around 80 in the server even though im on my college internet now....i go through Chic, to DC, to Virginia, to Atlanta, then i reach Dallas....figures my college would fuck me over when it comes to Dallas server....if u could tell me how to display my Trace ill do it again and post it.

**...bigdog...** · 08-29-05, 10:57 AM

noob.

there is another post about pings and tracert's in this forum section. But, to make it easier for you, here you go:

open up a DOS window, and type this:

tracert 72.36.157.88

right click the top bar of the DOS window, and check the "edit mode" so you can copy the screen. Then paste it here. We'll submit it to the AoW people and see what they think.

**32Degrees** · 08-29-05, 11:05 AM

Tracing route to 88.157.36.72.reverse.layeredtech.com [72.36.157.88]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 172.16.131.254
2 <1 ms <1 ms <1 ms vlan9.wn.washburn.edu [198.252.14.254]
3 <1 ms <1 ms <1 ms perim3725rtr-e1.wn.washburn.edu [198.252.8.13]
4 1 ms <1 ms <1 ms expidentgateway.wuacc.edu [198.252.8.65]
5 23 ms 23 ms 24 ms s3-1-0.cr1.halle.clevoh.e-xpedient.com [216.130.
7.37]
6 29 ms 31 ms 32 ms ge-0-1-0-198.car2.pitc.pitbpa.e-xpedient.com [20
6.183.12.76]
7 30 ms 30 ms 30 ms g0-1-0-440.car1.acm.pitbpa.e-xpedient.com [206.2
10.75.248]
8 41 ms 40 ms 39 ms p0-0-0.car1.eqnxf.washdc.e-xpedient.com [66.230.
75.246]
9 40 ms 41 ms 40 ms bpr1-ge-5-2-0.VirginiaEquinix.savvis.net [208.17
3.52.61]
10 40 ms 40 ms 40 ms cpr1-pos-4-0.VirginiaEquinix.savvis.net [206.24.
227.57]
11 41 ms 41 ms 41 ms bcs1-so-3-3-0.Washington.savvis.net [206.24.238.
97]
12 75 ms 75 ms 75 ms bcs1-so-3-2-0.Dallas.savvis.net [204.70.192.82]

13 76 ms 76 ms 75 ms ohr1-pos-4-0.FortWorthda1.savvis.net [208.172.13
1.82]
14 75 ms 75 ms 76 ms 216.39.64.2
15 77 ms 76 ms 77 ms 216.39.69.134
16 * * * Request timed out.
17 77 ms 76 ms 77 ms 88.157.36.72.reverse.layeredtech.com [72.36.157.
88]

Trace complete.

There it is