Forum Discussion

toxicpelican's avatar
toxicpelican
New Contributor

Frequent intermittent connection drops

Hi all!

So I've been having a problem with my cox internet for the past ~6mo at least. I've been experiencing intermittent connection drops. Most of the time not bad enough for the modem/router to show any errors on the lights, or on the computer to show a dead connection, but anything that is currently using the internet dies/freezes where its at. For example youtube or twitch.tv streams will just stop and cut out for 5sec-1min or so, internet pages will just freeze up and not load, or if I'm in game (lately BF1 in origin and Path of Exile in steam), it'll lock up for a few seconds and then disconnect me from the servers.

I've had the cox techs out 4 times now to deal with this and so far they have:

  • Made sure the modem is off the first splitter
  • Got rid of other splitters and disconnected lines not being used for tvs
  • Replaced fittings with good compression fittings and snugged them up
  • Changed the cable line from the wall to the modem to a new good line
  • Checked the signals etc and said they were all good?
  • They looked at the *node? right near the house (the round green box) and they said a few things there looked not great (he changed which port my house was plugged into just to check, and one of the ports was actually getting live power, you could touch it and get a small shock, and a few of the numbers when he checked it were off), and a line tech supposedly came out and worked on it a few days later, but I didn't have any interaction with him

I have done/checked:

  • Verified the issue on multiple hard wired computers
  • Changed the cat6 cable
  • Changed which port I was using in the switch
  • Plugged right into the modem
  • Bought a new modem (netgear cm600)
  • Made sure the modem is using cox's newest firmware (1.01.06)
  • Bought a new router (asus ac1900)
  • Updated router firmware
  • Disabled the firewalls on the router
  • Disabled the windows firewalls and virus scanners and any other programs I could
  • Verified with ping plotter that the connection just dies/goes to 100% packet loss
  • Updated my NIC drivers
  • Disabled energy saving on the NIC and disabled interrupt moderation on the NIC

At this point, I'm very frustrated in dealing with this, and am running low on ideas what to do, since cox either says nothings wrong, or can't/won't fix it/don't care. We pay a ton for cox service, and it's largely unusable for what I want to do. If there was some other provider I would jump ship, but of course there isn't.

Other things of possible importance: there is a filter installed just before the modem, and an amp down in the main box.

My modem is a Netgear cm600, and the router is an Asus AC1900, and the switch is a Netgear 8 port gigabit switch, and I opened up the walls in the house to look at the cable, it appears to be RG6 (house was built in 2003), and has a compression fitting going to the modem end of the cable.

Modem data:

Startup Procedure

Procedure Status Comment
Acquire Downstream Channel 795000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enable BPI+
IP Provisioning Mode Honor MDD IPv4 only
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 27 795000000 Hz 0.6 dBmV 42.3 dB 0 0
2 Locked QAM256 25 783000000 Hz 0.8 dBmV 42.2 dB 0 0
3 Locked QAM256 26 789000000 Hz 1.0 dBmV 42.4 dB 0 0
4 Locked QAM256 46 909000000 Hz 1.6 dBmV 42.0 dB 0 0
5 Locked QAM256 28 801000000 Hz 0.5 dBmV 42.0 dB 0 0
6 Locked QAM256 29 807000000 Hz 0.8 dBmV 42.4 dB 0 0
7 Locked QAM256 30 813000000 Hz 0.7 dBmV 42.4 dB 0 0
8 Locked QAM256 31 819000000 Hz 0.6 dBmV 42.3 dB 0 0
9 Locked QAM256 32 825000000 Hz 0.8 dBmV 42.4 dB 0 0
10 Locked QAM256 33 831000000 Hz 0.6 dBmV 42.2 dB 0 0
11 Locked QAM256 34 837000000 Hz 0.5 dBmV 42.2 dB 0 0
12 Locked QAM256 35 843000000 Hz 1.0 dBmV 42.0 dB 0 0
13 Locked QAM256 36 849000000 Hz 1.1 dBmV 42.2 dB 0 0
14 Locked QAM256 43 891000000 Hz 2.1 dBmV 42.1 dB 0 0
15 Locked QAM256 44 897000000 Hz 2.4 dBmV 42.3 dB 0 0
16 Locked QAM256 45 903000000 Hz 2.5 dBmV 42.4 dB 0 0
17 Locked QAM256 47 915000000 Hz 1.6 dBmV 43.2 dB 0 0
18 Locked QAM256 48 921000000 Hz 1.5 dBmV 43.0 dB 0 0
19 Locked QAM256 57 927000000 Hz 0.5 dBmV 42.5 dB 0 0
20 Locked QAM256 58 933000000 Hz 0.2 dBmV 42.5 dB 0 0
21 Locked QAM256 59 939000000 Hz 0.2 dBmV 42.5 dB 0 0
22 Locked QAM256 60 945000000 Hz -0.4 dBmV 41.9 dB 0 0
23 Locked QAM256 61 951000000 Hz -0.5 dBmV 41.9 dB 0 0
24 Locked QAM256 62 957000000 Hz 0.3 dBmV 42.1 dB 0 0
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 2 5120 Ksym/sec 25800000 Hz 47.8 dBmV
2 Locked TDMA and ATDMA 1 2560 Ksym/sec 17600000 Hz 46.8 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 32200000 Hz 47.3 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 38600000 Hz 47.8 dBmV

And the current modem error logs:

Time

Priority Description
2017-01-20, 23:38:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2017-01-18, 02:19:56 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2017-01-18, 02:19:17 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2017-01-18, 02:19:13 Notice (6) TLV-11 - unrecognized OID;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:29:53 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-12-24, 00:26:35 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-12-24, 00:26:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:26:34 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:26:19 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:26:19 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:26:04 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:26:04 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:25:48 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:25:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:24:46 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:24:40 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-24, 00:19:10 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-22, 07:01:05 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-22, 07:01:03 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-22, 07:01:02 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-22, 07:00:59 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-21, 09:20:44 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 23:24:44 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 15:19:15 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-12-20, 14:58:58 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
2016-12-20, 14:58:56 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 14:58:56 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 14:58:42 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 14:58:42 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 14:58:26 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 14:58:26 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 14:58:11 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 14:58:11 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 14:57:06 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-20, 07:17:19 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-18, 22:01:28 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-18, 18:50:20 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
2016-12-18, 16:51:01 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.0;CM-VER=3.0;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4

Seriously, ANY help would be appreciated. I just want to be able to game/watch shows etc when I have time off.

Thanks

8 Replies

Sort By
Most LikedOldestNewest
Replies have been turned off for this discussion
  • Tecknowhelp's avatar
    Tecknowhelp
    Valued Contributor II

    "one of the ports was actually getting live power, you could touch it and get a small shock, and a few of the numbers when he checked it were off), and a line tech supposedly came out and worked on it a few days later, but I didn't have any interaction with him"

    Sounds like a bad power supply on the node.  I would suggest trying to collect information on what exactly was done. Call and ask to talk to Tier 2, who should be able to get you in touch with the CAG(customer advocacy group) who have the ability to look that up. What you are mainly looking for is the ticket number so you can find out how the ticket was resolved and if the issue is still on going. 

    You could also try calling the electrical company and see if they are doing any work or know of any problems in the area.  Finally, try talking to other people on your street. If the entire node is having a problem, then it's likely other customers in the area are effected. The more of them you can get to call up and complain, the better.

  • cpljp's avatar
    cpljp
    Contributor

    One of the ports off the tap (the passive device in the green box) was getting live power as it was likely a power passing tap with a current limiter that was supplying 90 volts of power. Before packet switched phone, Cox used circuit switched phone technology which consistent of an NIU being placed on the side of the house and using .3 amps. The NIU was powered via the plant and thus a current limiter was placed in the tap to pass power alongside RF via the tap port. The tech may have forgotten to open the tap plate and removed the current limiter. Nonetheless I doubt that was your issue at least anymore since you would be logging errors if power was still hitting your equipment.

    Seeing the errors you're logging could mean there is intermittent noise in your node. You're best bet is for someone on here to pull up tickets for the node and see if there is any tickets online to track down noise or they can IM a maintenance tech and have the tech see if there is noise being logged

  • Becky's avatar
    Becky
    Moderator
    Hi Toxicpelican,

    According to the ticket from 12/21/16, the maintenance tech traced the problem to a defective amp on a pole down the street from your house. The amp was replaced. There have been no other reports from customers on your street since that date.

    You mentioned using an Asus AC1900 router. Have you tested your connectivity without the router? Pick a time of day when you normally experience connectivity issues while gaming. Connect your Netgear CM600 directly to your computer with an ethernet cord, and power cycle the Netgear. Proceed with your game as normal. Do you experience any freezing or server disconnects during this time?

  • toxicpelican's avatar
    toxicpelican
    New Contributor

    Hi Becky,

    Thanks for the response, and to the other posters as well (seriously, I appreciate it). I have tried connecting directly to the Netgear CM600 modem and power cycling it since the last tech was out here (12/21), as well as direct connecting to the previous modem as well. The problem still occurs. However, I will try it again later today when I wake up, just got off of night shift.

    As far as the other users in the area, no one else in my neighborhood is much of an internet user, it's a small group of houses ~14, and it's all older residents and a few younger kids, no one I know of is a gamer. If it wasn't for the gaming, I more than likely wouldn't notice/or care about the issue.

    But, I'll give the direct connection to the modem and a power cycle another try later today, and post back here.

    Thanks,

    Jeff

  • Tecknowhelp's avatar
    Tecknowhelp
    Valued Contributor II

    Becky said:
    a defective amp on a pole down the street from your house. The amp was replaced.

    I bet the amp died because of a bad power supply. The amp board was replaced, but not the power supply, and now it's causing intermittent issue. Happened to me when I was in a area with old/bad electrical transformers... or maybe it was all the "special" farmers in the area. Either way it's highly likly the old problem some how connects to the current problem. 

  • toxicpelican's avatar
    toxicpelican
    New Contributor

    Becky said:
    Hi Toxicpelican,
    You mentioned using an Asus AC1900 router. Have you tested your connectivity without the router? Pick a time of day when you normally experience connectivity issues while gaming. Connect your Netgear CM600 directly to your computer with an ethernet cord, and power cycle the Netgear. Proceed with your game as normal. Do you experience any freezing or server disconnects during this time?

    Becky,

    Tried this over several hours this afternoon and evening. Stayed plugged into the router/switch like normal and got into game/streaming, verified that the connection dropped several times. Plugged directly into the Netgear CM600 modem and restarted it and the computer, got back into game/streaming, same problem, dropped connections and severe packet loss. Gave it a few hours and tried it in with the router again, and then back to the direct line to the modem, same problem. Dropped connections and big chunks of packet loss. Same problem for months now.

    I also changed out the coax barrel connector in the wall plate that goes from house wiring to the coax line to the modem for one of the good 3GHz rated ones with the blue center. No change, same problem. I expected that, but I figured I'd rule out one more point of failure. I also tried removing the filter that's in place just before the cable modem on the coax line, the only thing it changed was the downstream power went from the -2 to the +2 range up to +10-13 range. And the connection kept dropping just the same.

    My connection is basically unusable for what I got the service for. Please advice.

    -Jeff

  • toxicpelican's avatar
    toxicpelican
    New Contributor

    Here's also the modem event log from today thus far:

    Time

    Priority Description
    2017-01-22, 22:26:56 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 22:26:14 Notice (6) TLV-11 - unrecognized OID;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 22:18:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 22:18:20 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 22:18:14 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 22:05:53 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 21:47:40 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:15:38 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:15:36 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:15:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:15:02 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:14:52 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:14:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:14:32 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:14:31 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:14:30 Critical (3) No UCDs Received - Timeout;;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:14:13 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:14:12 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:13:56 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:13:37 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:13:35 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:13:34 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:09:25 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;
    2017-01-22, 18:09:24 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:09:24 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:09:09 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:09:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:08:54 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:08:54 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:08:40 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:08:40 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:07:28 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 18:07:22 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 17:38:20 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 17:28:42 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-22, 17:28:09 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2017-01-18, 02:19:17 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=b0:7f:b9:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.1;CM-VER=3.0;
    2016-12-24, 00:29:53 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=b0:7f:b9:32:99:80;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:32:99:80;CMTS-MAC=00:1d:a2:e7:be:75;CM-QOS=1.0;CM-VER=3.0;
    Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4
  • Becky's avatar
    Becky
    Moderator
    Hi Toxicpelican,

    I ran a few tests this morning and noticed intermittent packet loss to your modem. I think another service call is warranted at this point. There is still something going on that we have yet to identify. I'm sorry for all of the frustration this is causing! Please email my team at cox.help@cox.com so we can get an appointment scheduled for you. Be sure to include your full name, address, and a link to this page in your email. We'll get to the bottom of this for you!