100 MBS for two days then under 2MBps - Time Warner Internet

#1
This question is about "100 MBS for two days then under 2MBps", with Time Warner Cable internet and apps. Hello,

I bought a CM600 Netgear modem and when I first hooked up my internet cable to TWC I was getting 100Mbps. This lasted maybe an hour before dropping down to 1Mbps. I decided to root out any physical problems first. I found that there was a 3way splitter on the line as well as a barrel in the wall that looked old. I ended up running a solid, single, non-break line from TWC's cable on the outside of the house all the way into the modem itself. There are no breaks or separations in the line at all.

I maintained 100Mbps for roughly two hours before it dropped to 0.5Mbps again and stayed there. When I got online to talk to the techs, they pushed something to my modem and i maintained 100Mbps for roughly one day. In the morning, I found myself back to 0.5Mbps.

I talked to another tech who then stated he was "pushing advanced modem settings" and the problem should go away for good. It has been two days at 100Mbs and I thought the issue was gone. Nope! This morning I was back to 1.4Mbps.

I just got done with a chat and another tech stated my signal levels to the modem are wrong and pushed "more advanced modem settings."

I logged into CM600's interface but the logs are wildly unhelpful and I cannot really see anything about power levels or anything of that nature in the GUI.

Anyone know of a way to get this thing to stay at 100Mbps? It's rated for 300Mbps on TWC's line but I am only on the 100Mbps package. i understand I wont get 100Mbps 24/7, but less than 2 Mbps is crazy.


[TABLE]

Time

Priority

Description


2016-11-11, 07:41:18

Error (4)

Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-11, 07:41:18

Error (4)

Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-11, 07:41:17

Warning (5)

ToD request sent - No Response received;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.0;CM-VER=3.0;


2016-11-11, 07:41:05

Notice (6)

Overriding MDD IP initialization parameters; IP provisioning mode = IPv6


2016-11-11, 07:41:01

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.0;CM-VER=3.0;


2016-11-11, 07:40:54

Error (4)

Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-11, 07:40:54

Error (4)

Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-11, 07:40:09

Critical (3)

Resetting the cable modem due to docsDevResetNow


2016-11-11, 07:39:28

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.0;CM-VER=3.0;


2016-11-11, 07:38:32

Critical (3)

Resetting the cable modem due to docsDevResetNow


2016-11-11, 07:17:02

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-11, 06:50:46

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-11, 06:35:12

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-11, 06:19:15

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 13:00:33

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:07:40

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:07:33

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:06:43

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:06:40

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:06:38

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:06:38

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:06:34

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:06:06

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:06:05

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:06:03

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:06:03

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-10, 11:05:55

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-09, 19:50:00

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-09, 19:32:31

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-09, 07:55:38

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-09, 00:09:45

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-08, 09:09:29

Critical (3)

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.1;CM-VER=3.0;


2016-11-07, 09:09:26

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.0;CM-VER=3.0;


2016-11-07, 08:47:03

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.0;CM-VER=3.0;


2016-11-06, 18:21:10

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.0;CM-VER=3.0;


Time Not Established

Critical (3)

SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;


Time Not Established

Warning (5)

DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.0;CM-VER=3.0;


Time Not Established

Notice (6)

Honoring MDD; IP provisioning mode = IPv4


Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.0;CM-VER=3.0;


Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:33:4b:30;CMTS-MAC=00:01:5c:77:a8:56;CM-QOS=1.0;CM-VER=3.0;


[/TABLE]


This topic covered 100 MBS for two days then under 2MBps, and TWC cable internet service.
 
Top