cancel
Showing results for 
Search instead for 
Did you mean: 

Wired connection issues.

Adam021987
Joining in

Good evening all

Not sure if anyone can help? 

We have been having issues with our wired connection from our virgin hub 3. The wired connection continuously drops out for anything between 5 - 60 seconds and its driving us crazy! This is intermittent and can happen continuously throughout the day. I have no issues with wifi, only the wired connection. We are using a cat 7 ethernet cable to a windows 10 pc. I have run various tests, tried on multiple computers and have tried multiple cables.

After sitting on the phone to support various times I am getting fed up with running through all the tests as I am getting no where. Support have said that they are unable to send out an engineer as they can not find a fault at their end. I have come to the conclusion that it is a fault with my virgin hub but have been told that they can not send me out a replacement. I also add that the light on the front of the hub is constantly red which according to virgins website means the router is over heating. The router is in an open space with plenty of ventilation so has no reason to overheat. The chap from support told me on the phone that the constant red light does not mean the hub is over heating. So is the virgin website wrong then?

This is becoming rather annoying. I was trying to complete courses for work but the internet kept dropping out, even as I am typing this the internet keeps dropping out, and as for online gaming well forget it! We have just renewed our contract and was told that our internet issue would be resolved. We never would of renewed if we thought we would still be having this problem. 

I understand I could buy a wifi dongle but would prefer the higher speeds that come with a wired connection. I would like to know if there is anybody that could assist or share some information on this matter if they have had similar issues? If not its back on the phone to the support to run through their tests once again and continue to go round in circles. 😞

Thank you for taking the time to read.

 

 

1 ACCEPTED SOLUTION

Accepted Solutions

Tudor
Very Insightful Person
Very Insightful Person

First, let’s have a look at your circuit, please provide the stats from the hub.

How to get stats from a VM hub

Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode

  • Click on the “> Check router status” button
  • Click on the “Downstream” tab, copy the text and paste into your reply
  • Click on the “Upstream” tab, copy the text and paste into your reply
  • Click on the “Networking” tab, copy the text and paste into your reply.

Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

See where this Helpful Answer was posted

6 REPLIES 6

Tudor
Very Insightful Person
Very Insightful Person

First, let’s have a look at your circuit, please provide the stats from the hub.

How to get stats from a VM hub

Open a web browser and go to 192.168.0.1 router mode or 192.168.100.1 modem mode

  • Click on the “> Check router status” button
  • Click on the “Downstream” tab, copy the text and paste into your reply
  • Click on the “Upstream” tab, copy the text and paste into your reply
  • Click on the “Networking” tab, copy the text and paste into your reply.

Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

Evening Tudor, Requested below. Network Log in next post as exceeded words. Sorry its also worth me pointing out that this only started last September when we moved home and kept the equipment from our old house. 

Downstream bonded channels

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

11387500004.540256 qam1
21467500004.540256 qam2
31547500004.540256 qam3
41627500004.640256 qam4
51707500004.940256 qam5
61787500004.940256 qam6
71867500004.940256 qam7
81947500004.940256 qam8
92027500004.840256 qam9
102107500004.940256 qam10
112187500004.640256 qam11
122267500004.440256 qam12
132347500004.140256 qam13
14242750000440256 qam14
152507500004.140256 qam15
162587500004.440256 qam16
172667500004.440256 qam17
182747500004.140256 qam18
19282750000440256 qam19
202907500004.340256 qam20
212987500004.540256 qam21
223067500004.640256 qam22
233147500004.540256 qam23
243227500004.640256 qam24



Downstream bonded channels

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

1Locked40.930
2Locked40.980
3Locked40.360
4Locked40.980
5Locked40.970
6Locked40.990
7Locked40.3100
8Locked40.3140
9Locked40.9200
10Locked40.3160
11Locked40.9260
12Locked40.3390
13Locked40.3370
14Locked40.3530
15Locked40.9700
16Locked40.3910
17Locked40.9990
18Locked40.91060
19Locked40.91190
20Locked40.91570
21Locked40.31820
22Locked40.92320
23Locked40.32810
24Locked40.33350

 

Upstream bonded channels

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

15370026346.3512064 qam2
23940002946.5512064 qam4
34620028346.3512064 qam3
46030027846.3512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Network Log

Time Priority Description

08/02/2022 19:58:29noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:15:19Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:15:16criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:15:15Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:15:15criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:05:56noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 07:39:40ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2022 07:33:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/02/2022 19:39:40ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2022 16:06:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/02/2022 07:39:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/01/2022 01:43:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2022 19:39:40ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2022 15:06:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:38Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:38criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:38Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:38criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:37Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/01/2022 11:25:10criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Tudor
Very Insightful Person
Very Insightful Person

All those stats on the surface look ok, Pre RS errors a correctable and you should always expect a few, but I don’t like the increase in their number relative to the increasing frequency band. These errors are accumulative since the hub was last power cycled so could you power cycle the hub and after a few hours post another set of figures. This should show if this observed increased continues.


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

Evening Tudor

Below as requested

Downstream bonded channels

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

11387500004.540256 qam1
21467500004.640256 qam2
31547500004.640256 qam3
41627500004.840256 qam4
5170750000540256 qam5
6178750000540256 qam6
7186750000540256 qam7
8194750000540256 qam8
92027500004.940256 qam9
10210750000540256 qam10
112187500004.840256 qam11
122267500004.540256 qam12
132347500004.340256 qam13
142427500004.140256 qam14
152507500004.340256 qam15
162587500004.440256 qam16
172667500004.540256 qam17
182747500004.340256 qam18
192827500004.140256 qam19
202907500004.440256 qam20
212987500004.640256 qam21
223067500004.840256 qam22
233147500004.640256 qam23
243227500004.640256 qam24



Downstream bonded channels

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

1Locked40.330
2Locked40.950
3Locked40.360
4Locked40.950
5Locked40.950
6Locked40.3120
7Locked40.360
8Locked40.380
9Locked40.3160
10Locked40.3200
11Locked40.9170
12Locked40.3180
13Locked40.3270
14Locked40.3460
15Locked40.9440
16Locked40.9580
17Locked40.3450
18Locked40.9620
19Locked40.3760
20Locked40.91090
21Locked40.31540
22Locked40.31660
23Locked40.92150
24Locked40.92510

Upstream bonded channels

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

15370000046.3512064 qam2
23940000046.5512064 qam4
34620000046.3512064 qam3
46030000046.5512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Network Log

Time Priority Description

08/02/2022 19:58:29noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:15:19Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:15:16criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:15:15Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:15:15criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 18:05:56noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/02/2022 07:39:40ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/02/2022 07:33:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/02/2022 19:39:40ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/02/2022 16:06:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/02/2022 07:39:39ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/01/2022 01:43:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/01/2022 19:39:40ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/01/2022 15:06:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:38Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:38criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:38Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:38criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/01/2022 20:47:37Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/01/2022 11:25:10criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;