Re: Think Broadband Ping Monitor Results (POST YOURS)
 

It still doesn't look great.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Yeah, it went quiet in the morning but has been pretty much dead for a few hours, a support call on Monday methinks.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I guess you have tried powering down your modem? and looked at your stats?

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Upstream
US-1 US-2 US-3 US-4
Channel Type 2.0 N/A N/A 2.0
Channel ID 34 N/A N/A 35
Frequency (Hz) 35800000 N/A N/A 27400000
Ranging Status Success N/A N/A Retries Exceed
Modulation 16QAM N/A N/A 16QAM
Symbol Rate (Sym/sec) 5120000 N/A N/A 5120000
Mini-Slot Size 4 N/A N/A 4
Power Level (dBmV) 46.00 N/A N/A 46.50
T1 Timeouts 0 0 0 0
T2 Timeouts 0 0 0 0
T3 Timeouts 0 0 0 637
T4 Timeouts 0 0 0 0

Tried factory reset, modem mode, you name it, the US is completely dead.

I rang 150 who said it was an SNR fault but didn't have a F code to see what was going on. Basically I only got online again today after the modem finally gave up on using the channel, and now my internet is fine aside from a much slower upload.

http://www.thinkbroadband.com/ping/s...04-10-2015.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

New Shub2ac, new power supply. Fingers crossed.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Past two nights I've had a 90 - 120 minute outage at midnight. I presume they're doing some work in this area [FLIT3]

http://www.thinkbroadband.com/ping/s...07-10-2015.png

http://www.thinkbroadband.com/ping/s...08-10-2015.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Nope, it's still doing it...... :dozey: I've also noticed that it stops connecting to the net several times a day.

http://www.thinkbroadband.com/ping/s...11-10-2015.png

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

13/10/2015 09:40:01 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:59 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:57 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:55 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:53 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:51 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:49 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:46 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:44 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:42 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:40 GMT 82000600 Unicast Maintenance Ranging attempted - No response - Retries exhausted
13/10/2015 09:39:40 GMT 82000300 Ranging Request Retries exhausted
13/10/2015 09:39:38 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:36 GMT 82000200 No Ranging Response received - T3 time-out
13/10/2015 09:39:34 GMT 82000200 No Ranging Response received - T3 time-out


Posted to the VM forums but no remedy found as yet.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

[img]Download Failed (1)[/img]

18/10/2015 10:30:49 GMT 66050310 Auth Success - Web login successful.
18/10/2015 09:54:40 GMT 68010302 DHCP WAN IP - 86.xxxxxxxxx
18/10/2015 09:54:11 GMT 68000407 TOD established
18/10/2015 09:54:00 GMT 84000510 Downstream Locked Successfully
18/10/2015 09:53:44 GMT 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
18/10/2015 09:53:39 GMT 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
18/10/2015 09:53:37 GMT 66050310 Auth Success - Web login successful.
18/10/2015 09:51:58 GMT 67070100 DBC-ACK not received
18/10/2015 09:50:56 GMT 67070100 DBC-ACK not received
18/10/2015 09:49:52 GMT 67070100 DBC-ACK not received
18/10/2015 09:48:50 GMT 67070100 DBC-ACK not received
18/10/2015 09:47:47 GMT 67070100 DBC-ACK not received
18/10/2015 09:46:44 GMT 67070100 DBC-ACK not received
18/10/2015 09:45:41 GMT 67070100 DBC-ACK not received
18/10/2015 09:45:34 GMT 68010302 DHCP WAN IP - 86.xxxxxxx
18/10/2015 09:45:04 GMT 68000407 TOD established
18/10/2015 09:44:54 GMT 84000510 Downstream Locked Successfully
18/10/2015 09:44:38 GMT 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
18/10/2015 09:44:17 GMT 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
18/10/2015 09:43:17 GMT 82000400 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out



I've been posting the graphs, network logs, and power levels, etc to VMs forum, but the responses are practically nil.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I guess all you can do is complain, if you have already had an engineer out, possibly even threaten to leave if you have a good alternative.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

2 techs have been out, new PSU, new SHUB2AC, all levels checked, etc.

What's the most annoying is that it's not the same every day. Not even the same timeouts, etc. And some days have no faults shown in the network log at all.

I've tried to get solutions via their forum to no avail, and explaining on the phone is hopeless.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

I know you have valid reason for doing otherwise but does the same still happen if the SH is left switched on? - merely for diagnostic purposes.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

It didn't happen when I left it on 24/24 for 3 days. But sometimes it doesn't happen for 3 or 4 days anyway after an overnight powerdown.

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

Then surely the next thing in the diagnostic process would be leaving it on 24/7?

Re: Think Broadband Ping Monitor Results (POST YOURS)
 

One of the techie bits of advice was that turning it off should not cause these problems, so it was up to VM to diagnose and fix the problem outside our home.