Regular Visitor
•
4 Messages
Intermittent "No Ranging Response received - T3 time-out"
I've been dealing with this issue since I moved and got setup in my new house. It was an annoyance but one I could deal with, but its been causing issues with my work from home connection. I will get t3 timeouts a few times a day, some only a few minutes apart but then have service without issues for hours. Sometimes the periods without interruption can last up to a week.
This is on a NETGEAR CM700 modem that was purchased new and had no issues at our previous address. We had a service call out in August to inspect the lines and he couldnt find anything wrong. I'm thinking this might be an issue outside my home and further up the infrastructure chain in our neighborhood.
Log example below.
| Mar 16 2020 01:19:21 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Mar 16 2020 01:19:21 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Mar 16 2020 08:44:02 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 08:44:46 | Critical (3) | Ranging Request Retries exhausted |
| Mar 16 2020 08:44:46 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted |
| Mar 16 2020 08:44:49 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 08:46:09 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Mar 16 2020 08:49:38 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 08:51:15 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Mar 16 2020 09:00:29 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 09:04:02 | Critical (3) | Ranging Request Retries exhausted |
| Mar 16 2020 09:04:02 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted |
| Mar 16 2020 09:04:06 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 09:06:13 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Mar 16 2020 09:56:53 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 09:57:36 | Critical (3) | Ranging Request Retries exhausted |
| Mar 16 2020 09:57:36 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted |
| Mar 16 2020 09:57:37 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 10:00:01 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Mar 16 2020 10:35:38 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 15:25:54 | Critical (3) | Ranging Request Retries exhausted |
| Mar 16 2020 15:25:54 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted |
| Mar 16 2020 15:25:54 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 15:29:49 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| Mar 16 2020 15:30:16 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 15:30:35 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Mar 16 2020 15:50:26 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 17:38:04 | Critical (3) | Ranging Request Retries exhausted |
| Mar 16 2020 17:38:04 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted |
| Mar 16 2020 17:38:14 | Critical (3) | Ranging Request Retries exhausted |
| Mar 16 2020 17:38:14 | Critical (3) | Unicast Maintenance Ranging attempted - No response - Retries exhausted |
| Mar 16 2020 17:38:16 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 17:42:14 | Critical (3) | Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out |
| Mar 16 2020 17:43:04 | Warning (5) | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1 |
| Mar 16 2020 17:55:55 | Critical (3) | No Ranging Response received - T3 time-out |
| Mar 16 2020 17:56:39 | Critical (3) | Ranging Request Retries exhausted |
EG
Expert
•
111.4K Messages
5 years ago
You need to also post the modem's signal status.
Please post the *Downstream Power Level*, the *Upstream Power Level*, and the *SNR* (Signal to Noise Ratio) numbers.
0
0
EG
Expert
•
111.4K Messages
5 years ago
The stats at that snapshot in time were fine. Is there a router / WiFi in the mix here ? If so, for a test, does a computer hardwired directly to the router device with an ethernet cable have the same problem ?
0
0
DigitalDeckard
Regular Visitor
•
4 Messages
5 years ago
I'll try to specifically grab a snapshot the next time its acting up.
Yes, I did earlier testing with the internet connection going straight from the modem to my desktop PC and we still saw the T3 upstream issues periodically.
0
0
EG
Expert
•
111.4K Messages
5 years ago
I'm not referring to the T3's at this moment. Those can happen no matter what (even if nothing) is connected to the modem. I'm talking about if you are experiencing actual connection drops / lapses, not just the log entries ?
0
0
DigitalDeckard
Regular Visitor
•
4 Messages
5 years ago
Yes, I experience interruptions in connectivity on my devices as a result of this.
If I'm streaming doing voice chats in Discord I stop being able to send packets up, but I still receive downbound packets for a few more seconds. Then I lose all connectivty and the upstream light starts flashing on the modem. Powering off and on always resolves the issue. All devices on wi-fi and wired connections are affected. Sometimes it happens once and then is fine for hours. Sometimes, I have to reset the modem multiple times within a 10 minute period.
I specifically had my desktop PC wired directly to the modem, removing the wi-fi hubs from my setup temporarliy and had the same upstream connection loss occur.
0
0
DigitalDeckard
Regular Visitor
•
4 Messages
5 years ago
0
0
EG
Expert
•
111.4K Messages
5 years ago
O/k, even though the signal stats looked o/k at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is intermittent noise ingress into the line(s) somewhere.
There are other signal stat figures that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.
I'm going to escalate your issue to the Comcast corporate employees that are available to these boards. They can check the CMTS (Cable Modem Termination System) for any real time degradation and / or error reports, see your node / cable plant and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and poll for those upstream receive signal stats.
You should get a reply here in your topic. Good luck !
0
XfinityJoeTru
Official Employee
•
7K Messages
5 years ago
Hello DigitalDeckard. We appreciate you visiting and posting on the Xfinity Forums. I can assist with troubleshooting your Internet timeouts issue. In order to have a better insight, I will have to poll the CMTS for real-time and historical RF signal reports from your modem, and check your local Node/Plant for signal degradation / errors. Please send me a private message and include your full name so I can access your equipment.
0