Menu
Reply
  • 5
  • 0
  • 0
bagginz
Joining in
284 Views
Message 1 of 7
Flag for a moderator

Repaired but slow

Hi, just had a engineer come to my house today to fix my (access denied) problem he put a 2nd splitter on my line and replaced a cable, my internet is now back on but not without some problems.

my speed is now 180mbps i pay for vivid 350 and was getting 360mbps even at peak also my wifi is now intermittent and keeps restarting every hour or so, i have contacted tech who made me use modem only mode and start my pc in safe mode and nothing worked.

they then redirected me to a paid sevice to help claiming it must be on my end but nothing has changed since my internet was fixed and im pretty tech savvy so can confidently say its nothing my end

also the speed is through wired connection not wifi

any suggestions ive tried everything

Thanks Aaron

0 Kudos
Reply
  • 8.57K
  • 877
  • 1.33K
jbrennand
Alessandro Volta
232 Views
Message 2 of 7
Flag for a moderator

Re: Repaired but slow

This may not be of help but...
Check all your coax connections are in nice and "finger" tight at the Hub and wall box and at any splitters/attenuators/etc and that the internal wiring is ok with no kinking or chaffing (rabbit chews!). Also check that all looks good with the outside cabling and wall box.
If that’s all good.... post up your Hub/network connection details and someone will check to see if there is a problem there. In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) and hit return. On the first page up [there should be no need to login if you have done so before] click on the “router status” icon at top right or the text at bottom middle - of first page up (depending on which hub you have) and then copy/paste 3 sets of data onto here - the downstream, upstream, & network logs. Don't worry too much about the formatting it can be easily read,& don’t include personal data or MAC addresses - blank them out.

--------------------
Services: HD TV on VIP (+ Sky Sports & Movies & BT sport), x3 V6 boxes (1 wired 2 WiFi,) SH2 in modem mode with Airport Extreme Router. On VIVID200, Talk Anytime Phone, x2 Mobile SIM only iPhones.
0 Kudos
Reply
  • 5
  • 0
  • 0
bagginz
Joining in
191 Views
Message 3 of 7
Flag for a moderator

Re: Repaired but slow

Downstream bonded channels

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

12990000002.538256 qam21
23230000002.238256 qam24
33150000002.240256 qam23
43070000002.238256 qam22
52910000001.938256 qam20
62830000002.738256 qam19
72750000002.538256 qam18
82670000002.738256 qam17
92590000002.938256 qam16
102510000002.538256 qam15
11243000000338256 qam14
122350000002.540256 qam13
132270000002.738256 qam12
142190000002.738256 qam11
152110000002.438256 qam10
162030000002.240256 qam9
171950000002.538256 qam8
181870000003.440256 qam7
191790000003.440256 qam6
201710000003.540256 qam5
211630000003.238256 qam4
221550000003.238256 qam3
231470000003.238256 qam2
241390000003.238256 qam1



Downstream bonded channels

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

1Locked38.9150
2Locked38.9200
3Locked40.3130
4Locked38.9240
5Locked38.9200
6Locked38.690
7Locked38.6210
8Locked38.9170
9Locked38.9130
10Locked38.9170
11Locked38.6150
12Locked40.3200
13Locked38.9220
14Locked38.9250
15Locked38.6230
16Locked40.3170
17Locked38.9310
18Locked40.9300
19Locked40.3360
20Locked40.3280
21Locked38.9390
22Locked38.9330
23Locked38.9220
24Locked38.9340

 

0 Kudos
Reply
  • 5
  • 0
  • 0
bagginz
Joining in
190 Views
Message 4 of 7
Flag for a moderator

Re: Repaired but slow

Upstream bonded channels

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

14620000040.8512016 qam73
23940000039.8512016 qam74
32580000038512016 qam76
43260000038.8512016 qam75



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0010
3ATDMA0020
4ATDMA0010
0 Kudos
Reply
  • 5
  • 0
  • 0
bagginz
Joining in
188 Views
Message 5 of 7
Flag for a moderator

Re: Repaired but slow

Network Log

Time Priority Description

2019-01-29 10:46:38.00Warning!Lost MDD Timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-29 10:49:17.00criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:28.00Warning!MDD message timeout;CM-MAC=;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:28.00Warning!Lost MDD Timeout;CM-MAC=;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 09:21:20.00criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:29.00Warning!Lost MDD Timeout;CM-MAC=;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
1970-01-01 00:01:29.00Warning!MDD message timeout;CM-MAC=;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 10:49:22.00criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:00:28.00Warning!RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:00:31.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:00:31.00Warning!RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:00:33.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:00:33.00Warning!RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:00:34.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:00:34.00Warning!RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:00:38.00Warning!Lost MDD Timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:02:48.00Warning!RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:02:50.00criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 11:02:50.00Warning!RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
2019-01-31 14:19:39.00criticalNo Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
  • 5
  • 0
  • 0
bagginz
Joining in
187 Views
Message 6 of 7
Flag for a moderator

Re: Repaired but slow

Thank you for your reply i hope these are the correct figures you asked for

0 Kudos
Reply
  • 26.7K
  • 1.01K
  • 1.91K
Forum Team (Retired) Kath_F
Forum Team (Retired)
137 Views
Message 7 of 7
Flag for a moderator

Re: Repaired but slow

Hi bagginz, 

Thanks for your post and apologies to hear that you are having an issue with your connection. 

Checking the stats of your hub, all power levels and signal levels are where they should be. There is no area fault and the only thing showing up red is the wifi which suggests an issue with one of your devices. 

Are you getting this issue on all devices? 

When testing the speed through the ethernet cable, are you able to get the higher speeds?

Let us know.

Thanks,

Kath_F
Forum Team



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


0 Kudos
Reply