Hi all, I've been researching this problem for the last few weeks, and notice many people have similar issues. I have a tech come over a week from now, and want to make sure I ask all the right questions and have him/her check everything they should.
My internet has been intermittent since I moved to Brantford, ON in August 2018. Have had my Hitron replaced 3 times. So I highly doubt it's the modem. My LAN has also been up constantly, but my WAN drops a significant amount per day for about 20-30sec (as many as 15 times a day).
Here is my data. If anyone could help me prepare for when the tech comes, that would be great!!
Ranging Request Retries exhausted
|2||04/07/2019 10:37:19||82000600||critical||Unicast Maintenance Ranging attempted - No response - Retries exhausted;|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Signal noise ratio (dB)|
|Receiver||FFT type||Subcarr 0 Frequency(MHz)||PLC locked||NCP locked||MDC1 locked||PLC power(dBmv)|
|Port ID||Frequency (MHz)||Modulation||Signal strength (dBmV)||Channel ID||Bandwidth|
|1||30596000||ATDMA - 64QAM||38.500||1||6400000|
|2||38595824||ATDMA - 64QAM||43.250||3||3200000|
|3||23700000||ATDMA - 64QAM||38.500||2||6400000|
|Channel Index||State||lin Digital Att||Digital Att||BW (sc's*fft)||Report Power||Report Power1_6||FFT Size|
Running a ping test of 3600 pings to the CTMS resulted in only 2 packets lost, and to the DNS there were 0 packets lost. The minimum ping to the CTMS was 3ms with a max of 98ms and an average of 9ms, and to the DNS it was min 2ms, max 41ms, avg 8ms, but if I understand the part about timing you mentioned the firmware update means that the ping times displayed aren't necessarily accurate.
It is odd as we definitely have had issues with even light internet usage i.e. video streaming via Youtube, Netflix, Amazon Prime TV and other apps that pause and buffer frequently, so I'd assume it is an issue with our internet and not the apps, but based on the results of those tests I guess it would imply we don't have any issues in regards to the cabling. That likely means that any issues we are experiencing are due to external factors and likely related to what others have been discussing since around January if I'm understanding everything correctly. The only thing I can think of that might be affecting the tests is that I had to reset the modem the day before running them to access the DOCSIS WAN information, so the soft reset may have helped mask the issue, but I know we haven't seen packet loss in tests even when run at the same time that we are experiencing the buffering/disconnection issues.
In the meantime I'll see if I can get any information on the OFDM channel health in case it might point to some issue.
I'm seeing the same issues with the 18.104.22.168 software for the 4582U modem. Modem keeps losing connection to the internet for a few seconds repeatedly after roughly 1 week and you can't ping the modem's 192.168.100.1 or access its browser interface. After rebooting the modem it's back to normal for another week. I suspect this is a firmware issue causing a memory leak. I'm also seeing the No Ranging T3 timeout critical error in the logs.
May be a bit of a dead thread...
Check the times of the disconnects...
Are they always the same time? half hour apart by a fraction of a second? (Had this problem back in 2008, 2012... was told it was my hardware over and over.. but, with my experience supporting US customers, I knew it was a backend issue (Rogers just updated the "service" in the neighbourhood with new packages, higher fees, but, no backbone to support it) (5 months... later had 8 months of the same))
Other issues that may cause a hit: heavy load on the same power circuit (ie: deep freezer starting up... that was an issue when I was on the Bell network recently... changed power plugin location and, the connection improved)
I'm currently having similar issues.. I'm on a reseller using the Roger's connections... and, yah, it's been bad... the cabling in this neighbourhood is 48 years old. (1975)