Comcast user connection issues

[Anaxogoras]

Great link!  Bob Garfield also has a great show called On The Media, broadcast by WNYC.

[Infidelz]

hello Skuzzy. I don't have comcast but I have been disconnected several times today. Its OK once in a while, until you have a successfull ME262 mission and disco just prior to landing. Not only do you lose the system message you lose your perk points. Very dissapointed.

here is my tracert

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

C:\Documents and Settings\Owner>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     2 ms     2 ms     2 ms  192.168.1.1
  2    11 ms    13 ms    18 ms  d-216-36-16-1.cpe.metrocast.net [216.36.16.1]
  3    11 ms    13 ms    12 ms  static-216-36-30-138.cpe.metrocast.net [216.36.3
0.138]
  4    13 ms    13 ms    12 ms  static-216-36-30-246.cpe.metrocast.net [216.36.3
0.246]
  5    11 ms    13 ms    12 ms  dca-edge-19.inet.qwest.net [65.127.222.209]
  6    13 ms    13 ms    12 ms  dca-core-02.inet.qwest.net [205.171.9.41]
  7     *        *       14 ms  dcx-core-01.inet.qwest.net [67.14.28.2]
  8    13 ms    17 ms    18 ms  dcp-brdr-02.inet.qwest.net [205.171.251.34]
  9    14 ms    17 ms    18 ms  192.205.34.253
 10    62 ms    60 ms    58 ms  tbr2.wswdc.ip.att.net [12.123.8.190]
 11    60 ms    59 ms    61 ms  cr2.wswdc.ip.att.net [12.122.16.93]
 12    59 ms    58 ms    58 ms  cr1.attga.ip.att.net [12.122.1.173]
 13    59 ms    58 ms    62 ms  cr2.attga.ip.att.net [12.122.2.134]
 14    61 ms    60 ms    63 ms  cr1.dlstx.ip.att.net [12.122.2.225]
 15    59 ms    58 ms    60 ms  gar5.dlstx.ip.att.net [12.122.139.5]
 16    61 ms    61 ms    60 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255
.82]
 17    62 ms    59 ms    63 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.
222]
 18    60 ms    61 ms    61 ms  206.16.60.38

Trace complete.

C:\Documents and Settings\Owner>

Number seven was a bit sluggish its seemed. Does everyone go through att to get to your servers? Maybe they have something in common with the problem?

INFIDELZ.

[Skuzzy]

Hop number 7 is in your ISP's network.  It's not even the gateway to the Internet.  You need to contact QWest abot it.

[Infidelz]

My ISP is metrocast. I see what your saying there, I will contact the CEO of QWest personnally as soon as he gets his bailout money.

I ran another one after a crash on the 27th and Windows gave ATT 2 stars for their performance (Number 11). My ISP only got 1 star (number 4). Clearly Att got more stars. Which side of the St. Louis Gateway is that on? 


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

C:\Documents and Settings\Scubi>tracert 206.16.60.38

Tracing route to 206.16.60.38 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.1.1
  2     9 ms     9 ms     8 ms  d-216-36-16-1.cpe.metrocast.net [216.36.16.1]
  3     *       10 ms    12 ms  static-216-36-30-138.cpe.metrocast.net [216.36.30.138]
  4    13 ms    12 ms     *     static-216-36-30-246.cpe.metrocast.net [216.36.30.246]
  5    14 ms    13 ms    12 ms  dca-edge-19.inet.qwest.net [65.127.222.209]
  6    11 ms    13 ms    13 ms  dca-core-02.inet.qwest.net [205.171.9.41]
  7    14 ms    12 ms    13 ms  dcx-core-01.inet.qwest.net [67.14.28.2]
  8    15 ms    11 ms    14 ms  dcp-brdr-02.inet.qwest.net [205.171.251.34]
  9    17 ms    16 ms    12 ms  192.205.34.253
 10    61 ms    61 ms    58 ms  tbr2.wswdc.ip.att.net [12.123.8.190]
 11     *        *       58 ms  cr2.wswdc.ip.att.net [12.122.16.93]
 12    59 ms    58 ms    57 ms  cr1.attga.ip.att.net [12.122.1.173]
 13    59 ms    60 ms    57 ms  cr2.attga.ip.att.net [12.122.2.134]
 14    58 ms    58 ms    56 ms  cr1.dlstx.ip.att.net [12.122.2.225]
 15    57 ms    57 ms    59 ms  gar5.dlstx.ip.att.net [12.122.139.5]
 16    57 ms    57 ms    57 ms  mdf1-gsr12-1-pos-7-0.dal1.attens.net [12.122.255.82]
 17    57 ms    57 ms    59 ms  mdf1-bi8k-2-eth-2-3.dal1.attens.net [63.241.192.222]
 18    56 ms    58 ms    58 ms  206.16.60.38

Trace complete.

C:\Documents and Settings\Scubi>

[Skuzzy]

Once it starts happening, any information after that can be considered useless as that information will be tainted by the problems with the previous hops.

You need to contact your ISP.

[SKColt]

I am in Wichita KS. I just began having disco issues last night.

Colt

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 1/6/2009 8:17:10 AM to 1/6/2009 8:19:25 AM

 1   *       *       *       *       *       *       *       *       *       *       [-]
 2   10 ms   11 ms    8 ms   10 ms   13 ms   11 ms   10 ms    9 ms    9 ms   11 ms  ip72-202-128-1.ks.ks.cox.net [72.202.128.1]
 3   11 ms    9 ms   10 ms    9 ms    9 ms   16 ms   10 ms   11 ms    7 ms   10 ms  ip70-183-64-37.ks.ks.cox.net [70.183.64.37]
 4   16 ms   18 ms   18 ms   18 ms   17 ms   18 ms   18 ms   17 ms   17 ms   18 ms  kscydsrj02-ae2.rd.ks.cox.net [70.183.71.105]
 5   *       *       *       *       *       *       *       *       *       *       [-]
 6   *       *       *       *       *       *       *       *       *       *       [-]
 7   24 ms   24 ms   27 ms   23 ms   23 ms   25 ms   25 ms   24 ms   25 ms   25 ms  mtc3dsrj01-ge-100.0.rd.ok.cox.net [68.1.0.113]
 8   *       *       *       *       *       *       *       *       *       *       [-]
 9  N/A     N/A      30 ms  N/A     N/A     N/A     N/A     N/A     N/A      30 ms  ae-4-99.edge2.Dallas3.Level3.net [4.68.19.204]
10  N/A     N/A     N/A     N/A     N/A     N/A      75 ms   29 ms   *       *      [192.205.35.225]
11  N/A     N/A     N/A      29 ms   *       *       *       *       *       28 ms  tbr1.dlstx.ip.att.net [12.122.86.206]
12   *       31 ms   31 ms   29 ms   29 ms   28 ms   37 ms   29 ms   31 ms   31 ms  cr1.dlstx.ip.att.net [12.122.18.129]
13   55 ms   *       *       *       *       *       *       *       *       *      cr2.sl9mo.ip.att.net [12.122.2.22]
14   *       56 ms   54 ms   57 ms   53 ms   57 ms   56 ms   57 ms   56 ms   54 ms  cr1.sl9mo.ip.att.net [12.122.2.217]
15   58 ms   57 ms   56 ms   55 ms   56 ms   54 ms   55 ms   56 ms   56 ms   56 ms  cr2.dlstx.ip.att.net [12.122.3.221]
16  191 ms   *       *       *       *       *       *       *       *       *      gar5.dlstx.ip.att.net [12.122.138.5]
17   32 ms   29 ms   28 ms   30 ms   30 ms   33 ms   28 ms   29 ms   29 ms   30 ms  [206.16.60.38]

Ping statistics for 206.16.60.38
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 28ms, Maximum = 33ms, Average = 29ms

[Skuzzy]

You need to get that to Cox.  The problems you are having lies within Cox's network.  First tier support will tell you nothing it wrong, as they are only responsible for your immediate Inter connection.  You will need to get this escalated and point them to the above post you have made.

Good luck.

[SKColt]

 I may have "stumbled" onto a solution.....maybe. The COX upper tier engineer pulled the recent logs for my modem, and told me the transmit levels were high, and had exceeded expected levels several times in the last three days. When I looked at the modem stats, the transmit level was at the upper edge. He suggested that COX come to the house to check and set levels.
 When I put my new system together this past weekend, I did not re-install my HDTV tuner card. I have a dedicated CATV drop for my PC desk. It hits a splitter, that feeds the modem and the HDTV tuner. Since I did not hook the tuner back up, I had an unterminated RF port on the splitter. I removed the splitter, and hooked the cable directly to the modem. The modem then displayed a transmit level 3.5Db lower then before, well within the range the COX engineer expected me to have.
 The ping plot did not look much better, but I then flew in AH for 4 straight hours without a burp! SKHammer emailed a ping plot to me(he is on the same ISP here in Wichita. He utilizes the same paths as I do, and never gets discoed. His plot had some of the same "anomalies" as mine.)
 COX is still coming out tomorrow morning to check the levels and the ping plots. Fingers remain crossed!!

Colt