BulletProof Nerds Gaming Community
May 22, 2012, 12:37:19 AM *
Welcome, Guest. Please login or register.

Login with username, password and session length
News: TO POST ON THE FORUMS YOU MUST REGISTER ON THE BPN HOMEPAGE, ONCE YOU ARE LOGGED IN THERE, IT AUTOMATICALLY LOGS YOU INTO THE FORUMS AS WELL.  IF YOU STILL CAN'T POST THEN LOG OUT OF THE WEBSITE AND LOG BACK IN, THEN COME BACK TO THE FORUMS.
 
   Home   Help BPN HOMEPAGE Search Login Register  
BulletProof Nerds Gaming Community > Computer Related > PC Help & Support > IMPORTANT: Need Everyone's Help
Pages: 1   Go Down
« previous next »
  Print  
Author Topic: IMPORTANT: Need Everyone's Help  (Read 1982 times)
0 Members and 2 Guests are viewing this topic.
Schlup
Master Admin
1000 POSTS CLUB!!!
*
*

BPN Props: 1226
Offline Offline

Posts: 6664



WWW Awards
« on: October 21, 2009, 02:54:54 AM »
So here's the deal, we are thinking about moving to a new datacenter with the server box the community has purchased.  The datacenter would be in Kansas City, MO which is smack dab in the middle of the United States.  Our current datacenter is in Dallas, TX.  However, I want to get a feel on what everybodies pings are going to look like to this datacenter.  This includes all members, recruits, Junior Division, and regulars on the servers.

How to do this:

XP Users:
Go to Start, then to All Programs, then to Accessories, then click on Command Prompt (a little black box that looks like MS-DOS should pop up)
Type in the following: ping 208.94.241.15

It will then ping that IP address (4) times.  On the very last line you will see "Minimum = XXms, Maximum = XXms, Average = XXms) where XX represents the ping times that you get.  Now I want you to post those times in this forum topic, also if you could repeat (3) times that would be even better and post all the numbers you get.  I need to know what you are currently getting as well.  Do the above with IP 64.182.65.69


Vista & Windows 7 Users:
Click on the Start globe in the lower left hand corner, then type "cmd" without the quotes and hit enter. (a little black box that looks like MS-DOS should pop up)
Type in the following: ping 208.94.241.15

It will then ping that IP address (4) times.  On the very last line you will see "Minimum = XXms, Maximum = XXms, Average = XXms) where XX represents the ping times that you get.  Now I want you to post those times in this forum topic, also if you could repeat (3) times that would be even better and post all the numbers you get.  I need to know what you are currently getting as well.  Do the above with IP 64.182.65.69

P.S. If anybody has any problems let me know and I'll help you out.

Bonus Mission:  If you'd like you can also run a traceroute for me as well.  To do this instead of typing: "ping 208.94.241.15" you will type "tracert 208.94.241.15" without the quotes.  Then right click in the window when it is done running and right-click the window and select "Select All" then hit enter on your keyboard and paste (Ctrl+V) into a reply on this forum topic.
« Last Edit: October 21, 2009, 01:27:41 PM by Schlup »
Schlup
Master Admin
1000 POSTS CLUB!!!
*
*

BPN Props: 1226
Offline Offline

Posts: 6664



WWW Awards
« Reply #1 on: October 21, 2009, 03:00:21 AM »
Minimum = 40ms, Maximum = 50ms, Average = 46ms

Minimum = 37ms, Maximum = 50ms, Average = 45ms

Minimum = 38ms, Maximum = 75ms, Average = 51ms


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

C:\Users\Schlup>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:
Reply from 208.94.241.15: bytes=32 time=47ms TTL=50
Reply from 208.94.241.15: bytes=32 time=60ms TTL=50
Reply from 208.94.241.15: bytes=32 time=51ms TTL=50
Reply from 208.94.241.15: bytes=32 time=48ms TTL=50

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



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

C:\Users\Schlup>tracert 208.94.241.15

Tracing route to 208.94.241.15 over a maximum of 30 hops

  1    10 ms     7 ms     7 ms  10.24.206.1
  2    11 ms    15 ms     9 ms  12-215-12-201.client.mchsi.com [12.215.12.201]
  3    19 ms    19 ms    18 ms  12-215-0-42.client.mchsi.com [12.215.0.42]
  4    25 ms    28 ms    25 ms  cr2.sl9mo.ip.att.net [12.122.142.142]
  5    25 ms    25 ms    25 ms  cr2.sl9mo.ip.att.net [12.123.140.169]
  6    25 ms    34 ms    32 ms  cr2.cgcil.ip.att.net [12.122.2.21]
  7    26 ms    25 ms    26 ms  ggr3.cgcil.ip.att.net [12.122.132.13]
  8    27 ms    28 ms    25 ms  192.205.33.194
  9    26 ms    25 ms    25 ms  te4-1.mpd01.ord03.atlas.cogentco.com [154.54.3.2
42]
 10    25 ms    25 ms    31 ms  vl3489.mpd01.ord01.atlas.cogentco.com [154.54.5.
17]
 11    37 ms    37 ms    36 ms  te2-4.mpd01.mci01.atlas.cogentco.com [154.54.2.2
33]
 12    39 ms    37 ms    38 ms  vl3508.na31.b006290-3.mci01.atlas.cogentco.com [
38.20.45.234]
 13    36 ms    37 ms    38 ms  38.104.86.74
 14    58 ms    61 ms    62 ms  SW1.KCMODATACENTER.com [208.94.243.14]
 15    40 ms    50 ms    47 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 16    45 ms    43 ms    45 ms  208.94.241.15

Trace complete.

C:\Users\Schlup>
Grimorly
Member
50 POSTS CLUB
*

BPN Props: 0
Offline Offline

Posts: 63


Awards
« Reply #2 on: October 21, 2009, 08:26:55 AM »
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Robert>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:
Reply from 208.94.241.15: bytes=32 time=88ms TTL=47
Reply from 208.94.241.15: bytes=32 time=62ms TTL=47
Reply from 208.94.241.15: bytes=32 time=81ms TTL=47
Reply from 208.94.241.15: bytes=32 time=65ms TTL=47

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

C:\Users\Robert>
C:\Users\Robert>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:
Reply from 208.94.241.15: bytes=32 time=60ms TTL=47
Reply from 208.94.241.15: bytes=32 time=64ms TTL=47
Reply from 208.94.241.15: bytes=32 time=101ms TTL=47
Reply from 208.94.241.15: bytes=32 time=92ms TTL=47

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

C:\Users\Robert>
C:\Users\Robert>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:
Reply from 208.94.241.15: bytes=32 time=66ms TTL=47
Reply from 208.94.241.15: bytes=32 time=74ms TTL=47
Reply from 208.94.241.15: bytes=32 time=58ms TTL=47
Reply from 208.94.241.15: bytes=32 time=62ms TTL=47

Ping statistics for 208.94.241.15:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 58ms, Maximum = 74ms, Average = 65ms
CoCoCountyKiller
Guest
« Reply #3 on: October 21, 2009, 08:56:04 AM »
C:\Documents and Settings\CoCo>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:

Reply from 208.94.241.15: bytes=32 time=396ms TTL=49
Reply from 208.94.241.15: bytes=32 time=345ms TTL=49
Reply from 208.94.241.15: bytes=32 time=375ms TTL=49
Reply from 208.94.241.15: bytes=32 time=102ms TTL=49

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

C:\Documents and Settings\CoCo>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:

Reply from 208.94.241.15: bytes=32 time=96ms TTL=49
Reply from 208.94.241.15: bytes=32 time=114ms TTL=49
Reply from 208.94.241.15: bytes=32 time=113ms TTL=49
Reply from 208.94.241.15: bytes=32 time=99ms TTL=49

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

C:\Documents and Settings\CoCo>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:

Reply from 208.94.241.15: bytes=32 time=109ms TTL=49
Reply from 208.94.241.15: bytes=32 time=132ms TTL=49
Reply from 208.94.241.15: bytes=32 time=123ms TTL=49
Reply from 208.94.241.15: bytes=32 time=106ms TTL=49

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

C:\Documents and Settings\CoCo>tracert 208.94.241.15

Tracing route to 208.94.241.15 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2     8 ms     9 ms     9 ms  te-8-4-ur01.walnutcreek.ca.sfba.comcast.net [68.
85.190.113]
  3     9 ms     9 ms     9 ms  te-8-4-ur03.walnutcreek.ca.sfba.comcast.net [68.
87.226.93]
  4    13 ms    14 ms    14 ms  68.85.154.194
  5    15 ms    16 ms    16 ms  pos-1-8-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.91.229]
  6    15 ms    18 ms    16 ms  te3-3.mpd01.sjc04.atlas.cogentco.com [154.54.11.
105]
  7    16 ms    16 ms    16 ms  te3-1.mpd01.sfo01.atlas.cogentco.com [154.54.28.
81]
  8   108 ms   235 ms   228 ms  te8-3.mpd01.mci01.atlas.cogentco.com [154.54.6.1
66]
  9    77 ms    80 ms    78 ms  vl3508.na31.b006290-3.mci01.atlas.cogentco.com [
38.20.45.234]
 10    75 ms   468 ms    75 ms  38.104.86.74
 11   112 ms   107 ms   127 ms  SW1.KCMODATACENTER.COM [208.94.243.14]
 12   123 ms   118 ms   146 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 13    92 ms   102 ms   108 ms  208.94.241.15

Trace complete.

C:\Documents and Settings\CoCo>ping 64.182.65.69

Pinging 64.182.65.69 with 32 bytes of data:

Reply from 64.182.65.69: bytes=32 time=63ms TTL=51
Reply from 64.182.65.69: bytes=32 time=61ms TTL=51
Reply from 64.182.65.69: bytes=32 time=61ms TTL=51
Reply from 64.182.65.69: bytes=32 time=65ms TTL=51

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

C:\Documents and Settings\CoCo>tracert 64.182.65.69

Tracing route to 69-65-182-64.cust.propagation.net [64.182.65.69]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     9 ms     7 ms     9 ms  te-8-4-ur01.walnutcreek.ca.sfba.comcast.net [68.
85.190.113]
  3     7 ms     9 ms     9 ms  te-8-4-ur03.walnutcreek.ca.sfba.comcast.net [68.
87.226.93]
  4    14 ms    13 ms    26 ms  68.85.154.194
  5    15 ms    16 ms    16 ms  pos-1-8-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.91.229]
  6    15 ms    18 ms    16 ms  er1-tengig3-4.sanjoseequinix.savvis.net [208.173
.53.137]
  7    18 ms    16 ms    21 ms  cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.7
0.200.198]
  8    60 ms    57 ms    60 ms  cr1-tengig0-7-0-0.dallas.savvis.net [204.70.196.
213]
  9    64 ms    61 ms    63 ms  msr1-tengig0-0-0-0.dallas.savvis.net [204.70.196
.202]
 10    58 ms    59 ms    57 ms  er1-ge-3-0-6.dallas.savvis.net [204.70.202.61]
 11    60 ms    60 ms    59 ms  federal-home-loan.Dallas.savvis.net [208.172.135
.2]
 12    60 ms    60 ms    64 ms  64.182.192.41
 13    61 ms    62 ms    63 ms  69-65-182-64.cust.propagation.net [64.182.65.69]


Trace complete.

C:\Documents and Settings\CoCo>
« Last Edit: October 21, 2009, 10:39:42 PM by CoCoCountyKiller »
Grimorly
Member
50 POSTS CLUB
*

BPN Props: 0
Offline Offline

Posts: 63


Awards
« Reply #4 on: October 21, 2009, 09:05:15 AM »
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Robert>tracert 208.94.241.15

Tracing route to 208.94.241.15 over a maximum of 30 hops

  1     2 ms     1 ms     1 ms  72-161-60-205.dyn.centurytel.net [72.161.60.205]

  2     6 ms     6 ms     4 ms  72-161-60-2.dyn.centurytel.net [72.161.60.2]
  3     6 ms     6 ms     4 ms  GE-0-0-0-j1.rt.wnvl.centurytel.net [66.112.11.73
]
  4     5 ms     7 ms     4 ms  host.lightcore.net [66.211.51.177]
  5    12 ms    12 ms    11 ms  bb-chcgilwu-jx9-02-xe-1-1-0.core.lightcore.net [
206.51.69.46]
  6    14 ms    14 ms    11 ms  207.88.184.205.ptr.us.xo.net [207.88.184.205]
  7    15 ms    14 ms    14 ms  65.106.6.249.ptr.us.xo.net [65.106.6.249]
  8    31 ms    31 ms    29 ms  gi2-32.mpd01.ord03.atlas.cogentco.com [154.54.12
.229]
  9    33 ms    32 ms    31 ms  te2-4.mpd01.ord01.atlas.cogentco.com [154.54.6.2
05]
 10    30 ms    29 ms    32 ms  te8-4.mpd01.mci01.atlas.cogentco.com [66.28.4.18
5]
 11    36 ms    34 ms    34 ms  vl3508.na31.b006290-3.mci01.atlas.cogentco.com [
38.20.45.234]
 12    30 ms   419 ms    29 ms  38.104.86.74
 13    52 ms    49 ms    52 ms  SW1.KCMODATACENTER.com [208.94.243.14]
 14    61 ms    41 ms    37 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 15    83 ms    82 ms    83 ms  208.94.241.15

Trace complete.

C:\Users\Robert>
Dark Insomniac
Member
250 POSTS CLUB
*

BPN Props: 14
Offline Offline

Posts: 442


Awards
« Reply #5 on: October 21, 2009, 11:11:52 AM »
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Owner>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:
Reply from 208.94.241.15: bytes=32 time=82ms TTL=51
Reply from 208.94.241.15: bytes=32 time=125ms TTL=51
Reply from 208.94.241.15: bytes=32 time=59ms TTL=51
Reply from 208.94.241.15: bytes=32 time=86ms TTL=51

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

C:\Users\Owner>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 208.94.241.15: bytes=32 time=60ms TTL=51
Reply from 208.94.241.15: bytes=32 time=62ms TTL=51

Ping statistics for 208.94.241.15:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
    Minimum = 60ms, Maximum = 62ms, Average = 61ms

C:\Users\Owner>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:
Request timed out.
Reply from 208.94.241.15: bytes=32 time=90ms TTL=51
Reply from 208.94.241.15: bytes=32 time=130ms TTL=51
Reply from 208.94.241.15: bytes=32 time=130ms TTL=51

Ping statistics for 208.94.241.15:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 90ms, Maximum = 130ms, Average = 116ms

C:\Users\Owner>tracert 208.94.241.15

Tracing route to 208.94.241.15 over a maximum of 30 hops

  1    11 ms    19 ms    13 ms  CPE-72-131-32-1.wi.res.rr.com [72.131.32.1]
  2    12 ms    13 ms    12 ms  gig2-1.milwwignfl-ybr2.wi.rr.com [24.160.225.77]

  3    13 ms    15 ms    12 ms  srp10-0.milwwirtco-rtr1.wi.rr.com [24.160.224.1]

  4    15 ms    15 ms    20 ms  tge1-0-0.chcgil3-rtr0.mwrtn.rr.com [24.160.229.1
93]
  5   689 ms    20 ms    15 ms  66.109.6.206
  6    13 ms    23 ms    15 ms  ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
  7    17 ms    13 ms    15 ms  te9-2.ccr02.ord03.atlas.cogentco.com [154.54.11.
145]
  8    16 ms    26 ms    21 ms  te1-1.ccr02.ord01.atlas.cogentco.com [154.54.29.
21]
  9    25 ms    15 ms    25 ms  te9-1.ccr01.ord01.atlas.cogentco.com [66.28.4.38
]
 10    39 ms    40 ms    50 ms  te3-4.mpd01.mci01.atlas.cogentco.com [154.54.7.1
85]
 11    42 ms    44 ms    39 ms  vl3508.na31.b006290-3.mci01.atlas.cogentco.com [
38.20.45.234]
 12     *      348 ms    40 ms  38.104.86.74
 13    59 ms    61 ms    96 ms  SW1.KCMODATACENTER.com [208.94.243.14]
 14    62 ms   130 ms    82 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 15    85 ms    84 ms    84 ms  208.94.241.15

Trace complete.
64m3
100 POSTS CLUB
*
*

BPN Props: 6
Offline Offline

Posts: 241



Awards
« Reply #6 on: October 21, 2009, 11:51:37 AM »
Unfortunately us NorCal boys are getting timed out on 1st 2 requests, ping results are identical for 5x tries.

Pinging 208.94.241.15 with 32 bytes of data:
Reply from 208.94.241.15: bytes=32 time=113ms TTL=47
Reply from 208.94.241.15: bytes=32 time=116ms TTL=47
Reply from 208.94.241.15: bytes=32 time=158ms TTL=47
Reply from 208.94.241.15: bytes=32 time=153ms TTL=47

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



Pinging 208.94.241.15 with 32 bytes of data:
Reply from 208.94.241.15: bytes=32 time=113ms TTL=47
Reply from 208.94.241.15: bytes=32 time=116ms TTL=47
Reply from 208.94.241.15: bytes=32 time=158ms TTL=47
Reply from 208.94.241.15: bytes=32 time=153ms TTL=47

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





Tracing route to 208.94.241.15 over a maximum of 30 hops

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     9 ms     8 ms     9 ms  68.85.216.61
  4    11 ms     9 ms     9 ms  68.85.154.213
  5    12 ms    13 ms    13 ms  pos-1-6-0-0-cr01.sanjose.ca.ibone.comcast.net [6
8.86.90.157]
  6    14 ms    16 ms    14 ms  te3-3.mpd01.sjc04.atlas.cogentco.com [154.54.11.
105]
  7    15 ms    14 ms    14 ms  te8-2.mpd01.sfo01.atlas.cogentco.com [154.54.2.1
65]
  8    81 ms    81 ms    80 ms  te3-3.mpd01.mci01.atlas.cogentco.com [154.54.2.2
09]
  9    81 ms    82 ms    84 ms  vl3808.na31.b006290-3.mci01.atlas.cogentco.com [
38.20.45.238]
 10    81 ms    88 ms    80 ms  38.104.86.74
 11   156 ms   116 ms   157 ms  SW1.KCMODATACENTER.com [208.94.243.14]
 12   152 ms   209 ms   175 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 13   158 ms   145 ms   176 ms  208.94.241.15

Trace complete.
« Last Edit: October 21, 2009, 11:53:42 AM by 64m3 »
Player Info
Schlup
Master Admin
1000 POSTS CLUB!!!
*
*

BPN Props: 1226
Offline Offline

Posts: 6664



WWW Awards
« Reply #7 on: October 21, 2009, 12:03:54 PM »
Ok peeps, I should have asked for what you are currently getting as well.  Do the above with IP 64.182.65.69

P.S. 64m3, did you not talk to your ISP yet?  You are still having issues locally.
Dark Insomniac
Member
250 POSTS CLUB
*

BPN Props: 14
Offline Offline

Posts: 442


Awards
« Reply #8 on: October 21, 2009, 12:52:29 PM »
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

C:\Users\Owner>ping 64.182.65.69

Pinging 64.182.65.69 with 32 bytes of data:
Reply from 64.182.65.69: bytes=32 time=54ms TTL=45
Reply from 64.182.65.69: bytes=32 time=61ms TTL=45
Reply from 64.182.65.69: bytes=32 time=62ms TTL=45
Reply from 64.182.65.69: bytes=32 time=56ms TTL=45

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

C:\Users\Owner>ping 64.182.65.69

Pinging 64.182.65.69 with 32 bytes of data:
Reply from 64.182.65.69: bytes=32 time=62ms TTL=45
Reply from 64.182.65.69: bytes=32 time=56ms TTL=45
Reply from 64.182.65.69: bytes=32 time=57ms TTL=45
Reply from 64.182.65.69: bytes=32 time=63ms TTL=45

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

C:\Users\Owner>ping 64.182.65.69

Pinging 64.182.65.69 with 32 bytes of data:
Request timed out.
Reply from 64.182.65.69: bytes=32 time=64ms TTL=45
Reply from 64.182.65.69: bytes=32 time=64ms TTL=45
Request timed out.

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

C:\Users\Owner>tracert 64.182.65.69

Tracing route to 69-65-182-64.cust.propagation.net [64.182.65.69]
over a maximum of 30 hops:

  1    15 ms    13 ms    14 ms  CPE-72-131-32-1.wi.res.rr.com [72.131.32.1]
  2    14 ms    20 ms    12 ms  gig2-1.milwwignfl-ybr2.wi.rr.com [24.160.225.77]

  3    15 ms    14 ms    14 ms  srp10-0.milwwirtco-rtr1.wi.rr.com [24.160.224.1]

  4    21 ms    19 ms    15 ms  tge2-0-0.chcgil3-rtr0.mwrtn.rr.com [24.160.229.1
97]
  5     *        *        *     Request timed out.
  6    16 ms    20 ms    15 ms  ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
  7    17 ms    39 ms    15 ms  216.156.72.5.ptr.us.xo.net [216.156.72.5]
  8    21 ms    18 ms    16 ms  207.88.13.2.ptr.us.xo.net [207.88.13.2]
  9    46 ms    42 ms    43 ms  207.88.14.10.ptr.us.xo.net [207.88.14.10]
 10    54 ms    55 ms    54 ms  207.88.185.30.ptr.us.xo.net [207.88.185.30]
 11    58 ms    58 ms    57 ms  64.182.192.41
 12    63 ms    58 ms    64 ms  69-65-182-64.cust.propagation.net [64.182.65.69]


Trace complete.

C:\Users\Owner>
HashBrowny
Member
100 POSTS CLUB
*

BPN Props: 10
Offline Offline

Posts: 109



Awards
« Reply #9 on: October 21, 2009, 01:10:55 PM »
Minimum = 128ms, Maximum = 319ms, Average = 202ms
Minimum = 81ms, Maximum = 101ms, Average = 93ms
Minimum = 105ms, Maximum = 147, Average = 119ms

Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.
C:\Documents and Settings\Administrator>ping 208.94.241.15
Pinging 208.94.241.15 with 32 bytes of data:

Reply from 208.94.241.15: bytes=32 time=128ms TTL=51
Reply from 208.94.241.15: bytes=32 time=184ms TTL=51
Reply from 208.94.241.15: bytes=32 time=177ms TTL=51
Reply from 208.94.241.15: bytes=32 time=319ms TTL=51

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

TRACERT:
Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\Administrator>tracert 208.94.241.15

Tracing route to 208.94.241.15 over a maximum of 30 hops

  1    12 ms    28 ms    11 ms  cpe-75-81-208-1.we.res.rr.com [75.81.208.1]
  2    12 ms    12 ms    12 ms  fa9-21.owboky-rtr1.natwky.rr.com [65.28.202.69]

  3    13 ms    12 ms    16 ms  ae-10.owboky-rtr2.natwky.rr.com [65.28.202.46]
  4    45 ms    44 ms    49 ms  so-4-0-1.chcgill3-rtr1.kc.rr.com [65.28.202.53]

  5    44 ms    47 ms    49 ms  ae-5-0.cr0.chi30.tbone.rr.com [66.109.6.112]
  6    95 ms    52 ms    47 ms  ae-1-0.pr0.chi10.tbone.rr.com [66.109.6.155]
 
  7    47 ms    49 ms    48 ms  te9-2.ccr02.ord03.atlas.cogentco.com [154.54.11.145]
  8    47 ms    47 ms    46 ms  vl3499.mpd02.ord01.atlas.cogentco.com [154.54.5.9]
 
  9    45 ms    50 ms    47 ms  te3-1.ccr02.mci01.atlas.cogentco.com [154.54.3.202]
 10    45 ms    46 ms    47 ms  te7-1.mpd01.mci01.atlas.cogentco.com [154.54.24.93]
 
 11    45 ms    47 ms    47 ms  vl3508.na31.b006290-3.mci01.atlas.cogentco.com [38.20.45.234]
 12    47 ms    48 ms    45 ms  38.104.86.74
 
 13    77 ms    81 ms    79 ms  SW1.KCMODATACENTER.com [208.94.243.14]
 14   120 ms    99 ms   114 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 15   146 ms   138 ms   194 ms  208.94.241.15

Trace complete.

C:\Documents and Settings\Administrator>
64m3
100 POSTS CLUB
*
*

BPN Props: 6
Offline Offline

Posts: 241



Awards
« Reply #10 on: October 21, 2009, 01:36:44 PM »
*schlup, what should i say to my isp?
Player Info
CoCoCountyKiller
Guest
« Reply #11 on: October 21, 2009, 10:32:03 PM »
where you from 64m3?

co.co.
CoCoCountyKiller
Guest
« Reply #12 on: October 21, 2009, 10:38:06 PM »
see above post

co.co.
« Last Edit: October 21, 2009, 10:43:21 PM by CoCoCountyKiller »
Schlup
Master Admin
1000 POSTS CLUB!!!
*
*

BPN Props: 1226
Offline Offline

Posts: 6664



WWW Awards
« Reply #13 on: October 22, 2009, 04:42:28 AM »
Quote from: 64m3 on October 21, 2009, 01:36:44 PM
*schlup, what should i say to my isp?
Tell them exactly what is going on, tell them you are running a traceroute to a server in Dallas, TX and a different one to Kansas City, MO and the first two hops time out. (You might run the test on some other stuff too like Yahoo, Google, etc.)  Tell them it is a routing issue and you want to submit a ticket to their network operations center (NOC).
2SftKties
Guest
« Reply #14 on: October 22, 2009, 07:35:50 PM »
*************************************************************
FIRST IP TEST
*************************************************************
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Tom>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:

Reply from 208.94.241.15: bytes=32 time=71ms TTL=47
Reply from 208.94.241.15: bytes=32 time=86ms TTL=47
Reply from 208.94.241.15: bytes=32 time=84ms TTL=47
Reply from 208.94.241.15: bytes=32 time=79ms TTL=47

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

C:\Documents and Settings\Tom>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:

Reply from 208.94.241.15: bytes=32 time=83ms TTL=47
Reply from 208.94.241.15: bytes=32 time=76ms TTL=47
Reply from 208.94.241.15: bytes=32 time=73ms TTL=47
Reply from 208.94.241.15: bytes=32 time=73ms TTL=47

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

C:\Documents and Settings\Tom>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:

Reply from 208.94.241.15: bytes=32 time=81ms TTL=47
Reply from 208.94.241.15: bytes=32 time=74ms TTL=47
Reply from 208.94.241.15: bytes=32 time=72ms TTL=47
Reply from 208.94.241.15: bytes=32 time=71ms TTL=47

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

C:\Documents and Settings\Tom>

C:\Documents and Settings\Tom>tracert 208.94.241.15

Tracing route to 208.94.241.15 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     6 ms     9 ms     6 ms  73.98.110.1
  3     7 ms     7 ms    11 ms  ge-4-45-ur01.burien.wa.seattle.comcast.net [68.87.206.49]
  4     9 ms     7 ms     7 ms  te-0-1-0-0-ar01.burien.wa.seattle.comcast.net [68.86.96.125]
  5    11 ms     8 ms    11 ms  be-40-ar01.seattle.wa.seattle.comcast.net [68.85.240.94]
  6    10 ms    10 ms    11 ms  pos-0-5-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.213]
  7    11 ms    11 ms    12 ms  pos-0-8-0-0-cr01.portland.or.ibone.comcast.net [68.86.85.206]
  8    24 ms    25 ms    23 ms  pos-1-15-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.197]
  9    27 ms    27 ms    27 ms  pos-0-8-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.78]
 10    29 ms     *       27 ms  te3-3.mpd01.sjc04.atlas.cogentco.com [154.54.11.105]
 11    27 ms    27 ms    28 ms  te3-1.mpd01.sfo01.atlas.cogentco.com [154.54.28.81]
 12    72 ms    76 ms    69 ms  te4-1.mpd01.mci01.atlas.cogentco.com [154.54.6.33]
 13    73 ms    71 ms    74 ms  vl3508.na31.b006290-3.mci01.atlas.cogentco.com [38.20.45.234]
 14    70 ms    70 ms    70 ms  38.104.86.74
 15    90 ms    78 ms    89 ms  SW1.KCMODATACENTER.com [208.94.243.14]
 16    93 ms    71 ms    79 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 17    72 ms    72 ms    72 ms  208.94.241.15

Trace complete.

C:\Documents and Settings\Tom>

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

C:\Documents and Settings\Tom>ping 64.182.65.69

Pinging 64.182.65.69 with 32 bytes of data:

Reply from 64.182.65.69: bytes=32 time=72ms TTL=50
Reply from 64.182.65.69: bytes=32 time=72ms TTL=50
Reply from 64.182.65.69: bytes=32 time=75ms TTL=50
Reply from 64.182.65.69: bytes=32 time=72ms TTL=50

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

C:\Documents and Settings\Tom>ping 64.182.65.69

Pinging 64.182.65.69 with 32 bytes of data:

Reply from 64.182.65.69: bytes=32 time=78ms TTL=50
Reply from 64.182.65.69: bytes=32 time=71ms TTL=50
Reply from 64.182.65.69: bytes=32 time=72ms TTL=50
Reply from 64.182.65.69: bytes=32 time=72ms TTL=50

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

C:\Documents and Settings\Tom>ping 64.182.65.69

Pinging 64.182.65.69 with 32 bytes of data:

Reply from 64.182.65.69: bytes=32 time=72ms TTL=50
Reply from 64.182.65.69: bytes=32 time=71ms TTL=50
Reply from 64.182.65.69: bytes=32 time=72ms TTL=50
Reply from 64.182.65.69: bytes=32 time=71ms TTL=50

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

C:\Documents and Settings\Tom>tracert 64.182.65.69

Tracing route to 69-65-182-64.cust.propagation.net [64.182.65.69]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.0.1
  2     8 ms     7 ms     7 ms  73.98.110.1
  3     6 ms     6 ms     7 ms  ge-4-45-ur01.burien.wa.seattle.comcast.net [68.87.206.49]
  4     6 ms    19 ms     6 ms  te-9-3-ur02.burien.wa.seattle.comcast.net [68.86.96.122]
  5     7 ms     7 ms     7 ms  te-0-9-0-0-ar01.seattle.wa.seattle.comcast.net [68.86.96.169]
  6    10 ms    11 ms     9 ms  pos-0-5-0-0-cr01.seattle.wa.ibone.comcast.net [68.86.90.213]
  7    11 ms    11 ms    12 ms  pos-0-8-0-0-cr01.portland.or.ibone.comcast.net [68.86.85.206]
  8    26 ms    24 ms    23 ms  pos-1-15-0-0-cr01.sacramento.ca.ibone.comcast.net [68.86.85.197]
  9    31 ms    27 ms    27 ms  pos-0-8-0-0-cr01.sanjose.ca.ibone.comcast.net [68.86.85.78]
 10    27 ms    27 ms    27 ms  er1-tengig3-4.sanjoseequinix.savvis.net [208.173.53.137]
 11    32 ms    35 ms    36 ms  cr1-tenge-0-3-5-0.sanfrancisco.savvis.net [204.70.200.198]
 12    69 ms    67 ms    71 ms  cr2-pos-0-3-2-0.dallas.savvis.net [204.70.194.54]
 13    72 ms    71 ms    76 ms  msr1-tengig0-3-0-0.dallas.savvis.net [204.70.196.206]
 14    69 ms    69 ms    68 ms  er1-ge-3-0-0.dallas.savvis.net [204.70.203.113]
 15    71 ms    70 ms    70 ms  federal-home-loan.Dallas.savvis.net [208.172.135.2]
 16    71 ms    71 ms    70 ms  64.182.192.41
 17    71 ms    71 ms    72 ms  69-65-182-64.cust.propagation.net [64.182.65.69]

Trace complete.

C:\Documents and Settings\Tom>
K_Templar
Guest
« Reply #15 on: October 23, 2009, 10:16:47 PM »
C:\Users\Kris>ping 64.182.65.69

Pinging 64.182.65.69 with 32 bytes of data:
Reply from 64.182.65.69: bytes=32 time=51ms TTL=54
Reply from 64.182.65.69: bytes=32 time=28ms TTL=54
Reply from 64.182.65.69: bytes=32 time=25ms TTL=54
Reply from 64.182.65.69: bytes=32 time=29ms TTL=54

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

C:\Users\Kris>


C:\Users\Kris>ping 208.94.241.15

Pinging 208.94.241.15 with 32 bytes of data:
Reply from 208.94.241.15: bytes=32 time=56ms TTL=52
Reply from 208.94.241.15: bytes=32 time=36ms TTL=52
Reply from 208.94.241.15: bytes=32 time=35ms TTL=52
Reply from 208.94.241.15: bytes=32 time=35ms TTL=52

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

C:\Users\Kris>tracert 208.94.241.15

Tracing route to 208.94.241.15 over a maximum of 30 hops

  1     2 ms     1 ms     1 ms  192.168.1.1
  2     2 ms     1 ms     1 ms  homeportal.gateway.2wire.net [192.168.0.1]
  3    14 ms    13 ms    13 ms  adsl-70-143-47-254.dsl.tul2ok.sbcglobal.net [70.
143.47.254]
  4    13 ms    13 ms    13 ms  dist2-vlan60.tul2ok.sbcglobal.net [69.152.80.131
]
  5    13 ms    13 ms    13 ms  bb1-g5-0-0.tul2ok.sbcglobal.net [69.152.80.242]

  6    23 ms    23 ms    23 ms  ex2-p2-0.eqdltx.sbcglobal.net [151.164.240.225]

  7    23 ms    23 ms    23 ms  asn174-cogent.eqdltx.sbcglobal.net [151.164.251.
126]
  8    23 ms    23 ms    23 ms  te9-1.mpd01.dfw01.atlas.cogentco.com [66.28.4.17
3]
  9    33 ms    35 ms    32 ms  te3-2.mpd01.mci01.atlas.cogentco.com [154.54.5.2
18]
 10    39 ms    36 ms    35 ms  vl3808.na31.b006290-3.mci01.atlas.cogentco.com [
38.20.45.238]
 11    34 ms    32 ms    33 ms  38.104.86.74
 12    38 ms    37 ms    36 ms  SW1.KCMODATACENTER.COM [208.94.243.14]
 13    35 ms    34 ms    34 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 14    36 ms    44 ms    35 ms  208.94.241.15

Trace complete.
tehfunk101
Guest
« Reply #16 on: October 24, 2009, 12:01:36 AM »
did this on windows 7 64-bit home edition


C:\Users\Kyle>tracert 208.94.241.15

Tracing route to 208.94.241.15 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    14 ms    10 ms     9 ms  ip174-71-112-1.om.om.cox.net [174.71.112.1]
  3     8 ms    10 ms    23 ms  68.13.9.197
  4     9 ms    23 ms    12 ms  68.13.8.21
  5     9 ms    22 ms    10 ms  68.13.8.205
  6    10 ms    11 ms    10 ms  mtc1dsrj01-xe210.0.rd.om.cox.net [68.13.14.5]
  7    25 ms    39 ms    26 ms  dalsbbrj02-ae2.0.r2.dl.cox.net [68.1.1.243]
  8    39 ms    27 ms    26 ms  te7-1.mpd01.dfw03.atlas.cogentco.com [154.54.25.
5]
  9    24 ms    27 ms    26 ms  te3-2.mpd01.dfw01.atlas.cogentco.com [154.54.6.5
7]
 10    36 ms    42 ms    39 ms  te9-1.mpd01.mci01.atlas.cogentco.com [154.54.25.
206]
 11    39 ms    39 ms    39 ms  vl3508.na31.b006290-3.mci01.atlas.cogentco.com [
38.20.45.234]
 12    37 ms    35 ms    45 ms  38.104.86.74
 13    40 ms    36 ms    41 ms  SW1.KCMODATACENTER.COM [208.94.243.14]
 14    36 ms    37 ms    36 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 15    34 ms    38 ms    39 ms  208.94.241.15

Trace complete.



C:\Users\Kyle>ping 64.182.65.69

Pinging 64.182.65.69 with 32 bytes of data:
Reply from 64.182.65.69: bytes=32 time=29ms TTL=55
Reply from 64.182.65.69: bytes=32 time=29ms TTL=54
Reply from 64.182.65.69: bytes=32 time=29ms TTL=55
Reply from 64.182.65.69: bytes=32 time=29ms TTL=54

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


C:\Users\Kyle>ping 208.94.241.1

Pinging 208.94.241.1 with 32 bytes of data:
Reply from 208.94.241.1: bytes=32 time=37ms TTL=116
Reply from 208.94.241.1: bytes=32 time=39ms TTL=115
Reply from 208.94.241.1: bytes=32 time=35ms TTL=116
Reply from 208.94.241.1: bytes=32 time=34ms TTL=116

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




C:\Users\Kyle>tracert 64.182.65.69

Tracing route to 69-65-182-64.cust.propagation.net [64.182.65.69]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    20 ms    10 ms     8 ms  ip174-71-112-1.om.om.cox.net [174.71.112.1]
  3     9 ms     7 ms     8 ms  68.13.9.197
  4     8 ms     9 ms    16 ms  68.13.8.21
  5    12 ms    10 ms    11 ms  68.13.8.205
  6     8 ms    12 ms    10 ms  mtc1dsrj01-xe210.0.rd.om.cox.net [68.13.14.5]
  7    27 ms    26 ms    33 ms  dalsbbrj01-ae0.r2.dl.cox.net [68.1.0.142]
  8    26 ms    38 ms    26 ms  207.88.185.30.ptr.us.xo.net [207.88.185.30]
  9    41 ms    28 ms    28 ms  64.182.192.41
 10    27 ms    27 ms    27 ms  69-65-182-64.cust.propagation.net [64.182.65.69]


Trace complete.



C:\Users\Kyle>tracert 208.94.241.15

Tracing route to 208.94.241.15 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    14 ms    10 ms     9 ms  ip174-71-112-1.om.om.cox.net [174.71.112.1]
  3     8 ms    10 ms    23 ms  68.13.9.197
  4     9 ms    23 ms    12 ms  68.13.8.21
  5     9 ms    22 ms    10 ms  68.13.8.205
  6    10 ms    11 ms    10 ms  mtc1dsrj01-xe210.0.rd.om.cox.net [68.13.14.5]
  7    25 ms    39 ms    26 ms  dalsbbrj02-ae2.0.r2.dl.cox.net [68.1.1.243]
  8    39 ms    27 ms    26 ms  te7-1.mpd01.dfw03.atlas.cogentco.com [154.54.25.
5]
  9    24 ms    27 ms    26 ms  te3-2.mpd01.dfw01.atlas.cogentco.com [154.54.6.5
7]
 10    36 ms    42 ms    39 ms  te9-1.mpd01.mci01.atlas.cogentco.com [154.54.25.
206]
 11    39 ms    39 ms    39 ms  vl3508.na31.b006290-3.mci01.atlas.cogentco.com [
38.20.45.234]
 12    37 ms    35 ms    45 ms  38.104.86.74
 13    40 ms    36 ms    41 ms  SW1.KCMODATACENTER.COM [208.94.243.14]
 14    36 ms    37 ms    36 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
 15    34 ms    38 ms    39 ms  208.94.241.15

Trace complete.
AngryYankee
Guest
500 POSTS CLUB!
*

BPN Props: 27
Offline Offline

Posts: 544


Nerd Rage!!!11!!!!one

  • Awards Voted Boon of the Month at the last BPN All Hands Meeting

    • Awards
    « Reply #17 on: October 26, 2009, 09:07:59 PM »
    Microsoft Windows XP [Version 5.1.2600]
    (C) Copyright 1985-2001 Microsoft Corp.

    H:\Documents and Settings\ET>ping 208.94.241.15

    Pinging 208.94.241.15 with 32 bytes of data:

    Reply from 208.94.241.15: bytes=32 time=62ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=68ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=72ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=60ms TTL=51

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

    H:\Documents and Settings\ET>ping 208.94.241.15

    Pinging 208.94.241.15 with 32 bytes of data:

    Reply from 208.94.241.15: bytes=32 time=54ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=50ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=65ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=54ms TTL=51

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

    H:\Documents and Settings\ET>ping 208.94.241.15

    Pinging 208.94.241.15 with 32 bytes of data:

    Reply from 208.94.241.15: bytes=32 time=70ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=63ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=63ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=65ms TTL=51

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

    H:\Documents and Settings\ET>
    [img]http://sigs.enjin.com/sig-
    Old_Colonel
    Guest
    « Reply #18 on: October 26, 2009, 09:56:11 PM »
    Microsoft Windows [Version 6.0.6002]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    ======================================
    C:\Users\Old_Colonel>ping 208.94.241.15

    Pinging 208.94.241.15 with 32 bytes of data:
    Reply from 208.94.241.15: bytes=32 time=65ms TTL=53
    Reply from 208.94.241.15: bytes=32 time=60ms TTL=53
    Reply from 208.94.241.15: bytes=32 time=61ms TTL=53
    Reply from 208.94.241.15: bytes=32 time=51ms TTL=53

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

    C:\Users\Old_Colonel>ping 208.94.241.15

    Pinging 208.94.241.15 with 32 bytes of data:
    Reply from 208.94.241.15: bytes=32 time=86ms TTL=53
    Reply from 208.94.241.15: bytes=32 time=56ms TTL=53
    Reply from 208.94.241.15: bytes=32 time=79ms TTL=53
    Reply from 208.94.241.15: bytes=32 time=76ms TTL=53

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

    C:\Users\Old_Colonel>ping 208.94.241.15

    Pinging 208.94.241.15 with 32 bytes of data:
    Reply from 208.94.241.15: bytes=32 time=50ms TTL=53
    Reply from 208.94.241.15: bytes=32 time=51ms TTL=53
    Reply from 208.94.241.15: bytes=32 time=80ms TTL=53
    Reply from 208.94.241.15: bytes=32 time=69ms TTL=53

    Ping statistics for 208.94.241.15:
        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
    Approximate round trip times in milli-seconds:
        Minimum = 50ms, Maximum = 80ms, Average = 62ms
    ======================================
    C:\Users\Old_Colonel>ping 64.182.65.69

    Pinging 64.182.65.69 with 32 bytes of data:
    Reply from 64.182.65.69: bytes=32 time=76ms TTL=52
    Reply from 64.182.65.69: bytes=32 time=77ms TTL=52
    Reply from 64.182.65.69: bytes=32 time=102ms TTL=52
    Reply from 64.182.65.69: bytes=32 time=89ms TTL=52

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

    C:\Users\Old_Colonel>ping 64.182.65.69

    Pinging 64.182.65.69 with 32 bytes of data:
    Reply from 64.182.65.69: bytes=32 time=79ms TTL=52
    Reply from 64.182.65.69: bytes=32 time=78ms TTL=52
    Reply from 64.182.65.69: bytes=32 time=87ms TTL=52
    Reply from 64.182.65.69: bytes=32 time=75ms TTL=52

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

    C:\Users\Old_Colonel>ping 64.182.65.69

    Pinging 64.182.65.69 with 32 bytes of data:
    Reply from 64.182.65.69: bytes=32 time=80ms TTL=52
    Reply from 64.182.65.69: bytes=32 time=77ms TTL=52
    Reply from 64.182.65.69: bytes=32 time=80ms TTL=52
    Reply from 64.182.65.69: bytes=32 time=87ms TTL=52

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

    =====================================

    C:\Users\Old_Colonel>tracert 208.94.241.15

    Tracing route to 208.94.241.15 over a maximum of 30 hops

      1     1 ms     1 ms     1 ms  MN-700 [192.168.2.1]
      2    13 ms    23 ms    23 ms  70.64.208.1
      3    20 ms    31 ms    21 ms  rc1nr-tge0-8-2-0-1.wp.shawcable.net [64.59.179.3
    ]
      4    39 ms    37 ms    46 ms  rc2ch-pos5-0.il.shawcable.net [66.163.76.26]
      5    40 ms    51 ms    66 ms  rd1ec-ge12-0-0.il.shawcable.net [66.163.65.49]
      6    45 ms    51 ms    63 ms  te8-3.mpd01.ord03.atlas.cogentco.com [154.54.9.5
    3]
      7    47 ms    37 ms    52 ms  vl3489.mpd01.ord01.atlas.cogentco.com [154.54.5.
    17]
      8    69 ms    58 ms    60 ms  te8-4.mpd01.mci01.atlas.cogentco.com [66.28.4.18
    5]
      9    64 ms    53 ms    50 ms  vl3508.na31.b006290-3.mci01.atlas.cogentco.com [
    38.20.45.234]
     10    51 ms    59 ms    52 ms  38.104.86.74
     11    80 ms    62 ms    75 ms  SW1.KCMODATACENTER.COM [208.94.243.14]
     12    49 ms    78 ms    48 ms  208.94.241.2
     13    49 ms    52 ms    50 ms  208.94.241.15

    Trace complete.
    tonski
    100 POSTS CLUB
    *

    BPN Props: 0
    Offline Offline

    Posts: 128



    Awards
    « Reply #19 on: January 22, 2010, 03:51:04 PM »
    You guys have some funny user names..
    Schlup
    Master Admin
    1000 POSTS CLUB!!!
    *
    *

    BPN Props: 1226
    Offline Offline

    Posts: 6664



    WWW Awards
    « Reply #20 on: January 22, 2010, 04:56:09 PM »
    Why do you say that?  They seem pretty standard to me...
    Katarn79
    Member
    100 POSTS CLUB
    *
    *

    BPN Props: 10
    Offline Offline

    Posts: 240



    Awards
    « Reply #21 on: January 22, 2010, 08:32:24 PM »
    Microsoft Windows [Version 6.1.7600]
    Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

    C:\Users\Katarn79>ping 208.94.241.15

    Pinging 208.94.241.15 with 32 bytes of data:
    Reply from 208.94.241.15: bytes=32 time=30ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=28ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=30ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=28ms TTL=51

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

    C:\Users\Katarn79>ping 208.94.241.15

    Pinging 208.94.241.15 with 32 bytes of data:
    Reply from 208.94.241.15: bytes=32 time=29ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=46ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=31ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=28ms TTL=51

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

    C:\Users\Katarn79>ping 208.94.241.15

    Pinging 208.94.241.15 with 32 bytes of data:
    Reply from 208.94.241.15: bytes=32 time=73ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=30ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=97ms TTL=51
    Reply from 208.94.241.15: bytes=32 time=36ms TTL=51

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

    C:\Users\Katarn79>
    cygnus
    250 POSTS CLUB
    *

    BPN Props: 7
    Offline Offline

    Posts: 307



    Awards
    « Reply #22 on: January 25, 2010, 10:50:54 AM »
    Here ya go Schlup!

    Pinging 208.94.241.15 with 32 bytes of data:
    Reply from 208.94.241.15: bytes=32 time=58ms TTL=52
    Reply from 208.94.241.15: bytes=32 time=58ms TTL=52
    Reply from 208.94.241.15: bytes=32 time=57ms TTL=52
    Reply from 208.94.241.15: bytes=32 time=56ms TTL=52

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

    Was the same on 3 other tries within +/-1 ms

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

    C:\Users\Kelly>tracert 208.94.241.15

    Tracing route to 208.94.241.15 over a maximum of 30 hops

      1     7 ms     7 ms    12 ms  10.20.104.1
      2     7 ms     8 ms     7 ms  gw03.flfrd.phub.net.cable.rogers.com [66.185.90.
    225]
      3     7 ms     7 ms     7 ms  gw01.bloor.phub.net.cable.rogers.com [66.185.83.
    153]
      4    13 ms    13 ms    13 ms  so-5-0-3.gw02.bloor.phub.net.cable.rogers.com [6
    6.185.81.73]
      5    14 ms    13 ms    13 ms  so-0-0-0.gw02.mtnk.phub.net.cable.rogers.com [66
    .185.80.170]
      6    31 ms    33 ms    32 ms  69.63.248.101
      7     *        *        *     Request timed out.
      8    29 ms    31 ms    31 ms  te2-4.mpd03.jfk02.atlas.cogentco.com [154.54.7.1
    3]
      9    43 ms    43 ms    44 ms  te1-8.mpd01.ord01.atlas.cogentco.com [154.54.29.
    157]
     10    55 ms    55 ms    53 ms  te0-3-0-1.mpd21.mci01.atlas.cogentco.com [154.54
    .7.138]
     11    64 ms    69 ms    56 ms  te4-2.mpd01.mci01.atlas.cogentco.com [154.54.30.
    174]
     12    57 ms    57 ms    60 ms  vl3808.na31.b006290-3.mci01.atlas.cogentco.com [
    38.20.45.238]
     13    55 ms    57 ms    54 ms  38.104.86.74
     14    62 ms    60 ms    57 ms  SW1.KCMODATACENTER.COM [208.94.243.14]
     15    58 ms    56 ms    57 ms  jdc-vm1.joesdatacenter.com [208.94.241.2]
     16    55 ms    55 ms    56 ms  208.94.241.15

    Trace complete.


    Proud video junkie and addict since 1978 - Space Invaders rulz!
    Schlup
    Master Admin
    1000 POSTS CLUB!!!
    *
    *

    BPN Props: 1226
    Offline Offline

    Posts: 6664



    WWW Awards
    « Reply #23 on: January 25, 2010, 01:43:50 PM »
    Thanks guys but this has been done for a couple months now.  I don't need anymore trace routes or ping tests.
    cygnus
    250 POSTS CLUB
    *

    BPN Props: 7
    Offline Offline

    Posts: 307



    Awards
    « Reply #24 on: January 25, 2010, 05:01:32 PM »
    LOL!  I never bothered to look at the dates - saw new posts and assumed it was a recent thread!  Tongue


    Proud video junkie and addict since 1978 - Space Invaders rulz!
    Schlup
    Master Admin
    1000 POSTS CLUB!!!
    *
    *

    BPN Props: 1226
    Offline Offline

    Posts: 6664



    WWW Awards
    « Reply #25 on: January 26, 2010, 02:00:12 AM »
    No problem, better late than never I guess!  We did end up moving our server to this new data center and haven't had any issues!
    Pages: 1   Go Up
      Print  
    « previous next »
     
    Jump to:  


    Powered by SMF 1.1.16 | SMF © 2011, Simple Machines Page created in 0.296 seconds with 23 queries.