This has the indications of a classic case low signal strength, one cause of which is "bad" connection. "Corrosion" (oxidation) builds up in socketed connections, and affects electrical continuity. Unhooking and reconnecting all of the cable connections that are available to you is a place to start. Putting an amplifier in the cable to the modem is also a potential solution. Re-wiring the cable so that there is a first splitter that is binary (2x), with one half going directly to the cable modem and the other half going to a nx splitter to feed all of the TVs will increase signal strength to the modem.
etc. Fred Holmes At 11:47 PM 5/8/2010, Richard P. wrote: >During the last week, my cable modem for Cox Cable loses its Internet >connection about once or twice a day. When troubleshooting, the light >that indicates the cable connection on the Linksys modem, model >"BEFCMU10", is not illuminated. If I reboot the modem, it comes up >fine and I get adequate speeds through the connection. After calling >Cox, the only thing they can offer is a service call for which I will >be charged if it turns out that the problem is after their connection. > >I have also noticed a slight degradation in the analog TV signal from >Cox during the last week as well. > >Should I just go ahead and replace the modem to see if that makes a >difference? It would be less than the service call. > >Suggestions please. > >FYI, my Visualware Speed Connection test is: > >Test Type: Application Speed >Location: USA: Dulles, Virginia >Download Speed: 24652 Kbps >Upload Speed: 3380 Kbps >Speed Consistency: 80 % >Round Trip Time: 15 ms >Max Delay: 77 ms >Average Delay: 5 ms >Bandwidth: 24652 Kbps >Max Route Speed: 34952 Kbps >Route Concurrency: 1 > >2 connection problems found, click the to learn more. > >MSTR01: The data flow for this test is too erratic > >Although the speed achieved may match expectation for the connection, >a low data flow QoS score means that the data flow between the server >and the workstation was not consistent. There can be several reasons >for this such as data congestion along the route or data loss which >invokes recovery. The lower the QoS percentage, the more erratic the >data flow. Many applications can be severely affected by poor data >flow quality regardless of data throughput speed, for example media >applications such as video or voice may become jerky. Voice (VoIP) >telephony will become garbled. If you suspect that the connection was >in use by another application try running the test again to validate >if the problem is persistent. > > MSMD01: TCP is waiting too long for data > >The test recorded a TCP maximum delay that exceeded the natural TCP >forced idle delay as a result of the connection's trip time. This >indicates that there may be problems with consistent data flow between >the server and the client. A poor data flow QoS reading is also likely >if the max TCP delay is much higher in comparisons to the trip time. >Common reasons for this type of problem are packet loss and >duplicates. The test graph view will show the TCP delay over the time >of the test. Height and width of the 'orange' delay line shows the >delay consistency. > >Thanks in advance, > >Richard P. > > >************************************************************************* >** List info, subscription management, list rules, archives, privacy ** >** policy, calmness, a member map, and more at http://www.cguys.org/ ** >************************************************************************* ************************************************************************* ** List info, subscription management, list rules, archives, privacy ** ** policy, calmness, a member map, and more at http://www.cguys.org/ ** *************************************************************************
