Internet connecton not working

gerbilus · 16-05-2008, 09:18

Hello!

I am having problems with my 2Mb internet connection.
Here are my modem signal info and logs (its a motorola SB5100)

Downstream:
Frequency 331000000 Hz Locked
Signal to Noise Ratio 40 dB
Power Level 10 dB

Upstream:
Channel ID 3
Frequency 34000000 Hz Ranged
Power Level 42 dBmV

Log:
2008-05-15 20:48:55 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-15 20:46:42 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:00:13 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-15 20:35:56 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-15 18:44:36 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:02:13 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:02:10 3-Critical 0x040D9964 DHCP FAILED - Discover sent, no offer received
2008-05-15 17:52:37 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:00:13 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-14 21:10:37 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:00:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-14 03:18:12 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
2008-05-14 03:17:40 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-14 03:17:24 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-05-14 03:16:51 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-11 04:12:35 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response
2008-05-07 11:45:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-04 04:12:35 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response
2008-04-25 20:24:18 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-04-23 16:12:35 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response
2008-04-21 19:17:35 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:00:10 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-03-05 15:51:48 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
2008-03-05 15:51:47 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-03-05 15:51:39 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-03-05 15:51:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:51:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:51:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:49:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:49:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:49:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:49:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:49:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:53 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:27 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:26 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:07 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:47:54 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:47:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:47:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:47:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:47:28 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:47:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:47:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:43:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:43:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:43:29 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:43:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:42:58 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:42:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:42:06 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:42:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:41:39 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:41:36 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:41:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:41:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:41:13 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:41:13 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:41:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:41:07 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:40:46 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:40:46 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:40:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:40:41 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:40:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:40:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:40:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:40:15 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:39:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:39:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:39:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:39:22 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:39:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:39:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:38:01 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:38:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:54 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:54 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:36 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

I simply cannot view web pages for more than a minute or two here and there.
Pings nearly always time out (100% loss!)

I am in the B71 area (Sandwell/West Bromwich)

Can anyone help me please?

Many thank,

Gerb.

broadbandbug · 16-05-2008, 10:49

No return path lock.. You need to ring up VM and at least check for outages in your area.. Otherwise you have a fault!

16-05-2008, 10:50

Quote:

Originally Posted by gerbilus

Hello!

I am having problems with my 2Mb internet connection.
Here are my modem signal info and logs (its a motorola SB5100)

Downstream:
Frequency 331000000 Hz Locked
Signal to Noise Ratio 40 dB
Power Level 10 dB

Upstream:
Channel ID 3
Frequency 34000000 Hz Ranged
Power Level 42 dBmV

Log:
2008-05-15 20:48:55 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-15 20:46:42 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:00:13 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-15 20:35:56 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-15 18:44:36 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:02:13 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:02:10 3-Critical 0x040D9964 DHCP FAILED - Discover sent, no offer received
2008-05-15 17:52:37 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:00:13 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-14 21:10:37 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:00:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-14 03:18:12 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
2008-05-14 03:17:40 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-05-14 03:17:24 3-Critical 0x04E33A10 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout
2008-05-14 03:16:51 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-05-11 04:12:35 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response
2008-05-07 11:45:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-05-04 04:12:35 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response
2008-04-25 20:24:18 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2008-04-23 16:12:35 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response
2008-04-21 19:17:35 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
1970-01-01 00:00:10 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-03-05 15:51:48 6-Notice 0x045A80E4 TLV-11 - unrecognized OID
2008-03-05 15:51:47 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
2008-03-05 15:51:39 3-Critical 0x04E33948 No Ranging Response received - T3 time-out
2008-03-05 15:51:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:51:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:51:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:49:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:49:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:49:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:49:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:49:02 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:53 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:27 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:26 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:07 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:48:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:48:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:47:54 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:47:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:47:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:47:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:47:28 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:47:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:47:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:43:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:43:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:43:29 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:43:18 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:42:58 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:42:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:42:06 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:42:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:41:39 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:41:36 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:41:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:41:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:41:13 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:41:13 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:41:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:41:07 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:40:46 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:40:46 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:40:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:40:41 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:40:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:40:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:40:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:40:15 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:39:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:39:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:39:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:39:22 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:39:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:39:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:38:01 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:38:00 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:59 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:58 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:57 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:56 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:56 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:54 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:54 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:45 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:44 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2008-03-05 15:37:36 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2008-03-05 15:37:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing

I simply cannot view web pages for more than a minute or two here and there.
Pings nearly always time out (100% loss!)

I am in the B71 area (Sandwell/West Bromwich)

Can anyone help me please?

Many thank,

Gerb.

Your power levels are almost perfect for the modem you have the Downstream power a bit high at 10db but is stiil between -12db and +12db.

But I find your modem logs to be very unusual it looks like you could suffering from the modem doing what is called Flapping by this I mean it loses the connection and basically flaps around trying to re connect.

You need to call Tech Support on 0906 212 1111 and talk to them, especially after you lose a connection.

I usually recommend that you ignore the config logs but yours is very unusual and looks like a genuine fault.

gerbilus · 16-05-2008, 10:58

Many thanks for your help!

grdead · 16-05-2008, 14:13

Technical support generally runs a line test all the way to your modem and that is it . If they can not see a fault in that line test they would simply tell you that the fault could be with your system . Its better you get prepared . And yes , as others suggested , you have to call tech support the moment your connection drops.

gerbilus · 19-05-2008, 09:17

I called the tech support last friday - they got me to do the usual restarts and ipconfig renew , ping etc it worked for a few minutes then stopped again. Two people promised to call me back on friday night - neither did. One even said that doing ping from a DOS prompt bypasses my firewall ?!?!?!?!?! - Was very funny - I turned it off and it made no difference :-)

I managed to get someone else on saturday who sounded like he knew what he was talking about - again went through some stuff. He thinks I have more than one firewall on my PC (I don't) or something stopping him from pinging my PC (which had obtained a valid IP address) buy that doesn't explain why I get problems connecting using e.g. PSP or PS3 does it?

Anyways, thanks for your responses!

Gerb.

Graham M · 19-05-2008, 09:29

Quote:

Originally Posted by gerbilus

One even said that doing ping from a DOS prompt bypasses my firewall

/Facepalm

19-05-2008, 10:01

Quote:

Originally Posted by gerbilus

I called the tech support last friday - they got me to do the usual restarts and ipconfig renew , ping etc it worked for a few minutes then stopped again. Two people promised to call me back on friday night - neither did. One even said that doing ping from a DOS prompt bypasses my firewall ?!?!?!?!?! - Was very funny - I turned it off and it made no difference :-)

I managed to get someone else on saturday who sounded like he knew what he was talking about - again went through some stuff. He thinks I have more than one firewall on my PC (I don't) or something stopping him from pinging my PC (which had obtained a valid IP address) buy that doesn't explain why I get problems connecting using e.g. PSP or PS3 does it?

Anyways, thanks for your responses!

Gerb.

Is the any change in your config pages mainly the status and signal pages, as I have already said yoyr logs are unusual in my earlier post.

Sorry that Tech Support are not being of any help to you.

gerbilus · 19-05-2008, 10:37

Status & Signal pages - no changes. The log - more of the messages I had earlier.
I have an engineer due to visit tomorrow morning now, so will see what happens. Am worried he/she will just connect their own laptop to my modem and it will work perfectly.

I know the phone tech support can only do so much. The frustrating thing is that my broadband connection has been near perfect for over 2 years now - have been using a wireless router with no problems whatsoever - able to use it with PSP, PS3, Wii, 2 Laptops, a desktop running ubuntu.Oh and a Wifi enabled Mobile phone! The fact that all my devices have problems suggests it ain't my fault surely? I ain't ranting here - just want my broadband back :-)

Oh and my girlfriend mentioned that our TV on-demand has also been out since last wednesday (unrelated I'm sure ;-)

Once again many thats to y'all for your constructive postings.

Gerb.

19-05-2008, 11:11

Quote:

Originally Posted by gerbilus

Status & Signal pages - no changes. The log - more of the messages I had earlier.
I have an engineer due to visit tomorrow morning now, so will see what happens. Am worried he/she will just connect their own laptop to my modem and it will work perfectly.

I know the phone tech support can only do so much. The frustrating thing is that my broadband connection has been near perfect for over 2 years now - have been using a wireless router with no problems whatsoever - able to use it with PSP, PS3, Wii, 2 Laptops, a desktop running ubuntu.Oh and a Wifi enabled Mobile phone! The fact that all my devices have problems suggests it ain't my fault surely? I ain't ranting here - just want my broadband back :-)

Oh and my girlfriend mentioned that our TV on-demand has also been out since last wednesday (unrelated I'm sure ;-)

Once again many thats to y'all for your constructive postings.

Gerb.

TV comes in on the same Cable but thats a call to DTV faults on 151.

The config pages on your modem are not going to change if a different computer is connected to it.

gerbilus · 19-05-2008, 11:37

Only using 1 laptop at moment - connected directly to cable modem using ethernet cable.
I wanted to take my router out of the equation (I guessed Tech Support would tell me to anyway) Even tried several different ethernet cables just in case one was dodgy - no difference.

Interestingly the last Tech guy I spoke to said he couldn't ping my laptops IP address - This was even after I removed my firewall. Yet he was able to remotely power-cycle the modem one time.

If it is something on my Laptop I just don't know what it is :-)
Maybe its my router as well as my laptops....

Cheers whydoi....

Gerb.

grdead · 19-05-2008, 11:50

Quote:

Originally Posted by gerbilus

Status & Signal pages - no changes. The log - more of the messages I had earlier.
I have an engineer due to visit tomorrow morning now, so will see what happens. Am worried he/she will just connect their own laptop to my modem and it will work perfectly.

I know the phone tech support can only do so much. The frustrating thing is that my broadband connection has been near perfect for over 2 years now - have been using a wireless router with no problems whatsoever - able to use it with PSP, PS3, Wii, 2 Laptops, a desktop running ubuntu.Oh and a Wifi enabled Mobile phone! The fact that all my devices have problems suggests it ain't my fault surely? I ain't ranting here - just want my broadband back :-)

Oh and my girlfriend mentioned that our TV on-demand has also been out since last wednesday (unrelated I'm sure ;-)

Once again many thats to y'all for your constructive postings.

Gerb.

Gerb.... did the guys at tech support make you to establish a direct connection between the cable modem and the computer ?. I believe that they should make you to go for a direct connection and then run the tests on the cable modem ( they call it "Bluetools test" / "Whitetools Test" ). Once they run the tests they can dig up some old data ( for teh past 24/48/72 hours) that could help them to understand as whether its an issue with Intermittent connection or not. Also, do ask them to check for any "Overutilised Downstream issues" on your cable. Best of Luck !!

19-05-2008, 16:36

Quote:

Originally Posted by grdead

Gerb.... did the guys at tech support make you to establish a direct connection between the cable modem and the computer ?. I believe that they should make you to go for a direct connection and then run the tests on the cable modem ( they call it "Bluetools test" / "Whitetools Test" ). Once they run the tests they can dig up some old data ( for teh past 24/48/72 hours) that could help them to understand as whether its an issue with Intermittent connection or not. Also, do ask them to check for any "Overutilised Downstream issues" on your cable. Best of Luck !!

He is on the Knowsley Platform and they do not use BlueTools/WhiteTools they are NTL only.

Plus you are always asked to connect directly to the modem to run any diagnostics to ensure that they get the correct readings.

gerbilus · 20-05-2008, 12:25

VM Engineer has paid me a visit - he didnt do much here just checked the modem levels, checked the set top box (on demand very slow or not workimg at all) and the external connections outside my home. All ok. He said there does appear to be a fault of some sort in the area- an he has passed that on to the next engineer up the chain - not just me getting this problem apparently. Will see if things improve over the next day or so.

Yet again, many thanks for everyone replies.

Cheers,

Gerb.

gerbilus · 20-05-2008, 18:07

Just to let you good people know my broadband has been back on and working perfectly for a good 4 hours now. Now I just need to call 150 and make sure I'm not charged for those Tech Support calls.... :-)

Cheers,

Gerb.