Contour Slave Box Reboots Every 13 Minutes
Just got Contour installed yesterday and the slave box in my bedroom constantly reboots. I started to take note of it to see if there’s a pattern, and noticed that it would turn off every 13 minutes, on the spot. It would take another 5 minutes before I see the welcome screen. When it turns off, I can’t turn it back on with the remote or the power button on the box. I would need to unplug the power and plug it back in, or wait 5 minutes for it to turn back on by itself. The box is placed on a shelf, not enclosed, so I don’t think heat is an issue. This is very annoying, especially when watching sports.2KViews0likes2CommentsMotorola Surfboard SB6141 Lost Connection Issues
My modem keeps dropping connection the last few days and last night it was really bad. It was constantly trying to reboot. Here is what i was able to capture before it tried to reboot again. Time Priority Code Message Jan 01 1970 00:28:45 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:44 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:40 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:24 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:02 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:28:02 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:42 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:41 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:22 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:21 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:02 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:27:02 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:44 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:43 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:30 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:30 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:26:16 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:25:53 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:25:34 3-Critical R02.0 No Ranging Response received - T3 time-out;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0; Jan 01 1970 00:25:33 3-Critical R07.0 Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=b8:16:19:2f:f4:c3;CMTS-MAC=a4:4c:11:8b:47:a0;CM-QOS=1.1;CM-VER=3.0;Solved16KViews0likes3CommentsIs there something wrong with the Cisco Explorer 8642HDC Firmware
I recently had the trusty Scientific Altanta DVR replaced after a Service Call about being unable to view ON Demand movies. The new Cisco box worked ok for few days until we tried to view a recorded program. It stuttered and was generally unwatchable on the playback. That started to occur watching live TV too. Was this a bad disk? Another symptom was that viewing the guide shrank the live TV picture as expected, but when exiting from the Guide, the picture remained small in the upper right quadrant. Changing channels didn't reset. A complete reset by unplugging power was the only way to get it back. The continued playback stutter made me visit a store for an exchange. The second unit seemed OK, but suffered from the same stuuer playback. I left the stuttering program on what I thought might be bad disk, and subsequent recorded shows seemed fine. This morning I noticed the program playing through this box, was about 5 seconds delayed from the same program playing through a non-DVR box, where previously they had been in perfect sync. I clicked the guide, and the same shrunken picture state happened. I have been searching issues with the Cisco boxes and the stutter is mentioned a lot. Is the box subject to overheating - it is in a cabinet with glass doors. Can I get a Scientific Atlanta DVR Cable box. I am seriously considering a move to satellite36KViews0likes18Comments