keep getting discoed

[NEARY]

 i keep getting discoed 5 or less minutes after i log in, i have qwest broadband, and i live in colorado springs, colorado. does it have something to do the mountains? or is qwest to blame?

[NEARY]

can someone please help me

[toadkill]

Go to Cnet, and downloag the free program Ping Plotter. Use that to test your connection to the IPs listed in this post http://bbs.hitechcreations.com/smf/index.php/topic,68316.0.html If your PL% is high then it is your ISP, and you can either get in contact with them to see what you can do. or you can get service from other ISPs.

[NEARY]

i did that and it is going everywhere, the ping is is moving a lot and when i was discoed it said destination unreachable, then started again

[gpwurzel]

Your losing connectivity to the server - hence being disco'd. Run your pingplot for a few min, and post the results on here - unless its the very last hop (unlikely or everyone would be disco'd at the same time), there is a problem on the net between you and the AH servers.

Wurzel

[NEARY]

Target Name: Nessoft Site by IP
         IP: 216.92.150.222
  Date/Time: 7/25/2008 3:47:54 PM to 7/25/2008 3:48:00 PM

 1    0 ms    1 ms    1 ms    1 ms    0 ms    1 ms    0 ms    1 ms    1 ms  N/A     [192.168.0.1]
 2   32 ms   33 ms   33 ms   32 ms   32 ms   31 ms   34 ms   33 ms   32 ms  N/A     clsp-dsl-gw16-208.clsp.qwest.net [67.42.184.208]
 3   32 ms   32 ms   33 ms   33 ms   33 ms   32 ms   33 ms   32 ms   33 ms  N/A     clsp-agw1.inet.qwest.net [67.42.184.109]
 4   33 ms   44 ms   32 ms   34 ms   32 ms   32 ms   31 ms   32 ms   33 ms  N/A     cls-core-01.inet.qwest.net [205.171.152.65]
 5   57 ms   57 ms   58 ms   56 ms   58 ms   59 ms   63 ms   56 ms   55 ms  N/A     dal-core-02.inet.qwest.net [67.14.2.61]
 6   59 ms   59 ms   58 ms   64 ms   58 ms   57 ms   58 ms   56 ms   56 ms  N/A     dap-brdr-02.inet.qwest.net [205.171.25.18]
 7   59 ms   64 ms   58 ms   58 ms   58 ms   57 ms   58 ms   61 ms   58 ms  N/A     [192.205.35.53]
 8   92 ms   94 ms   94 ms   92 ms   92 ms   91 ms   93 ms   91 ms   94 ms  N/A     tbr2.dlstx.ip.att.net [12.122.87.214]
 9   92 ms   92 ms   92 ms   92 ms   91 ms   91 ms   91 ms   92 ms   91 ms  N/A     cr2.dlstx.ip.att.net [12.122.18.197]
10   91 ms   92 ms   92 ms   92 ms   91 ms   92 ms   91 ms   92 ms   89 ms  N/A     cr1.attga.ip.att.net [12.122.28.173]
11   92 ms   91 ms   92 ms   91 ms   92 ms   90 ms   91 ms   91 ms  N/A     N/A     cr2.wswdc.ip.att.net [12.122.1.174]
12   91 ms   91 ms   91 ms   92 ms   92 ms   91 ms   92 ms   91 ms  N/A     N/A     tbr2.wswdc.ip.att.net [12.122.16.86]
13   92 ms   92 ms   93 ms   91 ms   91 ms   92 ms   91 ms   91 ms  N/A     N/A     gar1.ascva.ip.att.net [12.122.80.197]
14   89 ms   88 ms   88 ms   90 ms   87 ms   90 ms   89 ms   88 ms  N/A     N/A     [12.117.208.18]
15   *       *       *       *      N/A     N/A     N/A     N/A     N/A     N/A      [-]
16   87 ms   89 ms   90 ms   89 ms   90 ms   89 ms   90 ms   89 ms  N/A     N/A     nessoft.com [216.92.150.222]

Ping statistics for Nessoft Site by IP
Packets: Sent = 9, Received = 9, Lost = 0 (0.0%)
Round Trip Times: Minimum = 87ms, Maximum = 90ms, Average = 89ms

here it is

[Bones]

I beleive you would want to run a trace to the game server for it to mean anything here.  Try 206.16.60.38

[NEARY]

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 7/25/2008 7:07:53 PM to 7/25/2008 7:08:02 PM

 1    1 ms    0 ms    1 ms    0 ms    0 ms    1 ms    0 ms    1 ms    1 ms    0 ms  [192.168.0.1]
 2   27 ms   24 ms   25 ms   25 ms   24 ms   25 ms   25 ms   24 ms   25 ms   25 ms  clsp-dsl-gw16-208.clsp.qwest.net [67.42.184.208]
 3   23 ms   26 ms   24 ms   25 ms   24 ms   24 ms   25 ms   24 ms   24 ms   25 ms  clsp-agw1.inet.qwest.net [67.42.184.109]
 4   29 ms   25 ms   24 ms   24 ms   25 ms   24 ms   24 ms   25 ms   24 ms   25 ms  cls-core-01.inet.qwest.net [205.171.152.65]
 5   49 ms   51 ms   50 ms   57 ms   49 ms   50 ms   50 ms   51 ms   56 ms   49 ms  dal-core-01.inet.qwest.net [67.14.2.53]
 6   51 ms   57 ms   51 ms   99 ms   49 ms   51 ms   50 ms   49 ms   51 ms   50 ms  dap-brdr-02.inet.qwest.net [205.171.25.14]
 7   *       50 ms   51 ms   50 ms  192 ms   53 ms   50 ms   50 ms   51 ms   54 ms  [192.205.35.53]
 8   49 ms   52 ms   51 ms   53 ms   50 ms   50 ms   51 ms   52 ms   51 ms   53 ms  tbr2.dlstx.ip.att.net [12.122.87.214]
 9   50 ms   50 ms   50 ms   49 ms  104 ms   50 ms   49 ms   51 ms   50 ms   49 ms  br2.dlstx.ip.att.net [12.123.16.213]
10   52 ms   49 ms   50 ms   50 ms   51 ms   52 ms   51 ms   49 ms   50 ms   50 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
11   52 ms  316 ms   53 ms   52 ms   50 ms   53 ms   52 ms   51 ms   51 ms   52 ms  mdf1-bi8k-2-eth-2-2.dal1.attens.net [63.241.192.218]
12   52 ms   52 ms   49 ms   51 ms   50 ms   49 ms   50 ms   50 ms   49 ms   50 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 = 49ms, Maximum = 52ms, Average = 50ms

ok here it is

[Skuzzy]

Pretty much what I expected to see.  I say that as I have been getting a lot of complaints from many QWest customers.  All seem to have the same issue at the gateways for QWest.

The gateway is the connection QWest uses for Internet access.  Whne those gateways get overcrowded, packet loss and various other anomalies ensue.  That is what your trace is indicating.  You need to get this to QWest.  Just keep in mind, if the problem is one of being over saturated, there is really nothing thy can do in  the short term.

They may chose to weather it, or they may already be looking into upgrading thier gateway service bandwidth.  They would be the only ones qualified to answer the question.

[NEARY]

how do i get it to qwest? i know that sounds stupid but i really don't know

[NEARY]

can someone please help me

[NEARY]

gaaaaghh NOT AGAINNNNN

[Skuzzy]

Try support@qwest.net.  Just a guess.  I guess you could call them and ask who to send it to as well.

[Thruster]

I've been unable to hold a connection more than 30 sec's for a couple of days now. Now that I think about it disco's were getting more common for a while before that but not like this. I've clocked sessions between 22 and 45 seconds max since yesterday. I even completely uninstalled my AV to see if an update was the culprit. No joy. I've never seen net stats like I get now.

Ping Plotter output:

Target Name: N/A
         IP: 206.16.60.38
  Date/Time: 8/1/2008 1:40:03 PM

 1   22 ms   34 ms   22 ms   12 ms  [73.57.236.1]
 2   23 ms   27 ms   23 ms   24 ms  ge-7-45-ur01.area4.il.chicago.comcast.net [68.87.229.201]
 3   26 ms   32 ms   26 ms   27 ms  te-9-3-ar01.area4.il.chicago.comcast.net [68.87.230.93]
 4   19 ms   11 ms   12 ms   15 ms  pos-0-13-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.53]
 5   14 ms   14 ms   11 ms   12 ms  xe-9-2-0.edge1.Chicago2.Level3.net [4.71.248.25]
 6   15 ms   16 ms   17 ms   15 ms  ae-14-53.car4.Chicago1.Level3.net [4.68.101.72]
 7   14 ms   16 ms   16 ms   18 ms  [192.205.33.209]
 8   51 ms   45 ms   47 ms   52 ms  tbr2.cgcil.ip.att.net [12.123.6.26]
 9   54 ms   51 ms   47 ms   54 ms  cr1.cgcil.ip.att.net [12.122.17.193]
10   54 ms   49 ms   58 ms   51 ms  cr1.sl9mo.ip.att.net [12.122.30.86]
11   56 ms   53 ms   48 ms   43 ms  cr2.dlstx.ip.att.net [12.122.3.221]
12   43 ms   44 ms   43 ms   42 ms  tbr2.dlstx.ip.att.net [12.122.18.214]
13   46 ms   45 ms   45 ms   45 ms  br2.dlstx.ip.att.net [12.123.16.213]
14   61 ms   45 ms   44 ms   *      mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
15   44 ms   48 ms   48 ms   64 ms  mdf1-bi8k-2-eth-2-1.dal1.attens.net [63.241.192.198]
16   55 ms   49 ms   50 ms   52 ms  [206.16.60.38]

Ideas?

[Skuzzy]

Comcast is going tobe a hit and miss proposition until soemthing is done to stop them from using the network shaping system they use.  It causes discos to make room for other bandwidth.

Speculation, but it seems Comcast has a contract with a certain VoIP phone company to allow a certain amount of bandwidth to always be available so the phone service will work reliably.

That is just a guess.  Rumor has it the FCC is going to tell Comcast they cannot fool around with a customers connection.  Until that ruling comes down, or the class action suit in California comes to a head, Comcast users will have spotty times depending on the network load.