Connection problems for 4 monthes

thetorkshireman · 14-07-2007, 09:15

Hi there i am on Virgins Broadband and previous to that was on blueyonder. Over the last 4 months my internet and also interactive tv goes off for periods of time ranging from a few seconds to a day and a half. I have kept a log since may and currently since 25th of may its gone off 127 times. I have been calling Virgin since april and had 2 engineers out and still the same its so frustrating as no one seems to be able to rectify.
Any help would be greatly apriciated also never send virgin a eail as they never reply
when it goes off the log in the motorola modem reads

***BOOTING***SB4200-0.4.9.6-SCM02-NOSH

Does that make sence to anyone
also here is what it reads before it comes back on

070713003910 4-Error X501.35 Unit Update Failed.
070713003910 8-Debug F502.1 Bridge Forwarding Enabled.
070713003909 4-Error E107.0 SW Upgrade Failed after download - Incompatible SW file
070713003909 4-Error X501.28 Unit Update - Not updating. This image is not for this platform.
070713003908 8-Debug M579.3 CM Cert Upgrade Disabled. Motorola CM certificate present
070713003908 8-Debug F502.2 Bridge Forwarding Disabled.
070713003908 7-Information X500.0 Attempting Unit Update
070713003903 6-Notice E102.0 SW Download INIT - Via Config file cm-2148-256
070713003903 8-Debug I503.0 Cable Modem is OPERATIONAL
070713003902 8-Debug F502.1 Bridge Forwarding Enabled.
070713003902 8-Debug F502.3 Bridge Learning Enabled.
070713003902 8-Debug B918.0 Baseline Privacy is skipped
070713003902 6-Notice I401.0 TLV-11 - unrecognized OID
070713003902 6-Notice D501.10 TFTP, Unknown SNMP 30 82 00 11 06 0C 2B 06 01 04 01 8B 15 4D 01 03
070713003902 7-Information X519.8 Unit Update - MMDMMD - SCD flags
070713003902 8-Debug I500.1 DOCSIS 1.0 Registration Completed
070713003902 7-Information I500.4 Attempting DOCSIS 1.0 Registration
070713003902 7-Information D509.0 Retrieved TFTP Config File SUCCESS
070713003902 4-Error D503.0 TFTP, Invalid type, CONTINUE
070713003902 7-Information D507.0 Retrieved Time....... SUCCESS
************ 7-Information D511.0 Retrieved DHCP .......... SUCCESS
************ 5-Warning D3.0 DHCP WARNING - Non-critical field invalid in response
************ 4-Error D530.8 DHCP - Invalid Log Server IP Address.
************ 4-Error D530.6 DHCP - Invalid Time Offset.
************ 5-Warning D520.2 DHCP Attempt# 1 BkOff: 5s Tot DSC:1 OFF:1 REQ:1 ACK:1
************ 7-Information D0.0 DHCP CM Net Configuration download and Time of Day
************ 7-Information T500.0 Acquired Upstream .......... SUCCESS
************ 8-Debug T503.1 Acquire US with status OK, powerLevel 42, tempSid 3093
************ 8-Debug T505.0 Acquired Upstream with status OK
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 7-Information T501.0 Acquired Downstream (331000000 Hz)........ SUCCESS
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq 331000000, US Id 6
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 315000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 307000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 299000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 291000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 283000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 275000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 267000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 259000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 251000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 243000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 235000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 227000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 219000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 211000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 203000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 195000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 187000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 179000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 171000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 163000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 155000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 147000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 139000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 131000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 123000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 115000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 107000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 99000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 91000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 857000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 849000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 7-Information H501.2 HFC: Shutting Downstream Down
************ 8-Debug T503.1 Acquire US with status RR Timeout, powerLevel 0, tempSid 0
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 7-Information H501.17 HFC: UCD Minislot size change.
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 7-Information H501.17 HFC: UCD Minislot size change.
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 7-Information H501.17 HFC: UCD Minislot size change.
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 7-Information T501.0 Acquired Downstream (331000000 Hz)........ SUCCESS
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq 331000000, US Id 5
************ 7-Information H501.2 HFC: Shutting Downstream Down
************ 8-Debug T503.1 Acquire US with status RR Timeout, powerLevel 0, tempSid 0
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 7-Information H501.17 HFC: UCD Minislot size change.
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 7-Information H501.17 HFC: UCD Minislot size change.
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 7-Information H501.17 HFC: UCD Minislot size change.
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 3-Critical R6.0 Unicast Maintenance Ranging attempted - No response - Retries exhausted
************ 3-Critical R5.0 Started Unicast Maintenance Ranging - No Response received - T3 timeout
************ 3-Critical R2.0 No Ranging Response received - T3 timeout
************ 7-Information T501.0 Acquired Downstream (330750000 Hz)........ SUCCESS
************ 8-Debug T509.0 Acquired DS with status OK, DS Freq 330750000, US Id 6
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 833000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 825000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 817000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 809000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 801000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 793000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 785000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 777000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 769000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 761000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 753000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 745000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
************ 8-Debug T509.0 Acquired DS with status NO FEC lock, DS Freq 737000000, US Id 0
************ 3-Critical T2.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing

ladyboy · 15-07-2007, 11:21

have they swapped any equipment one or the other could be knocking either one off..

thetorkshireman · 15-07-2007, 12:25

Yes they have changed the modem once when a engineer came he wassnt going to change it but i insited just as a process of ruling things out. This also affects the interactive services on the tv as well

thetorkshireman · 16-07-2007, 21:38

still none the wiser soemone said it might be my cable but would that cause intermittinet fault any suggestions please

thetorkshireman · 17-07-2007, 19:01

does anyone know if the cadle could cause these problems as i been told it might be that virgin dont know so anyone else who does let me know we need to do there job for them

bigcat · 17-07-2007, 20:41

If it affects the interactive services as well that means theres a problem with the return path.

Did the engineer check the levels in the house/at the cab?

thetorkshireman · 18-07-2007, 21:33

yes but when they came it was all working fine
its intermittent it goes off regular on a day to day basis but its having them here when its ok
what would the return path do and how can i check it

Wicked_and_Crazy · 18-07-2007, 21:35

Sounds more like a signal level issue to me

thetorkshireman · 16-08-2007, 21:28

well finally after 5 monthes they re cabled me and its now been ok for 2 weks hurray why so long to sort out i ask and with no compensation tut tut poor service