All COD2 Players your assistance is needed……

[little_old_man]

I’ve been talking with Rugger for the last couple of days about the high ping issues that many of us have been experiencing (especially in the western US) and he has been working with our server host to try and resolve these problems. Our current hosting company has our servers in Chicago, and they have additional servers in the Dallas TX area. We are considering switching to the Dallas servers to see if it would improve the ping issues, but not at the expense of everybody else who isn’t having the same problems we are out west. There are some tests that each of us can run on our computers that would help determine if the move would be beneficial to us in the west without hurting the ping for those of you who currently reside closer to Chicago than we do.

 

The test we need you all to perform is called a “traceroute” or “tracert”. In a nutshell what it does is trace the signal from your PC to the game server, and can show where the signal might be slowing down and causing a high ping. I need as many people as possible (especially those in the west) to run this test and post the results here on this thread so we can see how a server change will affect us all.

 

I realize that many of us are computer challenged, so I’ll make the instructions as detailed as possible without confusing the shit out of you.

1. Click the start button on your desktop then click “run”.

2. Once you click on run a small box will pop up.

3. In the space provided that says “Open”, type CMD then click OK.

 

 

 

4. Now a black command prompt box will open. To the right of the right carrot, type the following:  tracert 8.9.37.132 then hit the enter key on your keyboard. This command will create a map of how the signal goes from your computer to the COD2 DM server in Chicago. It will
probably take no more than 30 seconds and at the bottom will say “trace complete” when finished.

 

 

 

 

5. Now you’ll need to copy and paste this information here so we can all see it. The way you do that is to right click on the bar at the top of the command prompt box, go down to edit, then select all. Once you click select all the black box will turn white which indicates everything in there has been selected.

 

 

 

 

6. Now right click again on the bar at the top of the box, down to edit, then click on copy. All of the information in that box has been copied, and all you need to do to paste it here is reply to this topic on the message board, then right click and paste it here. It doesn’t matter if the data is formatted properly, we can figure out the rest.

7. Now we need to repeat steps 4 through 6 again, only this time we will enter the IP address for the new server in Dallas. So at the bottom just below where it says trace complete, type the following: tracert 68.232.164.55 then hit the enter key and do exactly as you did in the steps above to copy and paste the data here.

 

Sorry for the long-winded post, but this information is very important and hopefully will help to get things running more smoothly.

 

If you have any questions just post them here and I’ll get back to you as soon as I can.

 

Thanks,

LOM

 

Edited August 27, 2013 by little_old_man

[loaderXI]

Microsoft Windows XP [Version 5.1.2600]

© Copyright 1985-2001 Microsoft Corp.

 

C:\Documents and Settings\William Shepherd>tracert 8.9.37.132

 

Tracing route to 8.9.37.132 over a maximum of 30 hops

 

  1    79 ms    76 ms    77 ms  8.9.37.132

 

Trace complete.

 

C:\Documents and Settings\William Shepherd>tracert 8.9.37.132

 

Tracing route to 8.9.37.132 over a maximum of 30 hops

 

  1    75 ms    76 ms    77 ms  8.9.37.132

 

Trace complete.

 

C:\Documents and Settings\William Shepherd>tracert 68.232.164.55

 

Tracing route to 68.232.164.55.choopa.net [68.232.164.55]

over a maximum of 30 hops:

 

  1    63 ms    63 ms    63 ms  68.232.164.55.choopa.net [68.232.164.55]

 

Trace complete.

 

C:\Documents and Settings\William Shepherd>tracert 68.232.164.55

 

Tracing route to 68.232.164.55.choopa.net [68.232.164.55]

over a maximum of 30 hops:

 

  1    63 ms    63 ms    63 ms  68.232.164.55.choopa.net [68.232.164.55]

 

Trace complete.

 

C:\Documents and Settings\William Shepherd>

[little_old_man]

That's strange Loader, you're only getting one hop item in your test. I get a dozen on mine. It's like you're plugged right into the game server and still have a shitty ping.

[Blackbart]

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Roger>tracert 8.9.37.132

Tracing route to 8.9.37.132 over a maximum of 30 hops

  1     2 ms     1 ms    20 ms  199.15.196.1
  2     2 ms     1 ms     3 ms  wsip-98-172-7-233.fv.ks.cox.net [98.172.7.233]
  3     9 ms     9 ms     9 ms  kscydsrj02-ae0.rd.ks.cox.net [70.183.71.93]
  4    10 ms     9 ms    11 ms  70.183.71.66
  5     8 ms     9 ms     9 ms  70.183.71.64
  6    21 ms    21 ms    21 ms  68.1.2.121
  7    22 ms    21 ms    21 ms  70.167.150.130
  8    23 ms    27 ms    22 ms  ae0-60g.cr1.dfw1.us.nlayer.net [69.31.63.125]
  9    33 ms    31 ms    33 ms  xe-0-2-1.cr1.ord1.us.nlayer.net [69.22.142.4]
10    37 ms    34 ms    33 ms  ae1-30g.ar1.ord1.us.nlayer.net [69.31.111.134]
11    33 ms    35 ms    33 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
12    32 ms    31 ms    31 ms  8.9.37.132

Trace complete.

C:\Users\Roger>tracert 68.232.164.55

Tracing route to 68.232.164.55.choopa.net [68.232.164.55]
over a maximum of 30 hops:

  1     2 ms     1 ms     1 ms  199.15.196.1
  2     3 ms     1 ms     3 ms  wsip-98-172-7-233.fv.ks.cox.net [98.172.7.233]
  3    10 ms     9 ms     9 ms  kscydsrj02-ae0.rd.ks.cox.net [70.183.71.93]
  4    11 ms    11 ms     9 ms  70.183.71.66
  5    17 ms     9 ms     9 ms  70.183.71.64
  6    21 ms    21 ms    21 ms  68.1.2.121
  7    22 ms    21 ms    21 ms  70.167.150.130
  8    21 ms    20 ms    21 ms  as20473.xe-7-0-0.ar1.dfw1.us.nlayer.net [69.31.6
3.238]
  9    23 ms    23 ms    23 ms  68.232.164.55.choopa.net [68.232.164.55]

Trace complete.

C:\Users\Roger>

[loaderXI]

FUCK IF I KNOW....RAN TEST TWICE DAMN NEAR SAME ON BOTH TRIES

[little_old_man]

Damn Bart, it looks like changing to the Dallas server would cut your ping in half. You're already too damn lucky, we better re-think this.

[Blackbart]

I already go through Dallas...I would lose three hops and gain about 10ms...I'm all for that...LOL... :)

[Dirk Diggler]

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Dirk Diggler>  tracert 8.9.37.132

Tracing route to 8.9.37.132 over a maximum of 30 hops

  1     1 ms    <1 ms    <1 ms  homeportal [192.168.100.254]
  2     *        *        *     Request timed out.
  3    40 ms    43 ms    40 ms  be6294.cipc2-wpg.bb.allstream.net [199.212.165.1
17]
  4    39 ms    39 ms    39 ms  ae0.gw1-chi.bb.allstream.net [199.212.160.202]
  5    38 ms    39 ms    38 ms  equinix.xe-1-3-0.cr2.ord1.us.nlayer.net [206.223
.119.61]
  6    41 ms    43 ms    40 ms  ae2-30g.ar1.ord1.us.nlayer.net [69.31.111.138]
  7    39 ms    39 ms    40 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
  8    40 ms    39 ms    38 ms  8.9.37.132

Trace complete.

C:\Users\Dirk Diggler>  tracert 68.232.164.55

Tracing route to 68.232.164.55.choopa.net [68.232.164.55]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  homeportal [192.168.100.254]
  2     *        *        *     Request timed out.
  3    42 ms    40 ms    39 ms  be6294.cipc2-wpg.bb.allstream.net [199.212.165.1
17]
  4    38 ms    39 ms    37 ms  ae0.gw1-chi.bb.allstream.net [199.212.160.202]
  5    39 ms    39 ms    39 ms  equinix.xe-1-3-0.cr2.ord1.us.nlayer.net [206.223
.119.61]
  6    40 ms    39 ms    38 ms  ae3-60g.cr1.ord1.us.nlayer.net [69.31.111.153]
  7    62 ms    62 ms    64 ms  xe-3-3-0.cr1.dfw1.us.nlayer.net [69.22.142.5]
  8    66 ms    63 ms    63 ms  ae1-50g.ar1.dfw1.us.nlayer.net [69.31.63.126]
  9    64 ms    62 ms    62 ms  as20473.xe-7-0-0.ar1.dfw1.us.nlayer.net [69.31.6
3.238]
 10    62 ms    61 ms    61 ms  68.232.164.55.choopa.net [68.232.164.55]

Trace complete.

C:\Users\Dirk Diggler>

 

i love Chicago.......

[TecHnOBoY]

I am not a CoD 2 Player but is saw this and hat to stop in:


The bottleneck from here seems to be tinet; the same as yours @@little_old_man

On top i got packetloss of up to 20%

 

 

 

For Windows users a litte tool

http://winmtr.net/download-winmtr/

does the same, but it's easier to use

Edited August 27, 2013 by TecHnOBoY

[Blackbart]

One thing to consider also is when is peak time usage for your area and if the bandwidth has been oversold by your provider...The peak time of usage in my area is around 9:00pm which is slightly later than most areas... :)

[TecHnOBoY]

 

last post edited, because the C&P resulst were barely readable

[Dark Asylumn]

looks like my ping would double

 

 

 

 

 

Microsoft Windows [Version 6.1.7600]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\BA>tracert 8.9.37.132

Tracing route to 8.9.37.132 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     2 ms     1 ms     2 ms  68.67.18.1
  3     1 ms     1 ms     1 ms  67.216.112.1
  4     6 ms     6 ms     6 ms  12.87.147.41
  5    18 ms    19 ms    15 ms  cr84.sl9mo.ip.att.net [12.123.140.214]
  6    20 ms    18 ms    18 ms  cr2.sl9mo.ip.att.net [12.123.140.169]
  7    18 ms    15 ms    15 ms  cr2.cgcil.ip.att.net [12.122.2.21]
  8    14 ms    15 ms    16 ms  gar13.cgcil.ip.att.net [12.122.132.121]
  9     *       13 ms    13 ms  ae3.chi11.ip4.tinet.net [173.241.128.29]
 10    21 ms    19 ms     *     gtt-gw.ip4.tinet.net [77.67.70.166]
 11    15 ms    15 ms    17 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
 12    18 ms    17 ms    15 ms  8.9.37.132

Trace complete.

C:\Users\BA>tracert 68.232.164.55

Tracing route to 68.232.164.55.choopa.net [68.232.164.55]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  1.1.168.192.in-addr.arpa [192.168.1.1]
  2    <1 ms     1 ms     2 ms  1.18.67.68.in-addr.arpa [68.67.18.1]
  3     1 ms     2 ms     1 ms  1.112.216.67.in-addr.arpa [67.216.112.1]
  4    10 ms     7 ms     7 ms  41.147.87.12.in-addr.arpa [12.87.147.41]
  5    14 ms    20 ms    18 ms  cr84.sl9mo.ip.att.net [12.123.140.214]
  6    18 ms    15 ms    15 ms  cr2.sl9mo.ip.att.net [12.123.140.169]
  7    17 ms    19 ms    15 ms  cr2.cgcil.ip.att.net [12.122.2.21]
  8    15 ms    16 ms    17 ms  gar13.cgcil.ip.att.net [12.122.132.121]
  9     *       13 ms     *     ae3.chi11.ip4.tinet.net [173.241.128.29]
 10    33 ms    38 ms    34 ms  xe-3-1-0.dal33.ip4.tinet.net [89.149.180.246]
 11    36 ms    36 ms    36 ms  gtt-gw.ip4.tinet.net [173.241.130.154]
 12    35 ms    37 ms    36 ms  ae0-11g.ar1.dfw1.us.nlayer.net [198.47.104.68]
 13    40 ms    38 ms    36 ms  as20473.xe-7-0-0.ar1.dfw1.us.nlayer.net [69.31.6
3.238]
 14    40 ms    39 ms    36 ms  68.232.164.55.choopa.net [68.232.164.55]

Trace complete.

C:\Users\BA>

Edited August 27, 2013 by Dark Asylumn

[Boomer]

20 bucks to my paypal acct & I'll help you!

[PimpedOutPete]

Hey Guys, I won't be back from vacation til September 1st... I will check then.

[1lost1]

Not a COD 2 player but thought i would post from the West coast as well

 

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Jon>tracert 8.9.37.132

Tracing route to 8.9.37.132 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  NBG-419N.zyxel.com [192.168.1.1]
  2     8 ms     7 ms     7 ms  73.102.220.1
  3     7 ms     8 ms     8 ms  te-0-0-0-8-ur06.tacoma.wa.seattle.comcast.net [6
8.85.144.9]
  4    11 ms    10 ms     9 ms  ae-28-0-ar03.seattle.wa.seattle.comcast.net [69.
139.164.205]
  5    12 ms    12 ms    12 ms  he-1-5-0-0-11-cr01.seattle.wa.ibone.comcast.net
[68.86.94.65]
  6    12 ms    15 ms    11 ms  be-12-pe03.seattle.wa.ibone.comcast.net [68.86.8
4.106]
  7    36 ms    12 ms    10 ms  sea-edge-13.inet.qwest.net [67.135.42.153]
  8     *        *        *     Request timed out.
  9    64 ms    66 ms    65 ms  216.207.157.42
 10    67 ms    65 ms    66 ms  ae3.ar1.ord1.us.nlayer.net [69.31.111.243]
 11    65 ms    66 ms    79 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
 12    63 ms    64 ms    62 ms  8.9.37.132

Trace complete.

C:\Users\Jon>tracert 68.232.164.55

Tracing route to 68.232.164.55.choopa.net [68.232.164.55]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  NBG-419N.zyxel.com [192.168.1.1]
  2    14 ms     8 ms     7 ms  73.102.220.1
  3    10 ms     7 ms     7 ms  te-0-0-0-8-ur06.tacoma.wa.seattle.comcast.net [6
8.85.144.9]
  4    10 ms     9 ms    23 ms  ae-28-0-ar03.seattle.wa.seattle.comcast.net [69.
139.164.205]
  5    12 ms    13 ms    15 ms  he-1-6-0-0-10-cr01.seattle.wa.ibone.comcast.net
[68.86.94.69]
  6    26 ms    28 ms    29 ms  pos-1-13-0-0-cr01.sacramento.ca.ibone.comcast.ne
t [68.86.85.162]
  7    28 ms    27 ms    27 ms  he-0-5-0-0-cr01.sanjose.ca.ibone.comcast.net [68
.86.85.182]
  8    33 ms    32 ms    35 ms  pos-0-3-0-0-pe01.11greatoaks.ca.ibone.comcast.ne
t [68.86.87.18]
  9    30 ms    34 ms    33 ms  xe-9-3-0.sjc10.ip4.tinet.net [213.200.80.165]
 10    64 ms    67 ms    67 ms  xe-8-3-2.dal33.ip4.tinet.net [141.136.111.98]
 11    66 ms    65 ms    66 ms  gtt-gw.ip4.tinet.net [173.241.130.154]
 12    70 ms    69 ms    69 ms  ae0-11g.ar1.dfw1.us.nlayer.net [198.47.104.68]
 13    66 ms    68 ms    64 ms  as20473.xe-7-0-0.ar1.dfw1.us.nlayer.net [69.31.6
3.238]
 14    71 ms    67 ms    66 ms  68.232.164.55.choopa.net [68.232.164.55]

Trace complete.

C:\Users\Jon>

[Artimus Prime]

Here is mine.....I ran it twice.

 

Microsoft Windows [Version 6.0.6002]
Copyright © 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Artimus>tracert 8.9.37.132

Tracing route to 8.9.37.132 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     7 ms     8 ms  73.98.100.1
  3     8 ms     7 ms     9 ms  te-7-2-ur03.ferndale.wa.seattle.comcast.net [68.
87.207.113]
  4    14 ms    13 ms    14 ms  ae-27-0-ar03.burien.wa.seattle.comcast.net [69.1
39.164.189]
  5    11 ms    12 ms    11 ms  ae-1-0-ar03.seattle.wa.seattle.comcast.net [68.8
5.240.94]
  6    16 ms    14 ms    15 ms  he-1-6-0-0-10-cr01.seattle.wa.ibone.comcast.net
[68.86.94.69]
  7    14 ms    13 ms    13 ms  be-16-pe03.seattle.wa.ibone.comcast.net [68.86.8
3.10]
  8    36 ms    20 ms    20 ms  sea-edge-13.inet.qwest.net [67.135.42.153]
  9     *        *        *     Request timed out.
 10    97 ms    97 ms    99 ms  216.207.157.42
 11    98 ms    97 ms   100 ms  ae3.ar1.ord1.us.nlayer.net [69.31.111.243]
 12    96 ms    96 ms    97 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
 13    96 ms    96 ms    96 ms  8.9.37.132

Trace complete.

C:\Users\Artimus>tracert 8.9.37.132

Tracing route to 8.9.37.132 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     7 ms     8 ms     7 ms  73.98.100.1
  3     8 ms     8 ms     8 ms  te-7-2-ur03.ferndale.wa.seattle.comcast.net [68.
87.207.113]
  4    13 ms    12 ms    15 ms  ae-27-0-ar03.burien.wa.seattle.comcast.net [69.1
39.164.189]
  5    12 ms    12 ms    12 ms  ae-1-0-ar03.seattle.wa.seattle.comcast.net [68.8
5.240.94]
  6    16 ms    19 ms    15 ms  he-1-8-0-0-10-cr01.seattle.wa.ibone.comcast.net
[68.86.94.229]
  7    13 ms    13 ms    12 ms  be-16-pe03.seattle.wa.ibone.comcast.net [68.86.8
3.10]
  8    22 ms    21 ms    21 ms  sea-edge-13.inet.qwest.net [67.135.42.153]
  9     *        *        *     Request timed out.
 10    97 ms    96 ms    97 ms  216.207.157.42
 11   100 ms    98 ms    96 ms  ae3.ar1.ord1.us.nlayer.net [69.31.111.243]
 12    96 ms    97 ms    96 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
 13    96 ms    98 ms    97 ms  8.9.37.132

Trace complete.

C:\Users\Artimus>

[little_old_man]

It looks like some people who use internet explorer are having trouble reading this thread. I'll see if I can re-post it so it works.

[TheLastColdBeer]

Forgiven LOM. Yeah, this thread doesn't seem to like IE 10. Works fine in Chrome. Just to place the info where it should be:

 

Microsoft Windows [Version 6.1.7601]

Copyright © 2009 Microsoft Corporation.  All rights reserved.

 

C:\Users\James>traceroute

'traceroute' is not recognized as an internal or external command,

operable program or batch file.

 

C:\Users\James>cmd

Microsoft Windows [Version 6.1.7601]

Copyright © 2009 Microsoft Corporation.  All rights reserved.

 

C:\Users\James>traceroute 8.9.37.132

'traceroute' is not recognized as an internal or external command,

operable program or batch file.

 

C:\Users\James>tracert 8.9.37.132

 

Tracing route to 8.9.37.132 over a maximum of 30 hops

 

  1    <1 ms    <1 ms    <1 ms  192.168.1.1

  2    37 ms    29 ms    19 ms  98.212.96.1

  3     9 ms    11 ms     9 ms  68.85.178.237

  4    10 ms    11 ms     9 ms  te-0-7-0-0-sur01.mendota.il.chicago.comcast.net

[69.139.235.61]

  5    19 ms    31 ms    19 ms  te-0-2-0-0-ar01.area4.il.chicago.comcast.net [68

.85.176.86]

  6    18 ms    19 ms    19 ms  he-3-11-0-0-cr01.350ecermak.il.ibone.comcast.net

 [68.86.90.13]

  7    22 ms    23 ms    19 ms  pos-1-0-0-0-pe01.350ecermak.il.ibone.comcast.net

 [68.86.86.34]

  8    18 ms    19 ms    18 ms  xe-4-0-1.chi11.ip4.tinet.net [77.67.71.145]

  9    20 ms    20 ms     *     gtt-gw.ip4.tinet.net [77.67.70.166]

 10    19 ms    18 ms    18 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]

 11    20 ms    17 ms    19 ms  8.9.37.132

 

Trace complete.

 

C:\Users\James>tracert 68.232.164.55

 

Tracing route to 68.232.164.55.choopa.net [68.232.164.55]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  192.168.1.1

  2    29 ms    25 ms    15 ms  98.212.96.1

  3    11 ms    10 ms     9 ms  68.85.178.237

  4     9 ms     9 ms     9 ms  te-0-7-0-0-sur01.mendota.il.chicago.comcast.net

[69.139.235.61]

  5    19 ms    19 ms    19 ms  te-0-2-0-2-ar01.area4.il.chicago.comcast.net [68

.86.188.246]

  6    22 ms    23 ms    23 ms  he-3-14-0-0-cr01.350ecermak.il.ibone.comcast.net

 [68.86.94.125]

  7    20 ms    20 ms    21 ms  pos-1-4-0-0-pe01.350ecermak.il.ibone.comcast.net

 [68.86.86.162]

  8    20 ms    18 ms    18 ms  xe-4-0-1.chi11.ip4.tinet.net [77.67.71.145]

  9    55 ms    51 ms    49 ms  xe-3-1-0.dal33.ip4.tinet.net [89.149.180.246]

 10    53 ms    51 ms    52 ms  gtt-gw.ip4.tinet.net [173.241.130.154]

 11    54 ms     *       51 ms  ae0-11g.ar1.dfw1.us.nlayer.net [198.47.104.68]

 12    51 ms    53 ms    51 ms  as20473.xe-7-0-0.ar1.dfw1.us.nlayer.net [69.31.6

3.238]

 13    50 ms    51 ms    51 ms  68.232.164.55.choopa.net [68.232.164.55]

 

Trace complete.

 

C:\Users\James>

 

As you can see, traceroute doesn't work, tracert was the only command win7 recognized.

[TBB]

Here you go:

 

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.



Tracing route to 8.9.37.132 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     8 ms     4 ms     5 ms  L100.NWRKNJ-VFTTP-118.verizon-gni.net [173.70.20
5.1]
  3     9 ms     7 ms     9 ms  G0-14-4-6.NWRKNJ-LCR-22.verizon-gni.net [130.81.
189.238]
  4     8 ms     9 ms     9 ms  ae2-0.NWRK-BB-RTR2.verizon-gni.net [130.81.209.1
70]
  5    12 ms    12 ms    12 ms  0.xe-4-1-0.BR3.NYC4.ALTER.NET [152.63.24.137]
  6     9 ms     9 ms     9 ms  204.255.168.66
  7     9 ms     9 ms    39 ms  ae-2.r23.nycmny01.us.bb.gin.ntt.net [129.250.4.1
48]
  8    34 ms    37 ms    42 ms  ae-3.r20.chcgil09.us.bb.gin.ntt.net [129.250.2.4
0]
  9    33 ms    34 ms    34 ms  ae-1.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.1
46]
 10    30 ms    27 ms    29 ms  xe-0-6-0-3.r06.chcgil09.us.ce.gin.ntt.net [128.2
42.186.130]
 11    32 ms    27 ms    27 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
 12    26 ms    27 ms    34 ms  8.9.37.132

Trace complete.

 

Microsoft Windows XP [Version 5.1.2600]
© Copyright 1985-2001 Microsoft Corp.



Tracing route to 68.232.164.55.choopa.net [68.232.164.55]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2     4 ms     4 ms     4 ms  L100.NWRKNJ-VFTTP-118.verizon-gni.net [173.70.20
5.1]
  3     6 ms     7 ms     7 ms  G0-14-4-6.NWRKNJ-LCR-21.verizon-gni.net [130.81.
189.236]
  4     5 ms     7 ms     5 ms  ae0-0.NWRK-BB-RTR1.verizon-gni.net [130.81.209.1
54]
  5    12 ms     9 ms    10 ms  0.xe-10-0-0.BR3.NYC4.ALTER.NET [152.63.24.109]
  6    12 ms    12 ms    12 ms  204.255.168.66
  7     9 ms     9 ms     9 ms  ae-2.r23.nycmny01.us.bb.gin.ntt.net [129.250.4.1
48]
  8    53 ms    57 ms    54 ms  ae-5.r20.asbnva02.us.bb.gin.ntt.net [129.250.2.1
83]
  9    51 ms    54 ms    55 ms  ae-3.r20.dllstx09.us.bb.gin.ntt.net [129.250.3.5
1]
 10    51 ms    52 ms    52 ms  ae-2.r07.dllstx09.us.bb.gin.ntt.net [129.250.3.6
7]
 11    52 ms    52 ms    52 ms  ae9.ar1.dfw1.us.nlayer.net [69.31.63.168]
 12    46 ms    53 ms    47 ms  as20473.xe-7-0-0.ar1.dfw1.us.nlayer.net [69.31.6
3.238]
 13    45 ms    49 ms    48 ms  68.232.164.55.choopa.net [68.232.164.55]

Trace complete.


 

[Ruggerxi]

Well we have some that will get a better ping and others will get a worse ping. What I'm gonna do is open up a server is Dallas for a month and let people connect and play there and see if this is a good compromise for everyone that plays on the server.

 

Admins let me know what the group wants to do by the end of next month.

[little_old_man]

Rugger,

 

Will there be a 3rd server or are you going to replace one of the current servers for a month?

[Ruggerxi]

I'm actually getting a test server for a couple days to test out first. I will post details once I have them.

[FunkyChickn]

[MrCrowe]

Chicago:

 

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\i7>tracert 8.9.37.132

Tracing route to 8.9.37.132 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     5 ms     5 ms     4 ms  L100.LSANCA-VFTTP-72.verizon-gni.net [96.229.202
.1]
  3    30 ms     7 ms     7 ms  G0-9-4-1.LSANCA-LCR-21.verizon-gni.net [130.81.1
88.126]
  4     6 ms     6 ms     6 ms  ae0-0.LAX01-BB-RTR1.verizon-gni.net [130.81.209.
246]
  5     7 ms     6 ms     7 ms  0.xe-4-1-0.BR1.LAX15.ALTER.NET [152.63.112.229]

  6     7 ms     7 ms     7 ms  ae-7.r05.lsanca03.us.bb.gin.ntt.net [129.250.8.8
5]
  7     7 ms     6 ms     7 ms  ae-2.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.2
29]
  8    56 ms    41 ms    73 ms  ae-4.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.1
69]
  9    39 ms    39 ms    43 ms  ae-0.r21.dllstx09.us.bb.gin.ntt.net [129.250.2.5
9]
 10    69 ms    69 ms    71 ms  ae-1.r23.dllstx09.us.bb.gin.ntt.net [129.250.5.2
42]
 11   101 ms    74 ms    77 ms  ae-4.r21.chcgil09.us.bb.gin.ntt.net [129.250.2.2
01]
 12    66 ms    66 ms    66 ms  ae-2.r06.chcgil09.us.bb.gin.ntt.net [129.250.4.2
02]
 13    78 ms    75 ms    76 ms  xe-0-6-0-3.r06.chcgil09.us.ce.gin.ntt.net [128.2
42.186.130]
 14    74 ms    74 ms    77 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]
 15    73 ms    74 ms    73 ms  8.9.37.132

Trace complete.
 

Dallas:

 

Microsoft Windows [Version 6.1.7601]
Copyright © 2009 Microsoft Corporation.  All rights reserved.

C:\Users\i7>tracert 68.232.164.55

Tracing route to 68.232.164.55.choopa.net [68.232.164.55]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  Wireless_Broadband_Router.home [192.168.1.1]
  2     5 ms     5 ms     4 ms  L100.LSANCA-VFTTP-72.verizon-gni.net [96.229.202
.1]
  3     7 ms     8 ms     6 ms  G0-9-4-0.LSANCA-LCR-22.verizon-gni.net [130.81.1
05.4]
  4     6 ms     6 ms     7 ms  so-6-0-0-0.LAX01-BB-RTR2.verizon-gni.net [130.81
.29.126]
  5     7 ms     9 ms     7 ms  0.xe-11-1-0.BR1.LAX15.ALTER.NET [152.63.114.113]

  6     7 ms     8 ms     7 ms  ae-7.r05.lsanca03.us.bb.gin.ntt.net [129.250.8.8
5]
  7    18 ms     7 ms    14 ms  ae-2.r20.lsanca03.us.bb.gin.ntt.net [129.250.2.2
29]
  8    43 ms    46 ms    39 ms  ae-4.r20.dllstx09.us.bb.gin.ntt.net [129.250.2.1
69]
  9    43 ms    39 ms    39 ms  ae-2.r07.dllstx09.us.bb.gin.ntt.net [129.250.3.6
7]
 10    49 ms    45 ms    46 ms  ae9.ar1.dfw1.us.nlayer.net [69.31.63.168]
 11    43 ms    41 ms    41 ms  as20473.xe-7-0-0.ar1.dfw1.us.nlayer.net [69.31.6
3.238]
 12    43 ms    41 ms    41 ms  68.232.164.55.choopa.net [68.232.164.55]

Trace complete

[riverkwai]

Pinging 8.9.37.132 with 32 bytes of data:

Reply from 8.9.37.132: bytes=32 time=37ms TTL=122

Reply from 8.9.37.132: bytes=32 time=37ms TTL=122

Reply from 8.9.37.132: bytes=32 time=36ms TTL=122

Reply from 8.9.37.132: bytes=32 time=37ms TTL=122

 

Ping statistics for 8.9.37.132:

    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

    Minimum = 36ms, Maximum = 37ms, Average = 36ms

 

 

 

Tracing route to 8.9.37.132 over a maximum of 30 hops

 

 

  4    36 ms    36 ms    36 ms  ae0.gw1-chi.bb.allstream.net [199.212.160.202]

  5    37 ms    37 ms    36 ms  equinix.xe-1-3-0.cr2.ord1.us.nlayer.net [206.223

.119.61]

  6     *       37 ms    37 ms  ae2-30g.ar1.ord1.us.nlayer.net [69.31.111.138]

  7    37 ms    37 ms    37 ms  tge8-1.ar2.ord1.us.scnet.net [69.31.111.10]

  8    37 ms    37 ms    37 ms  8.9.37.132

 

 

Then when I go on the server my ping is 50 ms

Edited August 31, 2013 by riverkwai