connection drops constantly telling me connection is limited

heres the log, not sure what to make of all of this. 

Thanks

Downstream Channel Bonding Value Index Lock Status Frequency SNR Power Modulation

12345678910111213141516
LockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLockedLocked
519 MHz573 MHz591 MHz567 MHz555 MHz561 MHz543 MHz579 MHz609 MHz603 MHz597 MHz615 MHz621 MHz633 MHz639 MHz585 MHz
40.3 dB33.3 dB39.5 dB0.0 dB39.0 dB39.4 dB40.2 dB38.6 dB39.6 dB39.3 dB39.2 dB39.4 dB39.2 dB36.7 dB38.0 dB39.6 dB
3.3 dBmV0.2 dBmV1.9 dBmV1.5 dBmV1.4 dBmV1.8 dBmV2.7 dBmV0.6 dBmV2.0 dBmV1.6 dBmV1.4 dBmV1.9 dBmV1.5 dBmV0.0 dBmV0.0 dBmV1.8 dBmV
256 QAM256 QAM256 QAMunknown256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM256 QAM

 

Upstream Channel Bonding Value Index Lock Status Frequency Symbol Rate Power Level Modulation Channel ID

1234
LockedLockedLockedLocked
30.6 MHz18.5 MHz23.3 MHz37.0 MHz
5120 Ksym/sec2560 Ksym/sec5120 Ksym/sec2560 Ksym/sec
35.8 dBmV34.5 dBmV34.8 dBmV36.3 dBmV
ATDMATDMAATDMAATDMA
1191012

 

CM Error Codewords   Unerrored Codewords Correctable Codewords Uncorrectable Codewords

3239427432286701348428570898111874877514262631719834827427273223084383255972584829792320023234679938257303148232346984183084429921290347554032346971862774558911
589118226110231133764580901773420069884893024899935891189547054135312318194404653569
720175150105006265831372178715258427754373539652941558759931443087571155971

 

this log is of today and a page of yesturday, not sure if thats enough:

Sun Nov 05 18:20:43 2017Notice (6) WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:161) - Reason:INTERFERENCE
Sun Nov 05 18:05:18 2017Critical (3) Http login:admin from IP address 192.168.0.10
Sun Nov 05 18:04:12 2017Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sun Nov 05 17:59:59 2017Critical (3) Http login:jamestranx2x2@gmail.com failed from IP address 192.168.0.10
Sun Nov 05 17:58:57 2017Warning (5) MDD message timeout;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 17:58:06 2017Critical (3) Http login:jamestranx2x2@gmail.com failed from IP address 192.168.0.10
Sun Nov 05 17:57:25 2017Warning (5) MDD message timeout;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 17:34:01 2017Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sun Nov 05 17:33:45 2017Warning (5) MDD message timeout;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 17:20:29 2017Notice (6) WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sun Nov 05 17:19:37 2017Warning (5) MDD message timeout;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 17:05:24 2017Notice (6) WiFi Interface [wl1] set to Channel 40 (Side-Band Channel:36) - Reason:INTERFERENCE
Sun Nov 05 17:03:50 2017Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sun Nov 05 17:00:55 2017Warning (5) MDD message timeout;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 15:19:51 2017Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 15:19:47 2017Warning (5) MDD message timeout;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 15:13:47 2017Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 15:13:43 2017Warning (5) MDD message timeout;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 15:02:43 2017Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 14:59:23 2017Warning (5) MDD message timeout;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 14:33:07 2017Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sun Nov 05 14:17:05 2017Warning (5) MDD message timeout;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 11:04:06 2017Notice (6) WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sun Nov 05 11:02:09 2017Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sun Nov 05 10:48:59 2017Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:44) - Reason:INTERFERENCE
Sun Nov 05 10:18:51 2017Notice (6) WiFi Interface [wl1] set to Channel 44 (Side-Band Channel:48) - Reason:INTERFERENCE
Sun Nov 05 10:07:46 2017Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sun Nov 05 10:03:45 2017Notice (6) WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:161) - Reason:INTERFERENCE
Sun Nov 05 09:48:40 2017Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:44) - Reason:INTERFERENCE
Sun Nov 05 09:33:33 2017Notice (6) WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:161) - Reason:INTERFERENCE
Sun Nov 05 09:31:43 2017Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sun Nov 05 09:16:35 2017Notice (6) WiFi Interface [wl0] set to Channel 6 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sun Nov 05 09:03:23 2017Notice (6) WiFi Interface [wl1] set to Channel 44 (Side-Band Channel:48) - Reason:INTERFERENCE
Sun Nov 05 08:48:19 2017Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:44) - Reason:INTERFERENCE
Sun Nov 05 08:03:08 2017Notice (6) WiFi Interface [wl1] set to Channel 44 (Side-Band Channel:48) - Reason:INTERFERENCE
Sun Nov 05 07:17:55 2017Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:44) - Reason:INTERFERENCE
Sun Nov 05 06:47:45 2017Notice (6) WiFi Interface [wl1] set to Channel 44 (Side-Band Channel:48) - Reason:INTERFERENCE
Sun Nov 05 03:16:57 2017Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:44) - Reason:INTERFERENCE
Sun Nov 05 02:16:42 2017Notice (6) WiFi Interface [wl1] set to Channel 44 (Side-Band Channel:48) - Reason:INTERFERENCE
Sat Nov 04 22:43:45 2017Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 22:15:45 2017Notice (6) WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 22:13:32 2017Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 21:45:33 2017Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:44) - Reason:INTERFERENCE
Sat Nov 04 20:28:01 2017Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 19:42:46 2017Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 18:12:17 2017Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 17:59:42 2017Notice (6) WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 16:31:15 2017Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b4:2a:0e:c8:b7:92;CMTS-MAC=00:01:5c:74:7c:5f;CM-QOS=1.1;CM-VER=3.0;
Sat Nov 04 16:29:20 2017Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:44) - Reason:INTERFERENCE
Sat Nov 04 16:14:15 2017Notice (6) WiFi Interface [wl1] set to Channel 161 (Side-Band Channel:157) - Reason:INTERFERENCE
Sat Nov 04 16:11:41 2017Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 15:59:10 2017Notice (6) WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:153) - Reason:INTERFERENCE
Sat Nov 04 15:44:03 2017Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:44) - Reason:INTERFERENCE
Sat Nov 04 15:28:59 2017Notice (6) WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:153) - Reason:INTERFERENCE
Sat Nov 04 15:26:28 2017Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 15:13:54 2017Notice (6) WiFi Interface [wl1] set to Channel 40 (Side-Band Channel:36) - Reason:INTERFERENCE
Sat Nov 04 15:11:23 2017Notice (6) WiFi Interface [wl0] set to Channel 11 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 14:58:49 2017Notice (6) WiFi Interface [wl1] set to Channel 161 (Side-Band Channel:157) - Reason:INTERFERENCE
Sat Nov 04 14:56:14 2017Notice (6) WiFi Interface [wl0] set to Channel 1 (Side-Band Channel:N/A) - Reason:INTERFERENCE
Sat Nov 04 14:43:43 2017Notice (6) WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:153) - Reason:INTERFERENCE
Sat Nov 04 14:28:38 2017Notice (6) WiFi Interface [wl1] set to Channel 157 (Side-Band Channel:161) - Reason:INTERFERENCE
Sat Nov 04 14:13:33 2017Notice (6) WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:153) - Reason:INTERFERENCE
Sat Nov 04 13:58:27 2017Notice (6) WiFi Interface [wl1] set to Channel 48 (Side-Band Channel:44) - Reason:INTERFERENCE
Sat Nov 04 13:43:22 2017Notice (6) WiFi Interface [wl1] set to Channel 149 (Side-Band Channel:153) - Reason:INTERFERENCE

 

I hope you guys can help me with this problem.

5 REPLIES
Highlighted

Re: connection drops constantly telling me connection is limited

also forgot to mention that I disabled wifi

Established Sharer

Re: connection drops constantly telling me connection is limited

Being a Windows 7 and Win10 user myself, I'll bet that the message 'Connection is limited' is being generated by a Microsoft operating system.  It does not come from the modem and probably not from your router, if you are using a separate one.  It's telling you that the computer can't find any one of a group of Microsoft servers, so it believes you aren't connected to the internet at all.  There's a reason for that:

 

When you look at the signal logs, you're going to see three lines labeled

Unerrored Codewords

Correctable Codewords

Uncorrectable Codewords

Some of these have very large numbers in the tables for each of the 16 DS channels assigned to your modem for internet data transmission.

 

The first row is Unrerrored Code Words.  These are internet data packets correctly decoded by the modem.    if your incoming data was perfectly split up among all 16 DS channels every time, those numbers would all be exactly the same; in the real world they should be within about 10% of each other.

 

Next row down you see Correctable Codewords.  Your modem has enough smarts to be able to reconstruct data words that have partially been partially garbled during transmission within the cable network.  These aren't  perfect but they don't cause major delays to your data.  Correctable error counts range from zero to 100 or more per million total codewords on each channel.  Higher error counts that appear only on specific channels point to outside interference or equipment misalignment, not a good thing.

 

And the bottom row  is Uncorrectable Codewords.  You guessed it, these are too badly damaged to be recovered, so they have to be resent from the source which is usuallly out ion the worldwide web, external to TWC and Spectrum's cable network.  When a modem restarts, it self-adjusts to the cable system over the first 12 hours or so.  During this interval you will see several hundred UCCWs, fter which they should stop increasing.  On a healthy cable network this number should always be less than the number of Correctable Errors on every channel.  Again, a number that grows is a sign of trouble.

 

The WiFi messages in the event log further down tell us that your modem is scanning channels, not locked on one that your devices can find every time each one wants to chat.  You need to disable WiFi scanning by assigning it to fixed channels, one each in the 2.4 and 5.8 GHz bands.  On 2.4 (wi0) the defaults are 1, 6, and 11 so avoid those.  Go for 3, 4,8 or 9 which  are less likely to be used.  On 5.8 GHz (wi1)  the channel numbers are stepped by 4 instead and 36, 40, 44, or 48 are usually good to try first, unless all your neighbors also read this advice and set up their routers' WiFi exactly the same way.  But trust me, nobody ever precisely follows technical advice they read here in these forums! 

Expert

Re: connection drops constantly telling me connection is limited

You have severe broadcast tv ingress from tv channels 28-29-30-31

Something is corroded loose, chewed and or open splitter ports., if not obvious, call TWC

 

Re: connection drops constantly telling me connection is limited

thank you both

Expert

Re: connection drops constantly telling me connection is limited

Lock the 2.4 gHz to ch's 3 or 8, On the 5.8 gHz wireless band, either turn it off or lock it onto a channel halway between the ones it scans.

 

Your major issue is bad connections allowing the ingress that's resetting the modem, that also fouls up the wireless as they reset as well.