Visitor
•
6 Messages
MDD message timeout
As far as I can tell same issue as here:
First call, Comcast restarted the modem, verified they were able to connect and called it a day.
Second call, got lucky and modem lost signal while on call. Tech verified bad signals and scheduled a tech go onsite. Tech shows up, sees Arris SB6141 and says it's not supported and leaves, even though it still shows up on Comcast's own supported modems page SMH.
*replaced SB6141 with SB8200 and installed new router...same issues SMH again
Third call, they said they'd send a tech to come out and check signals, but my concern now is that this may be due to a loose/cut cable upstream of the modem/building. If the signal check at the time the tech is on-site is good, what recourse do I have to hold Comcast accountable to stabilize the connection?
Considering it's a brand new (latest supported model) modem and the modem is showing the following when we lose internet for a minute:
02/19/2022 10:20 74010100 6 "CM-STATUS message sent. Event Type Code: 4; Chan ID: 4 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=***;CMTS-MAC=***;CM-QOS=1.1;CM-VER=3.1;"
02/19/2022 10:19 84020300 5 "MDD message timeout;CM-MAC=***;CMTS-MAC=***;CM-QOS=1.1;CM-VER=3.1;"n
I don't see how it could be anything OTHER than a bad line or upstream node hardware (we've had a lot of snow/blizzards and freezing temps here recently).
user_syo254
Visitor
•
6 Messages
3 years ago
0
0
user_syo254
Visitor
•
6 Messages
3 years ago
Looks like it WAS an upstream issue. Can’t stand Comcast. You can show them all the documentation in the world proving it, but if you’re the first person to notice an issue with the node you’re on, you’re stuck with the issue till others report it SMH.
This is especially problematic if the issue is very sporadic and only happens occasionally. Most people are ok with a 99% daily uptime. Too bad for any of us that have a backup that runs for more then a day and the blip causes it to fail.
0
0
user_syo254
Visitor
•
6 Messages
3 years ago
Looks like it WAS an upstream issue. Can’t stand Comcast. You can show them all the documentation in the world proving it, but if you’re the first person to notice an issue with the node you’re on, you’re stuck with the issue till others report it SMH.
This is especially problematic if the issue is very sporadic and only happens occasionally. Most people are ok with a 99% daily uptime. Too bad for any of us that have a backup that runs for more then a day and the blip causes it to fail.
0
0