Quote:
|
Originally Posted by greyripper
Can anyone help decipher these errors?
I suspect connection problem with the NTL network rather than on my (ethernet) side.
Any comments and thoughts very welcome, I am suffering from frequent (70-80 each day) loss of connection. Anything from 2 seconds to 10 of minutes lost each time).
Time Not Established Time Not Established 1 Critical(3) 68000300 DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established 2 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 8 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 9 Critical(3) 84000200 SYNC Timing Synchronization failure - Failed to acquire FEC f...
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 8 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 8 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 8 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
Time Not Established Time Not Established 1 Critical(3) 82000700 Unicast Ranging Received Abort Response - Re- initializing MAC
Time Not Established Time Not Established 4 Critical(3) 82000200 No Ranging Response received - T3 time-out
|
Hi greyripper,
Most of the above relate to the modem trying to scan and find a downstream to lock onto which it isnt.
No time stamp on any of them.
The 68000300 is from the DHCP server trying to send info which the modem is not understanding.
Quote:
|
Originally Posted by greyripper
BTW.
CM has been replaced, connections remade at house and distribution box, swap to another UBR, tap swapped in distribution box.
Concurrent with the CM problems (loss of SYNC and READY) I get a flashing light on the (SAmsung) set-top box. Does anyone know how to access the event log on the STB??
---------- Post added at 22:06 ---------- Previous post was at 22:05 ----------
I have contacted NTL, has three engineers so far, another one tomorrow. Each call is treated like a new one, getting sick of spending 30-40 minutes on the phone each time!
|
I think to access on the STB it is page up and page down.
However I think you may have to endure another engineer visit if your sync and ready lights are dropping then this would indicate by way of the sync light and the logs it is failing to lock onto the downstream.
Maybe your downstream power is fluctuating.
When the connection drops what are the power levels showing, take them from the first screen where you got the logs froms.
