Forum Discussion
I have been experiencing the same issue, went and both two new modems and routers all doing the same thing so issue isn’t on my end. Did anyone find a solution?
How often are you seeing this message? If you're seeing it a few times a week it's harmless. Every cable network is going to get a momentary glitch every now and then. If you're seeing it several times per hour you probably need Cox to check for intermittent noise on the line.
- Tradev5 years agoNew Contributor
As it as often as every 30 mins and experience packet loss at all times or lag spikes. At this point it’s pretty much unusable especially at night time.
- Peterockinit5 years agoNew Contributor III
I cant even tell you that because I keep losing access to 192.168.100.1
only way i get it back is by power cycling and that clears my logs
I got a new modem, mb8600 - upstream power levels are 43-44 now as recommended by the latest tech visit. still getting dynamic range window violations but i do not know how often. I can only see the couple I get within a few hours and then I am unable to reach my modem UI ip address..
this is a mess. i really wish i could get an answer and a fix
- Peterockinit5 years agoNew Contributor III
Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected 1 Locked QAM256 9 831.0 -1.3 39.4 0 0 2 Locked QAM256 1 783.0 0.1 39.7 0 0 3 Locked QAM256 2 789.0 0.0 39.5 0 0 4 Locked QAM256 3 795.0 -0.2 39.7 0 0 5 Locked QAM256 4 801.0 -0.4 39.6 0 0 6 Locked QAM256 5 807.0 -0.3 39.8 0 0 7 Locked QAM256 6 813.0 -0.6 39.5 0 0 8 Locked QAM256 7 819.0 -0.6 39.8 0 0 9 Locked QAM256 8 825.0 -1.2 39.4 0 0 10 Locked QAM256 10 837.0 -1.4 39.3 0 0 11 Locked QAM256 11 843.0 -1.3 39.5 0 0 12 Locked QAM256 12 849.0 -1.3 39.3 0 0 13 Locked QAM256 13 855.0 -1.6 39.2 0 0 14 Locked QAM256 14 861.0 -1.9 39.0 0 0 15 Locked QAM256 15 867.0 -1.6 39.1 0 0 16 Locked QAM256 16 873.0 -1.3 39.3 0 0 17 Locked QAM256 33 357.0 2.5 39.6 0 0 18 Locked QAM256 34 363.0 2.3 39.8 0 0 19 Locked QAM256 35 369.0 2.3 39.9 0 0 20 Locked QAM256 36 375.0 2.3 39.9 0 0 21 Locked QAM256 37 381.0 2.4 39.6 0 0 22 Locked QAM256 38 387.0 2.0 39.9 0 0 23 Locked QAM256 39 393.0 0.5 39.7 0 0 24 Locked QAM256 40 399.0 1.5 39.8 0 0 25 Locked QAM256 41 405.0 1.9 40.0 0 0 26 Locked QAM256 42 411.0 1.9 40.0 0 0 27 Locked QAM256 43 417.0 1.8 39.9 0 0 28 Locked QAM256 44 423.0 1.9 39.9 0 0 29 Locked QAM256 45 429.0 2.0 39.9 0 0 30 Locked QAM256 46 435.0 2.0 40.1 0 0 31 Locked QAM256 47 441.0 2.0 40.0 0 0 32 Locked QAM256 48 447.0 2.1 40.2 0 0 33 Locked OFDM PLC 159 300.0 6.1 16.5 3759992 0 Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV) 1 Locked SC-QAM 1 5120 36.3 44.0 2 Locked SC-QAM 2 5120 29.9 44.0 3 Locked SC-QAM 3 5120 23.5 43.0 4 Locked SC-QAM 4 5120 16.9 42.0 - Dave95 years agoContributor III
I've heard that some modems have bugs that cause the web UI to stop working after a while, or maybe after many accesses. Try rebooting the modem and then don't check the UI for a day. See if you can still access it the next day.
I'm starting to think that a perfectly clean cable connection just doesn't exist. I've been working with Cox to troubleshoot multiple issues (always ended up being their equipment and never mine). Just when I thought I had a perfect connection, I've started getting ingress between 902 and 928 MHz which causes hundreds of thousands of uncorrectables on 5 channels. This manifests as glitches in audio and video when on calls. Once I can positively identify the time window that it occurs I'll have a tech come out during that time. It only happens for about 6 hours a day. But once that's fixed, all it takes is one neighbor to hook up some old coax to their TV and we're right back to square one.