User Profile

andy1027

Up to speed

Joined 12 years ago

123 Posts1 LikeLikes received

View All Badges

User Widgets

Contributions

Re: Internet still not quite right after Cable Repull
Watching this with interest. Having my own issues. Albeit they don't come close to your situation.
1 year ago Place Networking and WiFi
995Views
0likes
3Comments
Re: Flaky connection - Belfast - Intermittent
I'm unclear why you might think being based in Belfast means they don't have access to our account. They have helped me before.
1 year ago Place Networking and WiFi
1.7KViews
0likes
2Comments
Re: Flaky connection - Belfast - Intermittent

1 year ago Place Networking and WiFi
1.7KViews
0likes
0Comments
Re: Flaky connection - Belfast - Intermittent
I'm disappointed a forum moderator has not yet responded
1 year ago Place Networking and WiFi
1.7KViews
0likes
1Comment
Flaky connection - Belfast - Intermittent
Moved home recently this year and took our VM kit with us as per the moving home process. We've had a good connection using the Super Hub 3 (in Modem mode). In the last two weeks we have noticed the connection to be flaky and has dropped out completely at times. We have rebooted our kit several times and checked the connections on all the cabling. I took a look at the power levels on the super hub and have had a BB monitor running for the last few days to try and get a look on this. Would be grateful for a forum moderator to run some tests on our line to ascertain if we need a technician to visit. Thank you See below BB snapshot graph and stats from the modem. SUPER HUB 3.0 (Modem Mode) Downstream bonded channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 203000000 9.1 40 256 qam 9 2 139000000 8.8 37 256 qam 1 3 163000000 10.4 40 256 qam 4 4 171000000 10.5 40 256 qam 5 5 195000000 9.5 40 256 qam 8 6 227000000 9.1 40 256 qam 12 7 235000000 9.5 40 256 qam 13 8 243000000 9.5 40 256 qam 14 9 251000000 10 40 256 qam 15 10 275000000 10.8 40 256 qam 18 11 283000000 11.5 40 256 qam 19 12 307000000 12.1 38 256 qam 22 13 315000000 11.9 40 256 qam 23 14 331000000 11.9 40 256 qam 25 15 339000000 11.5 40 256 qam 26 16 347000000 11.5 40 256 qam 27 17 355000000 11.4 40 256 qam 28 18 363000000 11.4 40 256 qam 29 19 371000000 11.3 40 256 qam 30 20 379000000 10.9 38 256 qam 31 21 387000000 11.6 40 256 qam 32 22 395000000 12 40 256 qam 33 23 403000000 12.3 40 256 qam 34 24 419000000 12.4 40 256 qam 36 Downstream bonded channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 40.3 4376587 979414 2 Locked 37.6 5606647 2738070 3 Locked 40.3 3649776 1663622 4 Locked 40.3 3666532 1477538 5 Locked 40.3 3604484 1045672 6 Locked 40.3 3349111 627535 7 Locked 40.3 3272514 547070 8 Locked 40.3 3186905 473055 9 Locked 40.3 3097264 413716 10 Locked 40.3 2783774 256886 11 Locked 40.3 2679305 220738 12 Locked 38.9 2361308 132667 13 Locked 40.3 2245594 111520 14 Locked 40.9 2044959 82102 15 Locked 40.3 1961773 71707 16 Locked 40.9 1834799 58936 17 Locked 40.3 1746267 51260 18 Locked 40.3 1712543 47918 19 Locked 40.3 1553984 37356 20 Locked 38.9 1494439 33636 21 Locked 40.3 1431158 30873 22 Locked 40.3 1328795 26236 23 Locked 40.3 1201483 19707 24 Locked 40.3 1117144 18647 Upstream bonded channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 1 49600000 45.3 5120 64 qam 1 2 23600000 46 5120 64 qam 5 3 30100000 46 5120 64 qam 4 4 36600000 45 5120 64 qam 3 5 43100000 46.5 5120 64 qam 2 Upstream bonded channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 1 ATDMA 0 0 4 0 2 ATDMA 0 0 14 0 3 ATDMA 0 0 2 0 4 ATDMA 0 0 7 0 5 ATDMA 0 0 3 0
1 year ago Place Networking and WiFi
1.9KViews
0likes
8Comments
Re: Flaky connection - Belfast - Intermittent
Network Log Time Priority Description 02/10/2024 21:07:29 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 20:18:12 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 18:54:6 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 18:38:50 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:47:30 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:46:56 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:45:52 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:45:48 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:45:42 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:45:16 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:44:49 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:44:40 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:44:28 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:44:23 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:43:56 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:43:47 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:43:11 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:42:51 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:42:27 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/10/2024 13:42:7 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; General Configuration Network access Allowed Maximum Number of CPEs 1 Baseline Privacy Enabled DOCSIS Mode Docsis30 Config file rkldJKDHSUBsgvca69834ncxv Primary Downstream Service Flow SFID 31122 Max Traffic Rate 143750047 Max Traffic Burst 42600 Min Traffic Rate 0 Primary Upstream Service Flow SFID 31119 Max Traffic Rate 22000047 Max Traffic Burst 42600 Min Traffic Rate 0 Max Concatenated Burst 42600 Scheduling Type BestEffort
1 year ago Place Networking and WiFi
1.8KViews
0likes
0Comments
Re: Internet freezes/lags and hub loses connection
Did you get sorted?
1 year ago Place Networking and WiFi
1.1KViews
0likes
1Comment
Re: Not getting 200mbps
Issue resolved. We have since moved home and have a new issue. I will post this on a separate thread
1 year ago Place QuickStart, set up and connections
331Views
0likes
0Comments
Not getting 200mbps
We pay for 200mbps download and we aren't getting it. Also the ping is unreasonably high for what it ought to be. I ran a wired speed test directly to the Super Hub 3 and this was the outcome: See below status from the SH3. Anything out of kilter here? Downstream bonded channels Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID 1 203000000 2.7 40 256 qam 9 2 139000000 5 40 256 qam 1 3 147000000 5.5 40 256 qam 2 4 155000000 5.5 40 256 qam 3 5 163000000 4.6 40 256 qam 4 6 171000000 4.8 40 256 qam 5 7 179000000 3.9 40 256 qam 6 8 187000000 3.9 40 256 qam 7 9 195000000 3.2 40 256 qam 8 10 211000000 2.7 40 256 qam 10 11 219000000 2.5 40 256 qam 11 12 227000000 2.5 40 256 qam 12 13 235000000 2.7 40 256 qam 13 14 243000000 2.5 40 256 qam 14 15 251000000 3 40 256 qam 15 16 259000000 3 40 256 qam 16 17 267000000 3.7 40 256 qam 17 18 275000000 3.7 40 256 qam 18 19 283000000 4.4 40 256 qam 19 20 291000000 4.5 40 256 qam 20 21 299000000 5.5 40 256 qam 21 22 307000000 5.8 40 256 qam 22 23 315000000 5 40 256 qam 23 24 323000000 4.5 40 256 qam 24 Downstream bonded channels Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors 1 Locked 40.3 107 0 2 Locked 40.3 43 0 3 Locked 40.3 20 0 4 Locked 40.3 28 0 5 Locked 40.3 17 0 6 Locked 40.9 30 0 7 Locked 40.9 11 0 8 Locked 40.3 16 0 9 Locked 40.3 26 0 10 Locked 40.3 38 0 11 Locked 40.3 42 0 12 Locked 40.3 38 0 13 Locked 40.9 33 0 14 Locked 40.3 38 0 15 Locked 40.3 35 0 16 Locked 40.3 31 0 17 Locked 40.3 40 0 18 Locked 40.3 30 0 19 Locked 40.3 39 0 20 Locked 40.3 30 0 21 Locked 40.3 44 0 22 Locked 40.3 37 0 23 Locked 40.3 39 0 24 Locked 40.3 57 0 Upstream bonded channels Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID 1 49599970 43 5120 64 qam 1 2 36600049 43.3 5120 64 qam 3 3 43100000 43.3 5120 64 qam 2 4 30100000 43.3 5120 64 qam 4 5 23600000 43 5120 64 qam 5 Upstream bonded channels Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts 1 ATDMA 0 0 2 0 2 ATDMA 0 0 4 0 3 ATDMA 0 0 1 0 4 ATDMA 0 0 2 0 5 ATDMA 0 0 1 0 General Configuration Network access Allowed Maximum Number of CPEs 1 Baseline Privacy Enabled DOCSIS Mode Docsis30 Config file cmreg-vmdg505-bbt057-b.cm Primary Downstream Service Flow SFID 107910 Max Traffic Rate 143750047 Max Traffic Burst 42600 Min Traffic Rate 0 Network Log Time Priority Description 10/03/2024 12:13:16 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/03/2024 11:45:36 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/03/2024 01:38:50 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 05/03/2024 23:45:36 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 04/03/2024 18:15:36 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/03/2024 11:45:36 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 28/02/2024 01:27:31 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 27/02/2024 23:45:36 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 26/02/2024 18:34:35 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 24/02/2024 11:45:36 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 22/02/2024 02:58:55 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 21/02/2024 17:35:54 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 21/02/2024 14:32:22 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 13/02/2024 21:04:25 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 09/02/2024 16:13:23 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 08/02/2024 23:46:13 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 06/02/2024 04:06:32 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 05/02/2024 11:46:13 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 02/02/2024 02:23:38 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; 01/02/2024 23:46:13 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Solved
2 years ago Place QuickStart, set up and connections
speed
905Views
0likes
4Comments
Re: Microsoft are changing the way their emails sync
Its quite possible actually! I have access to another Outlook.com account for a charity I do some work with, and its mailbox was upgraded a while ago to the new Outlook.com ... long before June 30th though... As you referenced in your post, the back end infrastrucutre has also been upgraded. Becuase when I attach the charity mailbox to Outlook 2016 it no longer says 'Active Sync' but rather, Microsoft Exchange. Switching between the charity account back to mine is annoying becuause it constantly reminds me that Im still awaiting on the upgrade lol.
9 years ago Place Digital life
32KViews
0likes
0Comments