Menu
Reply
  • 1
  • 0
  • 0
colin6
Joining in
89 Views
Message 1 of 3
Flag for a moderator

200mbps just not working

Hi,

 

I switched on virgin 200mbps in November and since then i only have problems!!

I have been on the phone or chat online almost every week.

3 engineers came and went. The last engineer who came tried our wifi and miraculously had 197 mbps on his phone when I average 75 on ethernet with so many drop out that i can't really connect to ethernet. As soon as he left , the miracle stop and went back to my 40mpbs on wifi .. and it become worse by the day. Now to listen to a Youtube music video I have to only have youtube open otherwise i can go climb the Everest, then go climb the Himalayas and make a coffee before i can see the video...

When I tried to contact the chat online again, I was told there was an area issue of noise on the network ( despite the fact that when you check your broadband issue on the website it says 'No known issues.'.... ... ... And when you run the test they say 'It will take 10 minutes..') and that it should, hopefully, be resolved on the 6th without anymore explanation or anything else for that matter.. A quick look at the log on the router show that there is a lot of problem... And i'm losing my patience.. So is it really an area issue or is it just that Virgin can't give the speed they advertise?

 

Network Log:

1970-01-01 01:09:02.0082000900B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:09:04.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:10:14.0082000900B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:10:17.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:11:13.0082000900B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:11:52.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:12:56.0082000900B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:12:59.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:14:59.0082000900B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:15:03.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:17:31.0082000900B-INIT-RNG Failure - Retries exceeded;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 01:17:32.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-01-27 02:36:23.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-01-27 02:36:23.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-01-27 02:36:23.0084000700RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-01-27 02:36:24.0084000500SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-01-27 02:36:29.0084020200Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-01-27 17:41:15.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-01-30 01:39:17.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-01-30 03:01:47.0082000200No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Downstream:

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

1299000000340.3256 qam9
23230000004.840.3256 qam12
33150000004.440.3256 qam11
43070000003.540.3256 qam10
52910000003.240.9256 qam8
62830000003.740.3256 qam7
72750000003.940.3256 qam6
8267000000440.9256 qam5
9259000000440.9256 qam4
102510000004.140.3256 qam3
112430000004.140.3256 qam2
122350000004.540.9256 qam1

 

Cable Modem Status Item Status Comments

Acquired Downstream Channel(Hz)
299000000
Locked
Ranged Upstream Channel(Hz)
46200000
Locked
Provisioning State
Online
 

 

Thank you.

0 Kudos
Reply
  • 10.82K
  • 308
  • 632
Forum Team
Forum Team
55 Views
Message 2 of 3
Flag for a moderator

Re: 200mbps just not working

Hi colin6,

 

Welcome to the community and thanks for posting.

 

Sorry to read you are having issues with your broadband connection.

 

I've managed to locate your account and there is high traffic during peak hours which I have raised to our networks department for more investigation. Once they have replied I will let you know.

 

Will speak to you soon

Sam


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply
  • 10.82K
  • 308
  • 632
Forum Team
Forum Team
32 Views
Message 3 of 3
Flag for a moderator

Re: 200mbps just not working

Morning colin6,

 

Just letting you know more information in regards to the fault I raised.

 

The reference number is F005077383 and has a review date of 30th August. To discuss this further I have sent you a PM (purple envelope icon, right corner).

 

Apologies for the delay and inconvenience caused.

Regards

Sam


New around here? To find out more about the Community check out our Getting Started guide


0 Kudos
Reply