The internet in my house has been extremely inconsistent for months now. We've changed modems out 3 times and changed wireless routers out twice. We recently got a gateway modem from Cox hoping it may help the problem, it has not.
The previous modems and now this one all do about the same thing where they will run for an hour or so then suddenly drop internet connection and blink out all the lights except the power, they then turn back on one by one and begin blinking again restarting the one by one lighting up sequence. I've used the reset button on the modem, I've unplugged for a few minutes and plugged back in, and sometimes it works for a few minutes but then repeats going offline and restarting process again.
I've had techs come out to the house twice and the first time he said we were getting a 'nasty signal' so he went to the pole changed same of the wiring from the pole to the house and went back to check that signal again, it must have looked good at that point and he left after making sure my internet was working, it did work for about three hours and then began the same restarting process again.The next time the guy came out i explained the issue and he changed out some of the coax ends and left. not more than 20 minutes after he left the modem began its restarting process again.
I've read some of the other articles here and it seems a number of people are having similar issues, but none of the suggestions they received have seemed to work for me. I'm posting my event log and connection status but i am not sure what they will say if anything since the internet is actually working at this time. Thanks in advance for any advice or help.
|
| Startup Procedure |
| Procedure |
Status |
Comment |
| Acquire Downstream Channel |
807000000 Hz |
Locked |
| Connectivity State |
OK |
Operational |
| Boot State |
OK |
Operational |
| Configuration File |
OK |
138001_vm2.0_d.cfg |
| Security |
Enabled |
BPI+ |
|
|
| Downstream Bonded Channels |
| Lock Status |
Modulation |
Channel ID |
Symbol rate |
Frequency |
Power |
SNR |
DOCSIS/EuroDOCSIS locked |
| Locked |
QAM256 |
211 |
5360 Ksym/sec |
807000000 Hz |
-15.8 dBmV |
33.0 dB |
DOCSIS |
| Locked |
QAM256 |
209 |
5360 Ksym/sec |
795000000 Hz |
-15.7 dBmV |
31.9 dB |
DOCSIS |
| Locked |
QAM256 |
210 |
5360 Ksym/sec |
801000000 Hz |
-16.7 dBmV |
32.9 dB |
DOCSIS |
| Locked |
QAM256 |
212 |
5360 Ksym/sec |
813000000 Hz |
-16.3 dBmV |
33.1 dB |
DOCSIS |
| Locked |
QAM256 |
213 |
5360 Ksym/sec |
819000000 Hz |
-17.4 dBmV |
32.2 dB |
DOCSIS |
| Locked |
QAM256 |
214 |
5360 Ksym/sec |
825000000 Hz |
-15.5 dBmV |
32.8 dB |
DOCSIS |
| Locked |
QAM256 |
215 |
5360 Ksym/sec |
831000000 Hz |
-17.9 dBmV |
31.2 dB |
DOCSIS |
| Locked |
QAM256 |
216 |
5360 Ksym/sec |
837000000 Hz |
-16.1 dBmV |
32.0 dB |
DOCSIS |
|
|
| Upstream Bonded Channels |
| Lock Status |
Modulation |
Channel ID |
Symbol rate |
Frequency |
Power |
| Locked |
ATDMA |
3 |
5120 Ksym/sec |
28700000 Hz |
54.0 dBmV |
| Locked |
ATDMA |
4 |
5120 Ksym/sec |
35300000 Hz |
53.8 dBmV |
| Unlocked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
| Unlocked |
Unknown |
0 |
0 Ksym/sec |
0 Hz |
0.0 dBmV |
|
|
| Time |
Priority |
Description |
| Fri Aug 23 13:24:43 2013 |
Warning (5) |
Admin login authentication fail |
| Fri Aug 23 13:18:54 2013 |
Warning (5) |
MDD message timeout;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=70:ca:9b:a8:01:93;CM-QOS=1.1;CM-VER=3.0; |
| Fri Aug 23 13:17:12 2013 |
Warning (5) |
Admin login authentication fail |
| Fri Aug 23 12:48:58 2013 |
Warning (5) |
Dynamic Range Window violation |
| Fri Aug 23 12:48:51 2013 |
Notice (6) |
TLV-11 - unrecognized OID;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=70:ca:9b:a8:01:93;CM-QOS=1.1;CM-VER=3.0; |
| Fri Aug 23 12:44:04 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=70:ca:9b:a8:01:93;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:43:52 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:43:44 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=70:ca:9b:a8:01:93;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:43:20 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=70:ca:9b:a8:01:93;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:43:08 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=70:ca:9b:a8:01:93;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:55 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:53 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:45 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:43 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:40 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:38 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:36 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:34 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:32 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:30 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:28 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:24 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:19 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:15 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:13 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:07 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:42:05 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:41:54 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:41:52 2013 |
Critical (3) |
Unicast Ranging Received Abort Response - Re-initializing MAC;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=70:ca:9b:a8:01:93;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:41:40 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; |
| Fri Aug 23 12:41:35 2013 |
Critical (3) |
SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=44:94:fc:af:3b:49;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=44:94:fc:af:3b:49;CMTS-MAC=70:ca:9b:a8:01:93;CM-QOS=1.0;CM-VER=3.0; |
|
EdwardH
Valued Contributor
•
The Sync failures on the logs are likely due to the signal levels being seen as both the downstream and upstream levels are both out of spec. Though the modem's logs from our end show them ranging from normal levels through the day to spikes where they get to what you are seeing above. Are you seeing the problems with random resets more during certain times of day or in any kind of pattern?
0
0
xDrewx
New Contributor
•
Thanks for the reply, there are no set patterns or times when it fails more often, it just happens randomly often.
In a given day it can be anywhere from 5-15 times when it happens and those are just the times when someone is around or awake to deal with the modem. The new gateway modem we have is better about restarting itself after losing the signal, as in it restarts but doesnt always require a hard restart it will just find a signal again on it's own and run until the next outage.
0
0
xDrewx
New Contributor
•
Is there anything I can do to help fix the problem? Its pretty much impossible to accomplish anything as the drops are becoming more and more frequent.
0
0
ChrisL
Former Moderator
•
You could check for problems with the coax cabling such as damaged/loose cables or fittings. Short of that signal related issues almost always require a technician to come out and investigate where the signal loss is occurring.
0
0