on 10-10-2022 20:58
Currently experiencing intermittent buffering issues when viewing Prime on main TV or BCC via Wifi. The Virgin Hub is in modem mode. According to Virgin media checker there are no local issues but showing faults in the logs 'No Ranging Response Received.
Question: Do I need an engineer visit to resolve?
1 | 36600000 | 42 | 5120 | 64 qam | 3 |
2 | 49600000 | 42.5 | 5120 | 64 qam | 1 |
3 | 30100072 | 41.8 | 5120 | 64 qam | 4 |
4 | 43100000 | 42 | 5120 | 64 qam | 2 |
5 | 23600000 | 41.3 | 5120 | 64 qam | 5 |
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
5 | ATDMA | 0 | 0 | 8 | 0 |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 203000000 | -2.5 | 40 | 256 qam | 9 |
2 | 211000000 | -2.7 | 40 | 256 qam | 10 |
3 | 219000000 | -2.7 | 40 | 256 qam | 11 |
4 | 227000000 | -3 | 40 | 256 qam | 12 |
5 | 235000000 | -3.2 | 40 | 256 qam | 13 |
6 | 243000000 | -3.5 | 40 | 256 qam | 14 |
7 | 251000000 | -3.5 | 40 | 256 qam | 15 |
8 | 259000000 | -3.4 | 40 | 256 qam | 16 |
9 | 267000000 | -3.2 | 40 | 256 qam | 17 |
10 | 275000000 | -3 | 40 | 256 qam | 18 |
11 | 283000000 | -2.9 | 40 | 256 qam | 19 |
12 | 291000000 | -2.7 | 40 | 256 qam | 20 |
13 | 299000000 | -2.5 | 40 | 256 qam | 21 |
14 | 307000000 | -2.4 | 40 | 256 qam | 22 |
15 | 315000000 | -2.5 | 38 | 256 qam | 23 |
16 | 323000000 | -2.7 | 40 | 256 qam | 24 |
17 | 331000000 | -2.7 | 40 | 256 qam | 25 |
18 | 339000000 | -2.5 | 40 | 256 qam | 26 |
19 | 347000000 | -2.7 | 40 | 256 qam | 27 |
20 | 355000000 | -2.7 | 40 | 256 qam | 28 |
21 | 363000000 | -2.7 | 40 | 256 qam | 29 |
22 | 371000000 | -3.2 | 40 | 256 qam | 30 |
23 | 379000000 | -3.5 | 38 | 256 qam | 31 |
24 | 387000000 | -3.9 | 40 | 256 qam | 32 |
on 10-10-2022 22:18
Network Log - T3 Errors
10/10/2022 11:33:14 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/10/2022 18:05:22 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/10/2022 21:41:23 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/10/2022 20:51:51 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/10/2022 17:22:56 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/10/2022 08:51:51 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/09/2022 15:55:8 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/09/2022 23:04:30 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/09/2022 19:17:55 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/09/2022 07:14:47 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/09/2022 07:14:45 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/09/2022 12:10:25 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/09/2022 09:24:9 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/09/2022 09:24:7 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/09/2022 17:45:1 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/09/2022 07:19:46 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/09/2022 07:19:40 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/09/2022 07:19:40 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/09/2022 07:19:40 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/09/2022 07:19:25 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 13-10-2022 09:08
Hi Crunchybits,
Thank you for your post, and welcome to the forums 🙂
I am so sorry to hear you have been having some buffering issues. I have checked and cas see you have not rebooted in a while, could you reboot and see if this helps?
Can you please let me know if is it just buffering that you are having issues with? Is it on one device? Does it buffer on a wired connection?
Zoie