SYNC Timing Synchronization failure - Loss of Sync AND No Ranging Response received - T3 time-out - All Day Long


You are watching: Sync timing synchronization failure loss of sync

*

I have been using a (purchased) SurfBoard SB6141 for years with little to no issues. Recently I have been having a hell of a time with my Comcast connection. If I unplug the modem it usually gets better for a little bit. Otherwise the connection constantly drops and cripples all my devices. My August Home lock tells me its been disconnected all the time. My Nest Camera drops all day long. Sometimes I am unable to stream anything and/or have major buffering issues while streaming. I unplug the modem and router and it temporarily helps. I also work from home so its slowly driving me crazy.

Yesterday I called Comcast (when I was getting consistently terrible speeds) and they sent a reset command which temporarily made it better. At the same time I scheduled a technician to come out and diagnose the problem (tomorrow morning). I also ordered a new SB6183 just in case its a modem problem. I have tried a new co-axial cable from the wall (only outlet being used) to the modem but am getting the same behavior. The more I read the more I am thinking it's a problem with the Comcast wiring outside the house.

Just wondering if anyone can look at the Signal and Logs (below) and give me feedback as to whether its a modem or connection problem? If it's a connection problem I will probably return the SB6183.

See more: Does Anyone Know How To Get Dimer Badge 2K17 General Discussions

If its a modem problem I very well might cancel the Comcast appointment (so I do not get charged for it being a modem problem). This is the deepest I have dove into the inter-workings of a modem so thanks for any and all enlightenment!

Logs from this morning (same as below)

TimePriorityCodeMessage

May 26 2019 8:52:413-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 8:03:043-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 8:00:583-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 7:58:513-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 7:58:503-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 7:21:383-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 7:19:593-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 7:17:293-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 7:17:263-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 6:16:153-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 6:16:103-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 6:14:453-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 6:14:433-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 6:05:583-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 6:05:583-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 5:55:203-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 5:54:183-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 5:52:353-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 5:52:233-CriticalT05.0SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;

May 26 2019 5:50:203-CriticalR02.0No Ranging Response received - T3 time-out;CM-MAC=78:96:84:fa:4e:15;CMTS-MAC=00:01:5c:64:3e:53;CM-QOS=1.1;CM-VER=3.0;