I live in spokane valley washington. Every so often, usually at 6-10 at night, i get horrible packet loss. I've seen it get beyond the 50% mark but its usually around 25% packet loss when it happens. I ping hop #2. That is, the first machine with an IP address that my modem connects too. that machines IP address is 73.99.172.1. No matter what I trace route to, that is the next machine beyond my router. Its between my router and that machine where the packet loss is occurring.
Resetting the modem always seems to fix the problem for at least one hour.
This problem has been going on for about 5 months now. Sometimes it gets worse, and will happen every couple hours. Before the last month or so it went months with out a problem.
In the last week its been 3 modems, 3 routers, and 4 technicians. None of which fixed the problem.
Tuesday's comcast guy replaced the ends on the coax cable that runs from the wall to the router. Called it good and left.
Wednesday's comcast guy said he found something at the neighbors house that was causing feedback into my line. Said it was fixed and left.
Thursday's comcast guy said he replaced something in the box where my cable comes down from the roof and goes into the house. Said it was fixed for sure. and left.
Today's comcast guy didn't do anything at all, said it looked fine. Told me there was no phone number to anyone local that might be able to help, and said he doesn't deal with anything beyond the pole(the pole my cable connects to just outside of my property)
My current setup is a motorola sb6141 router and a linksys EA6900 router.
SIGNAL:
Channel ID 41 42 43 44 45 46 47 48
Frequency 579000000 Hz 585000000 Hz 591000000 Hz 597000000 Hz 603000000 Hz 609000000 Hz 615000000 Hz 621000000 Hz
Signal to Noise Ratio 38 dB 38 dB 38 dB 38 dB 38 dB 38 dB 37 dB 37 dB
Downstream Modulation QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256
Power Level
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
6 dBmV 5 dBmV 5 dBmV 5 dBmV 5 dBmV 5 dBmV 4 dBmV 4 dBmV
Upstream Bonding Channel Value
Channel ID 1 2 3
Frequency 36800000 Hz 30300000 Hz 23800000 Hz
Ranging Service ID 3338 3338 3338
Symbol Rate 5.120 Msym/sec 5.120 Msym/sec 5.120 Msym/sec
Power Level 44 dBmV 44 dBmV 44 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM
[3] QPSK
[3] 64QAM
Ranging Status Success Success Success
Signal Stats (Codewords) Bonding Channel Value
Channel ID 41 42 43 44 45 46 47 48
Total Unerrored Codewords 93759066 92801893 92815095 92823281 92797943 92799111 92800198 92815093
Total Correctable Codewords 0 0 0 0 12 9 42 20
Total Uncorrectable Codewords 573 592 566 565 621 662 608 604
LOGS:
Mar 21 2014 15:28:48 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 15:23:47 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 15:22:53 5-Warning T202.0 Lost MDD Timeout;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 15:22:29 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 14:32:46 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:28 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 14:20:59 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 13:49:21 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to T4 timeout ;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 13:43:04 3-Critical R04.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 13:42:13 5-Warning T202.0 Lost MDD Timeout;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 13:41:49 3-Critical T05.0 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Mar 21 2014 13:16:53 5-Warning Z00.0 MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:20 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Jan 01 1970 00:00:15 6-Notice N/A Cable Modem Reboot due to power reset ;CM-MAC=90:3e:ab:65:ce:8a;CMTS-MAC=00:1d:45:70:87:65;CM-QOS=1.1;CM-VER=3.0;
Modem is brand new, plugged in by the comcast tech on Thursday.
I'm left with 3 ideas:
1. keep having comcast techs come out and hope they get here at a time when the packet loss occurs, and hope that they have the knowledge to figure it out. (most of these guys don't seem to know what a trace route is and even denied that my Hop #2 was a comcast device)
2. send a massive amount of voltage up the wire and hope it breaks whatever is causing the problem.
3. DSL(id rather die)
They are really starting to BUM me out. and there shirts have been worn out in the nipple region.
↧