Having discos frequently

[33Vortex]

It's been a serious issue for me last few months and I've so far been unsuccsessful in finding the cause. Could someone please post a list of items to go through in search for this particular problem?

Thanks

[The Fugitive]

get ping plotter. Its a free program, install it and then check in one of the stickies at the top of the tech threads. Skuzzy posted the address to the servers. Type that in and ping the server every second for 10 minutes. Then post a picture here, or mail it to Skuzzy for him to check.

[flatiron1]

I am discoing too much also. 4 times last night in one hour.

Ran the pingplotter for 10 minutes but not sure if doing it right. Seems all I get is the last plot with the graph. I was thinking I should be getting a summary of the 10 minutes. Anyhow here is the results.  While watching the progress of the plot I saw several times it would go into the yellow and red area but mainly in the green.


Target Name: N/A
         IP: 206.16.60.39
  Date/Time: 4/28/2009 6:14:47 AM to 4/28/2009 6:14:56 AM

 1    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms    6 ms   [0.0.0.0]
 2    7 ms    7 ms    7 ms    7 ms    7 ms    8 ms    7 ms    7 ms    7 ms    7 ms  static.unknown.charter.com [96.34.67.140]
 3    8 ms    9 ms    8 ms    8 ms  191 ms  147 ms   22 ms   40 ms    8 ms    8 ms  static.unknown.charter.com [96.34.67.180]
 4   18 ms   18 ms   18 ms   19 ms   39 ms   18 ms   18 ms   18 ms   18 ms   18 ms  xe-8-0-0.edge3.Washington1.Level3.net [4.59.144.1]
 5   17 ms   17 ms   17 ms   17 ms   19 ms   17 ms   19 ms   18 ms   19 ms   19 ms  ae-2-79.edge1.Washington3.Level3.net [4.68.17.75]
 6   19 ms   19 ms  N/A      19 ms   19 ms  N/A      19 ms  N/A      19 ms   19 ms  att-level3-oc192.Washington1.Level3.net [4.68.127.154]
 7   56 ms   55 ms   56 ms   56 ms   55 ms   56 ms   57 ms   55 ms   55 ms   55 ms  cr2.wswdc.ip.att.net [12.122.134.106]
 8   55 ms   55 ms   54 ms   55 ms   54 ms   55 ms   55 ms   54 ms   55 ms   54 ms  cr1.attga.ip.att.net [12.122.1.173]
 9   55 ms   56 ms   56 ms   55 ms   55 ms   55 ms   56 ms   55 ms   56 ms   55 ms  cr2.dlstx.ip.att.net [12.122.28.174]
10   54 ms   54 ms   54 ms   54 ms   55 ms   53 ms   53 ms   53 ms   55 ms   55 ms  gar5.dlstx.ip.att.net [12.122.138.5]
11   55 ms   72 ms   56 ms   55 ms   55 ms   55 ms   56 ms   55 ms   55 ms   56 ms  [12.122.255.226]
12   56 ms   56 ms   56 ms   56 ms   56 ms   56 ms   56 ms   57 ms   57 ms   56 ms  mdf1-bi8k-1-eth-1-4.dal1.attens.net [63.241.192.42]
13   59 ms   55 ms   55 ms   55 ms   54 ms   54 ms   55 ms   55 ms   54 ms   54 ms  [206.16.60.39]

Ping statistics for 206.16.60.39
Packets: Sent = 10, Received = 10, Lost = 0 (0.0%)
Round Trip Times: Minimum = 54ms, Maximum = 59ms, Average = 55ms

[Skuzzy]

33Vortex, my bet is, your issues have to do with all the DoS attacks going on over the Pirate Bay trial.  It will eventually settle down, but there is no way to know how long it will take.

I have been monitoring the performance and response times coming out of Sweden and they are all over the map.  In any given 30 second window I see variances from 24ms to 175ms.  These are being measured at some very large pipes which normally run 8ms to 12ms.


flatiron, there is nothing that would indicate your problems are Internet related in that Ping Plot, but having Level3 in the path is never a good thing.

[flatiron1]

"flatiron, there is nothing that would indicate your problems are Internet related in that Ping Plot, but having Level3 in the path is never a good thing."


what does level 3 mean?
so is there any way to do anything about that?


how about this one seems I am in the red zone here  619 ms

[33Vortex]

Thanks for the info Skuzzy, didn't know that the trial affected the traffic to that extent.

[Skuzzy]

It normally would not have 33Vortex, but the kiddies on the Internet are retaliating by issuing massive DoS attacks against those involved with the trial.

Being the clueless lot they are, they have no idea how that impacts all the rest of the users having to get through the Sweden pipes.

[flatiron1]

cable guy came out today and replaced all my outside connections and said my modem has noise so he gave me a new one. Discoed 3 times already tonight.


System Information
------------------
Time of this report: 11/29/2008, 17:28:18
       Machine name: JAMES-PC
   Operating System: Windows Vista™ Home Premium (6.0, Build 6000) (6000.vista_gdr.080917-1612)
           Language: English (Regional Setting: English)
System Manufacturer: Dell Inc.
       System Model: Inspiron 530
               BIOS: Phoenix - AwardBIOS v6.00PG
          Processor: Intel(R) Core(TM)2 Duo CPU     E6550  @ 2.33GHz (2 CPUs), ~2.3GHz
             Memory: 2046MB RAM
          Page File: 668MB used, 3658MB available
        Windows Dir: C:\Windows
    DirectX Version: DirectX 10
DX Setup Parameters: Not found
     DxDiag Version: 6.00.6000.16386 32bit Unicode

------------
DxDiag Notes
------------
      Display Tab 1: No problems found.
        Sound Tab 1: No problems found.
          Input Tab: No problems found.

--------------------
DirectX Debug Levels
--------------------
Direct3D:    0/4 (retail)
DirectDraw:  0/4 (retail)
DirectInput: 0/5 (retail)
DirectMusic: 0/5 (retail)
DirectPlay:  0/9 (retail)
DirectSound: 0/5 (retail)
DirectShow:  0/6 (retail)

---------------
Display Devices
---------------
        Card name: NVIDIA GeForce 8300 GS
     Manufacturer: NVIDIA
        Chip type: GeForce 8300 GS
         DAC type: Integrated RAMDAC
       Device Key: Enum\PCI\VEN_10DE&DEV_0423&SUBSYS_049410DE&REV_A1
   Display Memory: 883 MB
 Dedicated Memory: 115 MB
    Shared Memory: 767 MB
     Current Mode: 1440 x 900 (32 bit) (60Hz)
          Monitor: Generic PnP Monitor
      Driver Name: nvd3dum.dll,nvwgf2um.dll
   Driver Version: 7.15.0011.7824 (English)
      DDI Version: 9Ex
Driver Attributes: Final Retail
 Driver Date/Size: 10/7/2008 13:33:00, 5963776 bytes
      WHQL Logo'd: Yes
  WHQL Date Stamp:
Device Identifier: {D7B71E3E-4763-11CF-FE6D-9F2401C2CA35}
        Vendor ID: 0x10DE
        Device ID: 0x0423
        SubSys ID: 0x049410DE
      Revision ID: 0x00A1
      Revision ID: 0x00A1
      Video Accel: ModeMPEG2_A ModeMPEG2_C
 

[Denholm]

Flatiron, Level3 is bad news because they overcrowd their servers. Skuzzy gave a brilliant explanation of this one time. He mentioned Level3 is an intersection (which it is, in the Internet) and the traffic moving through their servers are vehicles. However, Level3 (the intersection) has no traffic lights, thus when traffic traveling through their intersection increases, the flow of traffic slows down causing packet loss (discos) and moderate to severe lag.

[shane720]

I am haveing the same problem.  Was running a Moto dsl modem from at&t.  It died.  I now have the at&t 2wire modem.  Constant disco after about 5 to 10 minutes without fail.

[whiteman]

man i'm discoing out of control for the last 2 days. I'm on AT&T also, I'm going fing blow a hole in my computer.

I'd like to think the flooding here in houston had something to do with this but i discoed 5 times in 1 hour during the scenario 2 weeks ago.

Target Name: N/A
         IP: 206.16.60.39
  Date/Time: 5/1/2009 10:40:11 PM to 5/1/2009 10:40:30 PM

Hop Sent Err PL% Min Max Avg  Host Name / [IP]
 1    20   0 0.0   0   0   0  [192.168.1.1]
 2    20   0 0.0   0   0   0  [192.168.0.1]
 3    20   0 0.0   6   7   6  adsl-70-240-207-254.dsl.hstntx.swbell.net [70.240.207.254]
 4    20   1 5.0   6   7   6  [151.164.244.193]
 5    20   0 0.0   7 204  46  bb1-g14-0.hstntx.sbcglobal.net [151.164.92.204]
 6    20   0 0.0  13 102  26  [69.220.8.57]
 7    20   0 0.0  14  24  16  gar6.dlstx.ip.att.net [12.122.79.65]
 8    20   0 0.0  15  17  15  cr2.dlstx.ip.att.net [12.122.138.34]
 9    20   0 0.0  14 137  22  gar23.dlstx.ip.att.net [12.122.138.161]
10    20   0 0.0  15  17  16  12-122-254-154.attens.net [12.122.254.154]
11    20   0 0.0  15 449  65  mdf1-bi8k-2-eth-1-3.dal1.attens.net [63.241.192.214]
12    20   0 0.0  15  17  16  [206.16.60.39]

[thndregg]

Adding myself to the list of disco kings. DSL is having to reconnect, no matter what I'm doing.



This happens a lot.

[Skuzzy]

If you are having trouble with your DSL having to re-sync or re-connect to your ISP, then you need to contact your ISP about it.

whiteman, you need to contact your ISP as well.

[thndregg]

If you are having trouble with your DSL having to re-sync or re-connect to your ISP, then you need to contact your ISP about it.

whiteman, you need to contact your ISP as well.

I already sent Qwest an e-mail. Hope to hear back from them soon.

[33Vortex]

Seems I have to contact customer support as well.