Virgin Media Virgin Media Community

RedDragonTaff · ‎27-09-2020

Hi,

I am at the end of my tether. Since the 14 Sept 20 the VM network has really gone bad. Even today this is still ongoing. All other levels of communication Facebook, Customer Support 150/151 has fallen on deaf ears.

So tonight here's what I see on the Hub:

Network Log:
27/09/2020 21:35:13 GMT 27/09/2020 21:35:13 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:34:59 GMT 27/09/2020 21:34:59 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:34:37 GMT 27/09/2020 21:34:37 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:34:19 GMT 27/09/2020 21:34:19 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:34:00 GMT 27/09/2020 21:34:00 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:33:39 GMT 27/09/2020 21:33:39 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:33:20 GMT 27/09/2020 21:33:20 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:33:00 GMT 27/09/2020 21:33:00 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:32:40 GMT 27/09/2020 21:32:40 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:32:20 GMT 27/09/2020 21:32:20 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:32:01 GMT 27/09/2020 21:32:01 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:31:44 GMT 27/09/2020 21:31:44 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:31:21 GMT 27/09/2020 21:31:21 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:31:13 GMT 27/09/2020 21:31:13 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:31:03 GMT 27/09/2020 21:31:03 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:30:27 GMT 27/09/2020 21:30:27 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:30:18 GMT 27/09/2020 21:30:18 GMT Error (4) 68010302 DHCP WAN IP - removed
27/09/2020 21:30:04 GMT 27/09/2020 21:30:04 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:29:45 GMT 27/09/2020 21:29:45 GMT Warning (5) 84020200 Lost MDD Timeout
27/09/2020 21:29:38 GMT 27/09/2020 21:29:38 GMT Warning (5) 84020200 Lost MDD Timeout

Downstream:
DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) 139000000 147000000 155000000 163000000 N/A 179000000 187000000 195000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Locked Locked Locked Unlocked Locked Locked Locked
Channel ID 1 2 3 4 N/A 6 7 8
Modulation 256QAM 256QAM 256QAM 256QAM Unknown 256QAM 256QAM 256QAM
Symbol Rate (Msym/sec) 6.952000 6.952000 6.952000 6.952000 N/A 6.952000 6.952000 6.952000
Interleave Depth I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17 N/A I=12
J=17 I=12
J=17 I=12
J=17
Power Level (dBmV) -2.30 -2.44 -2.64 -2.56 N/A -2.69 -2.95 -2.87
RxMER (dB) 36.84 37.09 36.84 36.84 N/A 38.26 38.26 36.39
Pre RS Errors 327 319 297 276 N/A 295 302 966
Post RS Errors 289 287 297 275 N/A 295 302 966

Upstream:
US-1 US-2 US-3 US-4
Channel Type 2.0 2.0 2.0 2.0
Channel ID 1 4 2 3
Frequency (Hz) 60300000 39400000 53700000 46200000
Ranging Status Success Success Success Success
Modulation 64QAM 64QAM 64QAM 64QAM
Symbol Rate (Sym/sec) 5120000 5120000 5120000 5120000
Mini-Slot Size 2 2 2 2
Power Level (dBmV) 46.50 45.50 46.00 45.75
T1 Timeouts 0 0 0 0
T2 Timeouts 0 0 0 0
T3 Timeouts 1 0 0 0
T4 Timeouts 0 0 0 0

Upstream Burst:
Req
(1) Init Maint
(3) Per Maint
(4) Adv Short
(9) Adv Long
(10) Adv UGS
(11)
Modulation Type 16QAM QPSK 16QAM 64QAM 64QAM 16QAM
Differential Encoding OFF OFF OFF OFF OFF OFF
Preamble Length 56 640 384 104 104 104
Preamble Value Offset 652 0 0 716 716 716
FEC Error Correction (T) 0 5 5 10 16 5
FEC Codeword Information Bytes (K) 16 34 34 81 223 86
Maximum Burst Size 0 0 0 3 255 255
Guard Time Size 8 48 48 8 8 8
Last Codeword Length Fixed Fixed Fixed Shortened Shortened Shortened
Scrambler On/Off ON ON ON ON ON ON

Attached is the BQM graphs daily since 14th Sept. Can someone initiate an investigation please?

Thanks

AL

[MOD EDIT: Personal and private information has been removed from this post. Please do not post personal or private information in your public posts. Please review the Forum Guidelines]

Andrew-G · ‎22-06-2021

It would seem evident to me that (from this and a small number of intractable "field" problems) that VM do not have any effective fault finding process, are overly reliant upon some very crude diagnostics, and have little or no access to the tools necessary to maintain and troubleshoot on an RF network. Everything is divided into silos (eg between customer services, the field team, the network team), each sub-element is cheese pared down with the lowest cost labour available for each step, and there are procedures in place that are DESIGNED to stop employees taking ownership and sorting out problems that don't fit into the basic scripts and diagnostics. Usually this does work for simple problems, but anything out of the ordinary and it fails spectacularly.

So @RedDragonTaff given what's gone on, is it time to cut your losses and leave? On the one hand it looks to be that this latest bout of problems has only been going on for two weeks(?), on the other it has been a depressing read where the company have flunked each of multiple opportunities to diagnose and fix what ought to be an easily found and resolved problem.

If you're in a fixed term contract then you'll need to formally invoke VM's complaint policy and in the complaint give them 30 days to fix the problem or release you from contract without penalty. This might even be enough to get the field team to allocate the resources to find and fix, but looking at other comments in the forum, VM's complaints process appears to be an exercise in fobbing off complaints by the same sort of poorly trained offshore staff that do first line "support". But you'll need to go through that stage if it becomes necessary to escalate the complaint to arbitration by CISAS (and even if they do fix this, I'd go down that route to seek compensation).

See where this Helpful Answer was posted

David_Bn · ‎22-06-2021

Thanks for coming back to us RedDragonTaff, and I'm terribly sorry to see we've been experiencing long term issues with the services.

I would be happy to contact the area field manager to see if we can arrange for a senior engineer to come to your property to see if this can be resolved for you.

Alternatively, if you're unhappy to do this, I can seek to arrange for your account to be cancelled, without penalty as we have been seemingly unable to resolve this fault, after the arrival of multiple engineers

Come back to me and I'll start working on it for you

Kindest regards,

David_Bn

See where this Helpful Answer was posted

MikeRobbo · ‎27-09-2020

Have you checked the 'Check Service Status' at the top of the page ?

If nothing is showing try phoning 0800 561 0061, this will tell you of more local issues that may be affecting the area. Be aware that it isn't a manned line.

*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.

RedDragonTaff · ‎27-09-2020

Thanks Mike, both service page and this freephone number indicates no problem. However for the past two weeks the broadband has received numerous days of claimed faults and maintenance.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/b191b812231b67a5791822c64156e349e3...

RedDragonTaff · ‎28-09-2020

Today there was a planned maintenance in the morning:

Later this all started working at about 13:09 with the logs showing:

Downstream
DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) 139000000 147000000 155000000 163000000 171000000 179000000 187000000 195000000
Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Locked Locked Locked Locked Locked Locked Locked
Channel ID 1 2 3 4 5 6 7 8
Modulation 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM 256QAM
Symbol Rate (Msym/sec) 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000 6.952000
Interleave Depth I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17
Power Level (dBmV) 3.02 2.93 2.79 2.77 2.57 2.50 2.28 2.43
RxMER (dB) 37.36 37.94 37.94 37.94 38.26 38.26 38.26 38.26
Pre RS Errors 2463 1296 1375 1394 1276 2064 2532 2998
Post RS Errors 298 304 273 296 302 291 302 952

Upstream
US-1 US-2 US-3 US-4
Channel Type 2.0 2.0 2.0 2.0
Channel ID 1 2 3 4
Frequency (Hz) 60300000 53700000 46200000 39400000
Ranging Status Success Success Success Success
Modulation 64QAM 64QAM 64QAM 64QAM
Symbol Rate (Sym/sec) 5120000 5120000 5120000 5120000
Mini-Slot Size 2 2 2 2
Power Level (dBmV) 46.50 46.25 46.00 45.75
T1 Timeouts 0 0 0 0
T2 Timeouts 0 0 0 0
T3 Timeouts 0 0 0 0
T4 Timeouts 0 0 0 0

Upstream Burst
Req
(1) Init Maint
(3) Per Maint
(4) Adv Short
(9) Adv Long
(10) Adv UGS
(11)
Modulation Type 16QAM QPSK 16QAM 64QAM 64QAM 16QAM
Differential Encoding OFF OFF OFF OFF OFF OFF
Preamble Length 56 640 384 104 104 104
Preamble Value Offset 652 0 0 716 716 716
FEC Error Correction (T) 0 5 5 10 16 5
FEC Codeword Information Bytes (K) 16 34 34 81 223 86
Maximum Burst Size 0 0 0 3 255 255
Guard Time Size 8 48 48 8 8 8
Last Codeword Length Fixed Fixed Fixed Shortened Shortened Shortened
Scrambler On/Off ON ON ON ON ON ON

General Configuration
Network Access Allowed
Maximum Number of CPEs 1
Baseline Privacy Enabled
DOCSIS Mode EuroDOCSIS 3.0
Config File
Primary Downstream Service Flow
SFID 28550
Max Traffic Rate 230000061 bps
Max Traffic Burst 42600 bytes
Min Traffic Rate 0 bps
Primary Upstream Service Flow
SFID 28549
Max Traffic Rate 22000061 bps
Max Traffic Burst 42600 bytes
Min Traffic Rate 0 bps
Max Concatenated Burst 42600 bytes
Scheduling Type Best Effort

RedDragonTaff · ‎28-09-2020

I got an new WAN IP and have been tracking this via BQM and it was running okay from 13:00 to about 15:45 where it lost sync.

Logs now show:

Network Log
First Time Last Time Priority Error Number Description
28/09/2020 15:30:39 GMT 28/09/2020 15:30:39 GMT Warning (5) 84020200 Lost MDD Timeout
28/09/2020 15:30:36 GMT 28/09/2020 15:30:36 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
28/09/2020 15:30:12 GMT 28/09/2020 15:30:12 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
28/09/2020 15:29:53 GMT 28/09/2020 15:29:53 GMT Warning (5) 84020200 Lost MDD Timeout
28/09/2020 15:29:43 GMT 28/09/2020 15:29:43 GMT Critical (3) 68000900 TFTP file complete - but missing mandatory TLV
28/09/2020 15:29:27 GMT 28/09/2020 15:29:27 GMT Error (4) 68000407 TOD established
28/09/2020 15:29:21 GMT 28/09/2020 15:29:21 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
28/09/2020 15:29:20 GMT 28/09/2020 15:29:20 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
28/09/2020 15:29:11 GMT 28/09/2020 15:29:11 GMT Notice (6) 84000510 Downstream Locked Successfully
28/09/2020 15:28:55 GMT 28/09/2020 15:28:55 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
28/09/2020 15:28:51 GMT 28/09/2020 15:28:51 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
28/09/2020 15:28:51 GMT 28/09/2020 15:28:51 GMT Critical (3) 82000200 No Ranging Response received - T3 time-out
28/09/2020 15:28:47 GMT 28/09/2020 15:28:47 GMT Notice (6) 84000510 Downstream Locked Successfully
28/09/2020 15:28:28 GMT 28/09/2020 15:28:28 GMT Notice (6) 84000510 Downstream Locked Successfully
28/09/2020 15:28:27 GMT 28/09/2020 15:28:27 GMT Warning (5) 84020300 MDD message timeout
28/09/2020 15:28:27 GMT 28/09/2020 15:28:27 GMT Warning (5) 84020200 Lost MDD Timeout
28/09/2020 15:28:04 GMT 28/09/2020 15:28:04 GMT Notice (6) 84000510 Downstream Locked Successfully
28/09/2020 15:28:03 GMT 28/09/2020 15:28:03 GMT Warning (5) 84020300 MDD message timeout
28/09/2020 15:28:03 GMT 28/09/2020 15:28:03 GMT Warning (5) 84020200 Lost MDD Timeout
28/09/2020 15:27:40 GMT 28/09/2020 15:27:40 GMT Notice (6) 84000510 Downstream Locked Successfully

Downstream
DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) 331000000 N/A N/A N/A N/A N/A N/A N/A
Lock Status(QAM Lock/FEC Sync/MPEG Lock) Locked Unlocked Unlocked Unlocked Unlocked Unlocked Unlocked Unlocked
Channel ID 25 N/A N/A N/A N/A N/A N/A N/A
Modulation 256QAM Unknown Unknown Unknown Unknown Unknown Unknown Unknown
Symbol Rate (Msym/sec) 6.952000 N/A N/A N/A N/A N/A N/A N/A
Interleave Depth I=12
J=17 N/A N/A N/A N/A N/A N/A N/A
Power Level (dBmV) -12.91 N/A N/A N/A N/A N/A N/A N/A
RxMER (dB) 27.22 N/A N/A N/A N/A N/A N/A N/A
Pre RS Errors 3625188 N/A N/A N/A N/A N/A N/A N/A
Post RS Errors 291068 N/A N/A N/A N/A N/A N/A N/A

Upstream
US-1 US-2 US-3 US-4
Channel Type 2.0 N/A N/A N/A
Channel ID 4 N/A N/A N/A
Frequency (Hz) 39400000 N/A N/A N/A
Ranging Status Success N/A N/A N/A
Modulation 64QAM N/A N/A N/A
Symbol Rate (Sym/sec) 5120000 N/A N/A N/A
Mini-Slot Size 2 N/A N/A N/A
Power Level (dBmV) 45.75 N/A N/A N/A
T1 Timeouts 3 3 3 3
T2 Timeouts 0 0 0 0
T3 Timeouts 4 0 0 0
T4 Timeouts 0 0 0 0

Upstream Burst
Req
(1) Init Maint
(3) Per Maint
(4) Adv Short
(9) Adv Long
(10) Adv UGS
(11)
Modulation Type 16QAM QPSK 16QAM 64QAM 64QAM 16QAM
Differential Encoding OFF OFF OFF OFF OFF OFF
Preamble Length 56 640 384 104 104 104
Preamble Value Offset 652 0 0 716 716 716
FEC Error Correction (T) 0 5 5 10 16 5
FEC Codeword Information Bytes (K) 16 34 34 81 223 86
Maximum Burst Size 0 0 0 3 255 255
Guard Time Size 8 48 48 8 8 8
Last Codeword Length Fixed Fixed Fixed Shortened Shortened Shortened
Scrambler On/Off ON ON ON ON ON ON

General Configuration
Network Access Denied
Maximum Number of CPEs
Baseline Privacy
DOCSIS Mode EuroDOCSIS 3.0
Config File
Primary Downstream Service Flow
SFID
Max Traffic Rate 0 bps
Max Traffic Burst 0 bytes
Min Traffic Rate 0 bps
Primary Upstream Service Flow
SFID
Max Traffic Rate 0 bps
Max Traffic Burst 0 bytes
Min Traffic Rate 0 bps
Max Concatenated Burst 0 bytes
Scheduling Type

Information
Cable Modem
Serial Number 3PM347WF02D4B
Boot Code Version PSPU-Boot 1.0.20.1391
Software Version V2.01.15
Hardware Version 1.03
CA Key Installed

RedDragonTaff · ‎28-09-2020

Now I can see there's another problem:

All these posts today are via my mobile broadband connection incase anyone wondered.

RedDragonTaff · ‎08-06-2021

Now on a SH3. Connection started off fairly stable but in recent weeks, but to packet loss. Saw others having problems and saw a great post by a non VM techie that suggested power off for 5 mins and monitoring the connection errors.

Do I need to worry about Pre-errors or Post-errors or both? Can someone explain what they mean?

Logs soon after power on are:

Downstream bonded channels

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

1	203000000	3.9	40	256 qam	9
2	139000000	4.1	40	256 qam	1
3	147000000	4.4	40	256 qam	2
4	155000000	4.1	40	256 qam	3
5	163000000	4.1	40	256 qam	4
6	171000000	4.1	40	256 qam	5
7	179000000	4.1	40	256 qam	6
8	187000000	4	40	256 qam	7
9	195000000	4	40	256 qam	8
10	211000000	3.7	40	256 qam	10
11	219000000	3.5	40	256 qam	11
12	227000000	3.4	40	256 qam	12
13	235000000	3.2	40	256 qam	13
14	243000000	3	40	256 qam	14
15	251000000	3.2	40	256 qam	15
16	259000000	3	40	256 qam	16
17	267000000	2.9	40	256 qam	17
18	275000000	2.7	40	256 qam	18
19	283000000	3	40	256 qam	19
20	291000000	3.7	40	256 qam	20
21	299000000	4	40	256 qam	21
22	307000000	4.1	40	256 qam	22
23	315000000	4.3	40	256 qam	23
24	323000000	4.4	40	256 qam	24

Downstream bonded channels

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

1	Locked	40.3	3
2	Locked	40.3	5
3	Locked	40.3	4
4	Locked	40.9	6
5	Locked	40.3	5
6	Locked	40.3	0
7	Locked	40.9	0
8	Locked	40.3	5
9	Locked	40.9	5
10	Locked	40.3	5
11	Locked	40.9	5
12	Locked	40.9	3
13	Locked	40.3	5
14	Locked	40.3	0
15	Locked	40.3	4
16	Locked	40.3	0
17	Locked	40.3	0
18	Locked	40.3	0
19	Locked	40.3	5
20	Locked	40.9	4
21	Locked	40.3	20
22	Locked	40.9	6
23	Locked	40.9	4
24	Locked	40.3	5

RedDragonTaff · ‎08-06-2021

Network Log

Time Priority Description

08/06/2021 10:18:45	notice	LAN login Success;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
08/06/2021 10:11:6	Warning!	RCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
08/06/2021 10:11:6	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
08/06/2021 10:11:5	Warning!	RCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
08/06/2021 09:37:13	notice	LAN login Success;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
06/06/2021 10:57:11	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
06/06/2021 08:59:18	notice	LAN login Success;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
03/06/2021 17:45:23	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
03/06/2021 17:40:7	Warning!	RCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 23:19:48	critical	No Ranging Response received - T3 time-out;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 12:11:41	notice	LAN login Success;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:42:25	Warning!	RCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:42:25	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:42:24	Warning!	RCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:42:24	critical	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:42:22	Warning!	RCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:42:22	Warning!	Lost MDD Timeout;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:42:22	Warning!	RCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:42:22	Warning!	Lost MDD Timeout;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;
01/06/2021 11:42:22	Warning!	RCS Partial Service;CM-MAC=:::::;CMTS-MAC=:::::;CM-QOS=1.1;CM-VER=3.0;

Heres the BQM for the past 24Hours:

RedDragonTaff · ‎08-06-2021

Okay I think I have answered my own question wrt what's important about the Pre/Post RS errors. Someone on a Reddit post responded with:

"Pre errors will clear back to 0 when you reboot the hub. The hub can fix the pre errors but cannot fix post errors. If you have post errors there’s an issues somewhere. Also power levels shouldn’t fluctuate that much. Only about 0.5db either way"

I'll monitor the Post RS errors to see if there is a bad channel

Laurie_C · ‎08-06-2021

Hi RedDragonTaff,

Thanks for getting in touch, and a very warm welcome back to the Community Forum.

I'd be more than happy to look into your connection, I'll just need to confirm a few details with you via Private Message. Please look out for a purple envelope in the top right corner of your screen.

Kind regards,

Laurie

Laurie_C
Forum Team

Virgin Media Virgin Media Community

Virgin Media Virgin Media Community

CF23 Internet stability and packet loss