Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

No Ranging Response received - T3 time-out

Go to solution
Lexsed
Tuning in

on ‎08-05-2017 19:54

Hi,

Got this going on for the last month or so, frequent drops, while short, are extremely annoying and frequent. Tried all the troubleshooting I could find here, as well as from 3rd party sources, but no dice, it comes back and goes away randomly

Here are the logs which I assume can help determine the issue:

Date Time Error Number Error Description

08/05/201718:35:04 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:35:02 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:33:43 GMT66050310Auth Success - Web login successful.
08/05/201718:31:26 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:31:00 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:30:59 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:28:35 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:28:09 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:21:56 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:21:55 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:15:53 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:15:45 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:10:56 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:10:40 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:10:10 GMT84020200Lost MDD Timeout
08/05/201718:08:41 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:08:06 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:07:51 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:07:50 GMT82000200No Ranging Response received - T3 time-out
08/05/201718:07:46 GMT82000200No Ranging Response received - T3 time-out

 

Downstream Channels

Lock StatusChannel IDFrequencyModulationRx PowerRxMERPre RS ErrorsPost RS ErrorsLocked1171000000 Hz256 QAM-5.6 dBmV 37.1 dB994843745736Locked2179000000 Hz256 QAM-5.7 dBmV 37.6 dB955494700219Locked3187000000 Hz256 QAM-5.6 dBmV 37.6 dB1090159729393Locked4195000000 Hz256 QAM-5.6 dBmV 37.1 dB1309304915025Locked5203000000 Hz256 QAM-5.7 dBmV 37.4 dB1196401796995Locked6211000000 Hz256 QAM-5.9 dBmV 37.4 dB841841575510Locked7219000000 Hz256 QAM-6.0 dBmV 37.4 dB775186506153Locked8227000000 Hz256 QAM-6.0 dBmV 37.6 dB778429499077

Upstream Channels

Lock StatusChannel IDFrequencyModulationTx PowerModeChannel BandwidthSymbol RateLocked7439400000 HzATDMA48.3 dBmV16QAM6400000 Hz5120 Ksym/secNotLocked00 Hz 0 dBmV  0 Ksym/secNotLocked00 Hz 0 dBmV  0 Ksym/secLocked7625800000 HzATDMA46.8 dBmV16QAM6400000 Hz5120 Ksym/sec

0 Kudos
118 REPLIES 118

Go to solution
Dean_C
Moderator
Moderator
In response to Ron-ski

on ‎22-08-2019 21:50

Hello Ron-ski, 

 

Welcome to our community forum it's great to have you on board. 


I'm very sorry about the connection drop outs you have been experiencing since the start of the month and I'm confident that the replacement Hub we're sending out to you will fix the problem. 

 

If do you continue to experience drop outs once you have activated your new Hub then please let us know so we can assist you further. 

 

Thanks, 

 

Dean C 

0 Kudos

Go to solution
Ron-ski
On our wavelength
In response to Dean_C

‎23-08-2019 12:19 - edited ‎23-08-2019 12:20

@dean_C It's dropped out twice already this morning, the one just after 7pm last night was where I changed over the hub. I'm on proper fibre to the house with a media converter outside then coax into the house. 

 

 

My Broadband Ping - Ronski's Virgin Cable

0 Kudos

Go to solution
Ron-ski
On our wavelength
In response to Ron-ski

on ‎23-08-2019 22:16

It seems in the previous post I shared a live graph, here's a snapshot graph for the day showing the drop outs after we changed the hub the night before.

My Broadband Ping - Ronski's Virgin Cable

0 Kudos

Go to solution
Ron-ski
On our wavelength
In response to Ron-ski

‎27-08-2019 20:10 - edited ‎27-08-2019 20:12

Well just spent an infuriating 33 minutes on the phone to support, they really do not listen do they! They seem obsessed with peoples problems being wi-fi related (which no doubt a lot are) but I've explained I'm not the usual average user, explained I've checked the logs and have other monitoring (TBB ping monitor) in place and still they ask if I'm using an Apple or Android phone, talk about bang my head against the wall.

Anyway end result is that they are sending an engineer to look at my router, hope he knows how to navigate pfSense! Whilst he's here hopefully he'll check the coax/fibre side of things.

 

Openreach are installing FTTP soon, that can't come soon enough.

My Broadband Ping - Ronski's Virgin Cable

Go to solution
Peterwilks19
Joining in

on ‎28-08-2019 00:08

Hi, I've started having this issue over the last few days it got to the point its in a constant loop of connecting, when I go on webchat im told it'll be fixed the next day several times. Below is the log from the router.

2019 18:14:55Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;24/08/2019 18:26:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;24/08/2019 19:19:47noticeReceived REG-RSP while in REG-HOLD1 state;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;24/08/2019 19:21:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;25/08/2019 06:31:54criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;25/08/2019 06:31:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;25/08/2019 16:08:11Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;25/08/2019 16:10:20criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;01/01/1970 00:01:52Warning!ToD request sent - No Response received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;25/08/2019 17:53:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;26/08/2019 14:02:44criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;26/08/2019 14:02:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;26/08/2019 16:35:45criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;26/08/2019 16:35:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;27/08/2019 09:32:56Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;27/08/2019 09:35:16criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;27/08/2019 23:20:3criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;27/08/2019 23:20:3criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;27/08/2019 23:25:15noticeReceived REG-RSP while in REG-HOLD1 state;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;27/08/2019 23:28:10criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Up until this point the connection has been rock solid and very fast. 

0 Kudos

Go to solution
Ron-ski
On our wavelength
In response to Peterwilks19

on ‎29-08-2019 20:28

Engineers been, he changed the wideband attenuator from 15dB to 3dB and fitted a new 4 way splitter externally where the media convertor is located. He said the fibre installs should have these 4 way splitters, most have been fitted but as mine is not street accessible it wasn't done.

Hopefully this resolves it, only time will tell,  although unless VM come up with a better deal after the latest round price rises we're off elsewhere.

I'm also extremely disappointed with telephone support - the fault description the engineer had was slow and intermittent speed issues. Well I suppose 0 could be classed as a speed issues, but intermittent drop outs would be a better description! This also could have been resolved much sooner as sending out a new hub was a complete waste of time - my modem logs showed what the fault was.

PS Peterwilks19 Good luck on getting yours sorted, although I suspect you'll have to phone up and go through the nonsense that involves.

Go to solution
Ron-ski
On our wavelength
In response to Ron-ski

‎31-08-2019 12:30 - edited ‎31-08-2019 12:30

Well that didn't fix the issues, still getting t3 time outs in the logs.

Friday's TBB graph

My Broadband Ping - Ronski's Virgin Cable

 

Saturdays graph

My Broadband Ping - Ronski's Virgin Cable

0 Kudos

Go to solution
Peterwilks19
Joining in
In response to Ron-ski

on ‎31-08-2019 13:12

I saw VM vans by a box near me with all the equipment out, thag evening all back sorted 🤷‍♂️ must have been a local issue. Seem to have faster upload now too. Either way I'll be getting a separate router as its annoying losing all networking when the connection goes down. 

0 Kudos

Go to solution
bigdaddydeano
Joining in

on ‎11-09-2019 20:30

Found this thread while suffering from what seems to be the same issue...

Glad others are having it - thought it was just due to the heat in summer, but it's still happening (3 times a day now) - was tempted to go buy a new router and just use the H3.0 in modem mode... but maybe there's a fix?

I've even disabled both wifi networks to try and ease up pressure on the router, but it's still struggling with various errors.... Any help? 😞

02/09/2019 22:29:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:32:52criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:33:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:33:12Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:33:13Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:33:14Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:33:16Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:33:18Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:33:18Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:33:21Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:58:32criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:58:32Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:58:39criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:58:39Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:59:15criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:59:16Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:59:23criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 00:59:23Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/09/2019 20:05:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 

Refresh data
Downstream bonded channelsChannel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
12987500009.437256 qam21
21387500009.537256 qam1
31467500009.437256 qam2
41547500009.137256 qam3
5162750000937256 qam4
61707500008.637256 qam5
71787500008.537256 qam6
81867500008.537256 qam7
91947500008.437256 qam8
10202750000837256 qam9
112107500007.637256 qam10
122187500007.637256 qam11
132267500008.337256 qam12
142347500008.337256 qam13
152427500008.337256 qam14
162507500008.937256 qam15
17258750000937256 qam16
182667500009.337256 qam17
19274750000937256 qam18
202827500009.137256 qam19
212907500009.137256 qam20
223067500009.537256 qam22
233147500009.537256 qam23
243227500009.137256 qam24
0 Kudos

Go to solution
Ron-ski
On our wavelength
In response to bigdaddydeano

on ‎11-09-2019 20:40

Using the hub in modem mode makes no difference, in fact it makes getting the fault fixed even harder as the bottom rung support personal haven't got a clue as to what modem mode is, in fact they don't even know what the lights on the front of hub mean.

Something which should be so easy is made so difficult and frustrating because of this, mine still isn't fixed after a month, still having regular drop outs, spent 90 minutes on the phone last week, they were utterly useless - ask to speak to a manager and was cut off. Phone straight, another 20 minutes on hold and we start all other again, they haven't a clue what on ongoing fault is, eventually the guy said he'll put me through to someone that can help, after explaining all over again he couldn't help as his job was to fix printers!

When I can build up the enthusiasm I'm either going to phone again or create a new thread in the hope that someone actually picks it up and helps, otherwise I'll just have to keep paying for a sub standard service.

0 Kudos
Top