Xfinity Forum Archive...
This is an archived section of the community.
Content in this area has been identified as outdated or irrelevant.
This change was done in an effort to make the forum easier to use and to keep only the most helpful and recent content active.
Post your questions in the Xfinity Community
I would like to look into this for you from here. To protect the privacy of your account, please send me a private message verifying your full name, street address including city, state, and zip code (and apartment number if one is associated), and the full account number or phone number associated with your services. To send a private message click on my name, then click private message me.
Your power levels look good, but your error log confirms your issues.
I've asked an employee to check the CMTS for real-time and historical RF signal reports from your modem. They can also check your local node/plant for any degradation or error reports. You can expect a reply in this thread.
Like some others I see on this forum, I'm having a problem where my connection will occasionally die for a few seconds to a few minutes. It seems to happen more during busy times (evenings), but has happened other times as well.
We have called support, tried everything they suggested, still have the same problems. We also had a tech come out, he couldn't find any problems with the downstream connection. He tried moving our cable to a different place in the box attached to the apartment complex, but we're still having problems.
We are using a NETGEAR CM400 modem. The upstream light on the modem will sometimes flash when we're having problems, but other times it won't (or maybe I just haven't noticed it). The router is a Buffalo WZR-600DHP, but we tried having a computer plugged directly into the modem for about 10 hours and the problem still showed up a few times, so we don't think it's the router.
Here is the downstream/upstream information:
|Downstream Bonded Channels|
|Upstream Bonded Channels|
Here are the modem error logs (the "Lost MDD Timeout" messages are new, but the ranging request retries and T3/T4 timeout messages have accompanied this problem in the past):