- #1
NTL2009
- 597
- 381
Have had very reliable internet in the ~ 2.5 years we have been in this home, using my purchased Modem/router. A few months back, we started getting intermittent drop outs (~ 10/day?), lasting a couple minutes each. Mostly would come back on their own, sometimes I'd have to reboot the modem, sometimes the modem seemed to reboot on its own (or did Comcast/Xfinity trigger this?).
At this same time, on the Xfinity status page, they had a string of announcements about scheduled maintenance to correct noted network problems, so I thought maybe this was all on their end (and they did find some bad cables/connections along the way, and my signal levels improved from marginal to good), but the problem persisted. After unproductive runarounds with Xfinity, and a tech deciding we should have our buried cable replaced ( ~ 15 YO if original to the home- but it made no difference, as I expected, as my signal levels and S/N ratio were at a good level before/after). I have some scripts running to check the connection every minute and log any drops, so I've got a good record and measurment (Ethernet connection to modem/router, to eliminate WiFi as the culprit) . There's more to this, but to cut to the chase...
I got frustrated with the Xfinity run-around, and decided to rent their modem @ $15/mo to avoid some finger pointing. Well, to my surprise, the rented modem worked perfectly. I let it go a week (my old one was perfect for 3 days once over this trouble period, so I still can't be sure which end is having the problem). Then I wondered whether simply doing a factory reset, and the re-registering that old modem with Xfinity would magically clear up something. So I did that, and my old modem seems to be working near-perfectly for four days now. I did have one reboot and later, one error log "Started Unicast Maintenance Ranging - No Response received - T3 time-out;", but zero drop outs (other then when the reboot occurred). The 'corrected errors' are ~ 230 total now, after two days of uptime, and zero uncorrected, I thinks those numbers are not considered a problem?
Does it make any sense that a factory reset and re-register could clear up intermittent drops? I rebooted that old modem many, many times previously. FYI, the 'old' modem is on their 'approved' list, a Motorola MG7550 DOCSIS 3.0, which might be newer than the one the provided (an ARRIS TG1682G DOCSIS 3.0).
Hopefully, it keeps working and I'll return their modem, but I'm curious if there is a any sound technical reason the reset/re-register would help (over and above a regular reboot)?
At this same time, on the Xfinity status page, they had a string of announcements about scheduled maintenance to correct noted network problems, so I thought maybe this was all on their end (and they did find some bad cables/connections along the way, and my signal levels improved from marginal to good), but the problem persisted. After unproductive runarounds with Xfinity, and a tech deciding we should have our buried cable replaced ( ~ 15 YO if original to the home- but it made no difference, as I expected, as my signal levels and S/N ratio were at a good level before/after). I have some scripts running to check the connection every minute and log any drops, so I've got a good record and measurment (Ethernet connection to modem/router, to eliminate WiFi as the culprit) . There's more to this, but to cut to the chase...
I got frustrated with the Xfinity run-around, and decided to rent their modem @ $15/mo to avoid some finger pointing. Well, to my surprise, the rented modem worked perfectly. I let it go a week (my old one was perfect for 3 days once over this trouble period, so I still can't be sure which end is having the problem). Then I wondered whether simply doing a factory reset, and the re-registering that old modem with Xfinity would magically clear up something. So I did that, and my old modem seems to be working near-perfectly for four days now. I did have one reboot and later, one error log "Started Unicast Maintenance Ranging - No Response received - T3 time-out;", but zero drop outs (other then when the reboot occurred). The 'corrected errors' are ~ 230 total now, after two days of uptime, and zero uncorrected, I thinks those numbers are not considered a problem?
Does it make any sense that a factory reset and re-register could clear up intermittent drops? I rebooted that old modem many, many times previously. FYI, the 'old' modem is on their 'approved' list, a Motorola MG7550 DOCSIS 3.0, which might be newer than the one the provided (an ARRIS TG1682G DOCSIS 3.0).
Hopefully, it keeps working and I'll return their modem, but I'm curious if there is a any sound technical reason the reset/re-register would help (over and above a regular reboot)?