cancel
Showing results for 
Search instead for 
Did you mean: 

Constant disconnects while gaming

Famous182
Tuning in

Hi.

I'm really at my wits end and needing some help...I have tried to call but get an automated system telling me I have "intermittent issues" before disconnecting on me and I got nowhere on the online chat.

For months I have been getting kicked from online games every now and then, recently however it has escalated to kicking me a few times a night (sometimes as much as 3/4 times an hour) and its making playing online for myself and my son ununbearable. At the same time, the wifi drops on my mobile phone and other connected devices.

I have seen a few people having similar issues and in my quest to get to the bottom of this I have set up a BQM that I will post. I also have logs from router if required.

Cheers.

Screenshot_20210802-173106_Samsung Internet.jpg

 

1 ACCEPTED SOLUTION

Accepted Solutions

If I could respectfully suggest for the forum staff to book a technician, please? 

Notwithstanding that there's no problems evident from VM's side, the BQM shows a repeating problem of both poor latency and packet loss, the hub data (VM's own equipment, monitoring VM's network connection) is reporting far too many uncorrectable errors on the downstream, the upstream T3 timeout count is far too high for the few days since last reboot, and the network log confirms repeated channel loss errors.  

 

 

See where this Helpful Answer was posted

15 REPLIES 15

Andrew-G
Alessandro Volta

The BQM confirms there's a problem, it doesn't identify the cause.  Hub status data can often help with that.

Connect to the hub by clicking on this link http://192.168.0.1/  That should pull up the log in page for the hub.  But don't log in, just click on the link "Check router status"  That'll bring up a window with five tabs.  Open the Downstream tab.  Select all the text (Ctrl-A if using a keyboard), copy it (Ctrl-C), then paste it (Ctrl-V) into a reply here as TEXT not screenshots.  Post that, do the same for the Upstream and Network log.  You'll get an error message when you post the Network log, just click on "post" a second time.

Then we can check for any obvious problems with power, noise or error counts.

Famous182
Tuning in

 

 

13310000007.538256 qam25
22670000006.138256 qam17
32750000006.138256 qam18
42830000006.538256 qam19
52910000006.638256 qam20
6299000000738256 qam21
7307000000738256 qam22
83150000007.138256 qam23
93230000007.338256 qam24
103390000007.438256 qam26
113470000007.340256 qam27
12355000000740256 qam28
13363000000740256 qam29
14371000000738256 qam30
153790000007.138256 qam31
163870000007.438256 qam32
173950000007.440256 qam33
184030000007.338256 qam34
194110000007.138256 qam35
20419000000740256 qam36
21427000000738256 qam37
22435000000738256 qam38
234430000006.938256 qam39
244510000007.140256 qam40


Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.960
2Locked38.940
3Locked38.650
4Locked38.950
5Locked38.950
6Locked38.940
7Locked38.960
8Locked38.660
9Locked38.950
10Locked38.960
11Locked40.360
12Locked40.390
13Locked40.360
14Locked38.950
15Locked38.680
16Locked38.950
17Locked40.360
18Locked38.930
19Locked38.940
20Locked40.320
21Locked38.940
22Locked38.980
23Locked38.6200
24Locked40.320

Famous182
Tuning in

 

14619999343.8512064 qam11
23939891943512064 qam12
35370000443.8512064 qam10
46029998843.8512064 qam9


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0010
2ATDMA0010
3ATDMA0000
4ATDMA0000

Famous182
Tuning in
03/08/2021 08:42:39criticalNo Ranging Response received - T3 time-out;CM-MAC=48:4a:3a:23;CMTS-MAC=5c:83:6a:3f;CM-QOS=1.1;CM-VER=3.0;
03/08/2021 08:41:55criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=48:3a:23;CMTS-MAC=5c:c:6a:3f;CM-QOS=1.1;CM-VER=3.0;
03/08/2021 08:38:45Warning!Lost MDD Timeout;CM-MAC=48:a:3a:23;CMTS-MAC=5c:83:8f:M-QOS=1.1;CM-VER=3.0;
03/08/2021 08:38:44criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=4a:3a:23;CMTS-MAC=5c:83:f;CM-QOS=1.1;CM-VER=3.0;
03/08/2021 08:34:16criticalNo Ranging Response received - T3 time-out;CM-MAC=48:d3:43;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;C.0;
03/08/2021 08:32:57criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=48:23;CMTS-MAC=5c:83-QOS=1.1;CM-VER=3.0;
03/08/2021 08:31:12Warning!RCS Partial Service;CM-MAC=48:23;CMTS-MAC=5c:83:8f;CM-VER=3.0;
03/08/2021 08:30:59criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=48:3a:23;CMTS-MAC=5c:83:3f;CM-QOS=1.1;CM-VER=3.0;
03/08/2021 08:30:59Warning!Lost MDD Timeout;CM-MAC=48:d3:23;CMTS-MAC=5c:83:8f:dc=1.1;CM-VER=3.0;
02/08/2021 22:28:51Warning!RCS Partial Service;CM-MAC=48:d3:43:CMTS-MAC=5c:83:f;CM-QOS=1.1;CM-VER=3.0;
02/08/2021 20:22:42criticalNo Ranging Response received - T3 time-out;CM-MAC=48:d3:43:23;CMTS-MAC=5c:83:3f;CM-QOS=1.1;CM-VER=3.0;
02/08/2021 20:02:56noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=5c:83:3f;CM-QOS=1.1;CM-VER=3.0;
02/08/2021 20:02:51Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=48:d3:a:23;CMTS-MAC=5c:83:8f:OS=1.1;CM-VER=3.0;
02/08/2021 17:19:35noticeLAN login Success;CM-MAC=48:d3:23;CMTS-MAC=5c:83:8f:3f;CM-QOS=1.1;CM-VER=3.0;
02/08/2021 17:18:41Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=48:d3:23;CMTS-MAC=5c:a:3f;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:39criticalNo Ranging Response received - T3 time-out;CM-MAC=48:23;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/08/2021 17:05:53noticeLAN login Success;CM-MAC=48:d3:3a:23;CMTS-MAC=5c:83;CM-QOS=1.1;CM-VER=3.0;
02/08/2021 17:05:41Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=48:3a:23;CMTS-MAC=5c:83:3f;CM-QOS=1.1;CM-VER=3.0;
02/08/2021 16:28:2noticeLAN login Success;CM-MAC=48:3a:23;CMTS-MAC=5c:dc:6a:3f;CM-QOS=1.1;CM-VER=3.0;
02/08/2021 11:32:2Warning!RCS Partial Service;CM-MAC=48:a:23;CMTS-MAC=5c:dc:6a:3f;CM-QOS=1.1;CM-VER=3.0;

Thanks for the reply. Ive posted the relevant info.

 

Cheers. 

Unfortunately I can't see obvious problems with the posted data (staff can see more and may be able to), although the network log confirms the patchy connection.  Looks like you rebooted the hub shortly before posting the data - that zeroes the error counters and renegotiates the connection, which can delete the evidence of problems.  Might be worth letting the hub run for a good few hours, and posting the same data again.

Yeah I did reboot it to see if it cleared any issues. Didnt work.

 

Ok thanks ill post updated logs later. Which part specifically? 

 

Cheers.

Same again, please - Downstream, Upstream, Network log.

I’m having the same issue only when gaming internet is fine otherwise