Discos

[Thing]

Hello All

I recently having been having a horrible problem with discos.  In the past the game ran very well now I am having multiple discos when I play the game.  I have a cable modem through cox cable and use windows xp.  I currently use FS autostart while running AH.  Any suggestions are very much needed   


   Thing

[drdeathx]

You need to run Pingplotter. It is free software to analyze your packet loss. Then you need to post results here and Skuzzy will analyze it.

http://www.pingplotter.com/download.html


use ip address 206.16.60.38 or 12.193.161.229.I forget which one Skuzzy said to run. Think its the first one.

This will analyze your packet loss between you and Hitec and return trip.

Here is a sceen shot of what it looks like. This is my actual ping. Awesome isn't it?

[Thing]

Thanks Doc



 

[Thing]

Here it is

I hope I did it correctly
Target Name: 206.16.60.38.
         IP: 206.16.60.38
  Date/Time: 1/1/2009 9:50:47 PM to 1/1/2009 9:53:02 PM

 1  155 ms   12 ms   13 ms   24 ms   10 ms   16 ms   25 ms   11 ms   14 ms   28 ms  ip68-96-60-1.ph.ph.cox.net [68.96.60.1]
 2  113 ms   48 ms   15 ms   21 ms   14 ms   38 ms   15 ms    9 ms    9 ms   61 ms  ip68-2-6-181.ph.ph.cox.net [68.2.6.181]
 3   78 ms   22 ms   20 ms   10 ms   14 ms   19 ms   30 ms   48 ms   51 ms   30 ms  [70.169.73.41]
 4   39 ms   28 ms   15 ms   18 ms   69 ms   36 ms   33 ms   21 ms   26 ms  104 ms  chnddsrj01-ge710.0.rd.ph.cox.net [68.1.0.165]
 5   59 ms   29 ms   30 ms   31 ms   43 ms  102 ms   68 ms   24 ms   18 ms   78 ms  ae-11-11.car2.Phoenix1.Level3.net [4.69.133.34]
 6   34 ms   35 ms   73 ms   46 ms   33 ms   46 ms   50 ms   66 ms   62 ms   54 ms  ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
 7   26 ms   30 ms   34 ms   40 ms   83 ms   64 ms   64 ms   42 ms   59 ms   77 ms  ae-62-62.csw1.LosAngeles1.Level3.net [4.69.137.18]
 8   23 ms   35 ms   65 ms   33 ms   52 ms   39 ms   32 ms   52 ms   29 ms   47 ms  ae-1-69.edge1.LosAngeles1.Level3.net [4.68.20.7]
 9   27 ms   54 ms   25 ms   38 ms   56 ms   35 ms  117 ms   41 ms   61 ms   46 ms  [192.205.33.225]
10   83 ms  134 ms   93 ms   69 ms   78 ms  108 ms   93 ms  126 ms  143 ms   78 ms  cr2.la2ca.ip.att.net [12.122.129.10]
11   69 ms   97 ms   73 ms   82 ms   89 ms   75 ms  103 ms   88 ms  105 ms   72 ms  cr2.dlstx.ip.att.net [12.122.28.177]
12   68 ms   84 ms   69 ms   68 ms   66 ms   71 ms  218 ms   71 ms   69 ms   82 ms  gar5.dlstx.ip.att.net [12.122.138.5]
13   68 ms   83 ms   70 ms   73 ms   68 ms   87 ms   93 ms  109 ms  102 ms   73 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
14   70 ms  325 ms   69 ms   68 ms   72 ms   83 ms  100 ms  517 ms  507 ms   86 ms  mdf1-bi8k-2-eth-2-6.dal1.attens.net [63.241.192.46]
15   68 ms   69 ms   66 ms   77 ms   70 ms   74 ms  127 ms   71 ms  117 ms   74 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 = 66ms, Maximum = 127ms, Average = 81ms

[drdeathx]

let it run for at least 15 min during a busy period also

14   70 ms  325 ms   69 ms   68 ms   72 ms   83 ms  100 ms  517 ms  507 ms   86 ms  mdf1-bi8k-2-eth-2-6.dal1.attens.net [63.241.192.46]

I am learning to read this. Skuzzy will tell ya whats wrong. Looks like line 14 high.

[Thing]

Thanks again Doc.  I cant even stay logged on today.  I take off and lose my UDP session and get discoed.  Tried about ten times. 


Appreciate the help   

[Skuzzy]

If the last hop is showing a problem, then the problem is on the return trip back to your computer.  Due to the limitations of the 'traceroute (includes tracert, Ping Plot, and any other ICMP like utilities)', you can only see the data path your packets take TO the destination.

If the network path is asynchronous (takes a different path back), then you are only seeing half the data.  I have to run the other half for you.

It will have to wait until I am in the office, but generally speaking, the problem is going to lie in the Level3 network.  Your ISP has been switching over to Level3, as has every other cable ISP in the U.S.  Level3's network is badly oversold, but they are cheap, so they are attractive to the cable ISP's who are struggling to make money.

I'll run the trace when I get into the office.

[Thing]

Thanks Skuzzy

I ran ping plotter again Target Name: 206.16.60.38.
         IP: 206.16.60.38
  Date/Time: 1/2/2009 10:27:42 AM

 1    9 ms   32 ms    9 ms   15 ms   26 ms   11 ms  ip68-96-60-1.ph.ph.cox.net [68.96.60.1]
 2   11 ms    9 ms   13 ms   14 ms   11 ms    9 ms  ip68-2-6-181.ph.ph.cox.net [68.2.6.181]
 3   26 ms   10 ms   12 ms   11 ms   22 ms   12 ms  [70.169.73.41]
 4   11 ms   12 ms   13 ms   26 ms   12 ms   12 ms  chnddsrj01-ge710.0.rd.ph.cox.net [68.1.0.165]
 5  224 ms   29 ms   17 ms   16 ms   16 ms   15 ms  ae-11-11.car2.Phoenix1.Level3.net [4.69.133.34]
 6   46 ms   35 ms   21 ms   27 ms   42 ms   35 ms  ae-4-4.ebr2.LosAngeles1.Level3.net [4.69.133.38]
 7   30 ms   39 ms   26 ms   32 ms   33 ms   28 ms  ae-62-62.csw1.LosAngeles1.Level3.net [4.69.137.18]
 8   22 ms   25 ms   44 ms   24 ms   22 ms   24 ms  ae-1-69.edge1.LosAngeles1.Level3.net [4.68.20.7]
 9  N/A     N/A      30 ms   26 ms   22 ms   24 ms  [192.205.33.225]
10   71 ms   65 ms   79 ms   71 ms   65 ms   66 ms  cr2.la2ca.ip.att.net [12.122.129.10]
11  105 ms   65 ms   67 ms   86 ms   70 ms   68 ms  cr2.dlstx.ip.att.net [12.122.28.177]
12   72 ms   64 ms   67 ms   70 ms   67 ms   65 ms  gar5.dlstx.ip.att.net [12.122.138.5]
13   81 ms   69 ms   67 ms   71 ms   67 ms   69 ms  mdf1-gsr12-1-pos-6-0.dal1.attens.net [12.122.255.78]
14   72 ms  146 ms   67 ms   68 ms   70 ms   66 ms  mdf1-bi8k-2-eth-2-6.dal1.attens.net [63.241.192.46]
15   65 ms   66 ms   66 ms   68 ms   69 ms   67 ms  [206.16.60.38]

Ping statistics for 206.16.60.38.
Packets: Sent = 6, Received = 6, Lost = 0 (0.0%)
Round Trip Times: Minimum = 65ms, Maximum = 69ms, Average = 66ms

[Skuzzy]

traceroute 68.2.6.181
traceroute to 68.2.6.181 (68.2.6.181), 30 hops max, 40 byte packets
 1  206.16.60.33 (206.16.60.33)  0.661 ms  0.531 ms  0.480 ms
 2  mdf1-gsr12-1-gig-1-1.dal1.attens.net (63.241.192.201)  0.251 ms  0.207 ms  0.148 ms
 3  gar5.dlstx.ip.att.net (12.122.255.81)  0.966 ms  0.936 ms  0.932 ms
 4  cr2.dlstx.ip.att.net (12.122.138.6)  1.554 ms  1.366 ms  1.268 ms
 5  12.122.18.246 (12.122.18.246)  2.147 ms  1.830 ms  3.573 ms
 6  ggr4.dlstx.ip.att.net (12.122.86.153)  1.175 ms  1.222 ms  1.177 ms
 7  192.205.34.142 (192.205.34.142)  1.496 ms  1.639 ms  1.495 ms
 8  67.17.195.30 (67.17.195.30)  35.868 ms *  40.930 ms
 9  chnddsrj01-ge710.0.rd.ph.cox.net (68.1.0.165)  47.485 ms  47.508 ms  47.534 ms
10  bellcorc01-pos-0-7-0-0.ph.ph.cox.net (70.169.72.59)  49.186 ms  49.796 ms  49.188 ms
11  70.169.73.11 (70.169.73.11)  49.019 ms *  49.169 ms

Looks like Level3 is the problem.  Even so, I cannot reach the IP address inside of Cox's network at all.

I also noted you see problems on the inbound side as well, in that last trace.

You need to contact Cox about this and point them to the traces you have and the one I am posting here.

[Thing]

Hey Skuzzy

I contacted Cox and they weren't very helpful.  They said as long as my internet connection was working they really coultn't do anything else for me.  Any suggestions on how to remedy this mess?   

[Skuzzy]

First tier support is not going to help you.  All they are responsible for is your immediate connection.

Tell them you wish to escalate this problem or ask directly to speak to a higher tier support person.

It does not always work, and some ISP's would rather have you quit the service than deal with it.  If you are in an area where Cox has an exclusive deal, you may be out of luck.

I have already filed a trouble ticket with AT&T, but this is Level3 and there usually is not much that they can do as Cox is paying Level3 for the service.

[Thing]

Would getting rid of Cox and going with another ISP help?  I checked the Phoneix area and they have DSL and other ISPs as well.


Thank you for all your help

   Thing