cancel
Showing results for 
Search instead for 
Did you mean: 

Keep losing WiFi / connection to router

batesonmark
Tuning in

Hello everyone

Hoping some of you lovely people will be able to help me. We were a customer with Sky and moved to Virgin for the fibre internet and better speeds due to homeworking and kids constantly being on internet-enabled devices.

Joined Virgin in May and been having some intermittent problems with connection or WiFi, not 100% sure.

I am regularly dropping calls whilst working, Xbox is lagging constantly, Netflix is constantly buffering during episodes.

I have regularly done speed tests and they don't show any issues I have also done a BQM which is here but not sure if this really shows any issues.

Any and all suggestions are welcomed!

 

21 REPLIES 21

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

14107500002.740256 qam31
22027500004.640256 qam9
32107500004.540256 qam10
42187500004.440256 qam11
52267500004.140256 qam12
6234750000440256 qam13
7242750000440256 qam14
82507500003.940256 qam15
92587500003.540256 qam16
102667500003.440256 qam17
112747500003.240256 qam18
12282750000340256 qam19
132907500003.240256 qam20
142987500003.540256 qam21
153067500003.940256 qam22
163147500003.740256 qam23
173227500003.740256 qam24
183307500003.540256 qam25
193707500003.440256 qam26
203787500003.240256 qam27
213867500003.240256 qam28
22394750000340256 qam29
23402750000340256 qam30
244187500002.540256 qam32



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked40.337613
2Locked40.31860
3Locked40.32060
4Locked40.31710
5Locked40.33050
6Locked40.32350
7Locked40.32280
8Locked40.32450
9Locked40.32530
10Locked40.32820
11Locked40.32750
12Locked40.33070
13Locked40.328113
14Locked40.33480
15Locked40.92050
16Locked40.32690
17Locked40.32930
18Locked40.93269
19Locked40.92790
20Locked40.33400
21Locked40.32760
22Locked40.94003
23Locked40.33180
24Locked40.32670

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

15370000047.3512064 qam2
23940000047.3512064 qam4
34620000047.3512064 qam3
46030000048.8512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA00100
2ATDMA00120
3ATDMA00110
4ATDMA0090

Are there any issues showing if you call 0800 561 0061?

A period of no access could be indicative if you didn't turn the hub off!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

Time Priority Description

17/09/2021 14:00:39noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/09/2021 00:08:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/09/2021 14:00:44noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/09/2021 14:00:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/09/2021 10:20:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2021 02:00:44noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2021 02:00:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/09/2021 19:19:21criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/09/2021 14:00:44noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/09/2021 14:00:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/09/2021 11:59:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/09/2021 02:00:44noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/09/2021 02:00:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2021 14:09:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2021 14:00:44noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2021 14:00:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/09/2021 10:21:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/08/2021 20:07:46noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/08/2021 02:00:44noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt057-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/08/2021 02:00:44ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Just called and there are no issues according to the automated messages.

Yep definitely didn't turn the hub off so can't explain it.

OK - a Smattering of PostRS errors and rather too many T3 Timeouts for my liking!

Saying that though - the log isn't showing anything of major concern - And the t3s are cumulative so could be historical



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

I have no idea what any of that means.

From a users perspective, calls are dropping out constantly. Quality of voice and video is dire when doing video calls. Laptop says connected has disconnected although I am still connected to the router.

jbrennand
Very Insightful Person
Very Insightful Person
Start from a blank sheet.
___________________

Switch the Hub off and unplug it from the mains supply for five minutes. Whilst it's off, do a quick check that all of your coax cable connections are in nice and "finger" tight - at the Hub and wall box and also at any connectors etc. Ensure there are no “unterminated cable loose ends. Disconnect all the connections and reconnect to be sure. Also check that the internal wiring is ok with no kinking or chaffing, check that all looks good with the outside cabling and wall box (no “staples, etc.,) piercing the cables.. Then switch the Hub back on and leave ~5 minutes

When all done, check back in the settings and ensure that the RS error counts and T3’s have all reset to 0. Then check every hour or so to see if they start reappearing - they shouldn't. If they do (particularly the postRS ones) you have a problem (noise) that only a Tech visit will sort.

--------------------
John
--------------------

I do not work for VM. My services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired, 2 on WiFi) Hub5 in modem mode with Apple Airport Extreme Router +2 Airport Express's & TP-Link Archer C64 WAP. On Volt 350Mbps, Talk Anytime Phone, x2 Mobile SIM only iPhones.

The T3 timeout happens when the hub fails to make a connection to the CMTS to 'range' or get the best performing channels. If this happens it can lead to all downstream channels being 'dropped' to get a whole new set - This manifests as a disconnection and can be either a 'blip' or a full 5 minute renegotiation.

The PostRS errors are packets of data that are corrupt and cannot be corrected by the Reed-Solomon (hence RS) method.

Due to the nature of DOCSIS networks (good old analogue RF frequencies) you will always get corrupt network packets and hence the need for the RS method to correct them! - SOmetimes it just can't correct it and you get PostRS errors. Too many of these in too short a space of time leads to the same drops and slowdowns.

Basically - your line has probably got interference on it like a radio that isn't quite tuned in so it gets noise and if you can't hear critical information over the noise - you got problems!

Hope this helps - it is my *really* basic understanding of DOCSIS cable networks. Others have much, much more knowledge!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

Hi batesonmark,

 

We just wanted to see how things are going with your disconnection issues.

 

We can see that you have already been given some amazing advice from our community member @lotharmat already. Has this advice resolved the issues you're currently experiencing?

 

We have done a quick check from our end for you this morning and there are no issue showing which would be causing these regular dropouts. All power levels are within specification, there are no SNR issue or area faults that are affecting you either which is good news.

 

Please let us know if you still need further assistance.

 

Kind regards Jodi.