My complaint:
HET PROBLEEM IS NIET ECHT OPGELOST!
Totaljoy reageerde op augustus 24th, 2010 at 10:59
Totaljoy,
Inmiddels heb ik prettig gesprek gehad met ziggo. Het bedrag wat mij is aangeboden is een leuke en welkome pleister op de wonde voor de geleden ergenissen.
Echter het gesprek leverde eigenlijk geen aanwijsbare oorzaak aan. Het klopt dat de verbinding al enige dagen weer normaal functioneerde maar dat gebeurd wel vaker. De datum nu is 24 augustus 2010. Gisteravond viel de verbinding weer uit. Ik was moe en heb niet meer gereset maar heb afgesloten en ben naar bed gegaan. Vanochtend nog steeds geen verbinding. Bij controle van de modem was het lampje online uit. Ook het resetten van de modem had hierop geen resultaat. Nu al weer meerdere malen gereset. Modem uitgelezen en levert dit lange raport op: (dit is alleen van gisteren)
Configuration Manager
Status Signal Addresses Configuration Logs Help
This page displays detailed information intended for use by an authorized Motorola Cable Modem technician.
Time Priority Code Message
1970-01-01 01:20:19 3-Critical D003.0 DHCP WARNING – Non-critical field invalid in response.
1970-01-01 01:20:15 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:20:04 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 01:20:04 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:17:02 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 01:16:18 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:16:13 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 01:15:34 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:15:19 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 01:15:19 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:12:53 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 01:12:13 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:12:08 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 01:11:27 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:11:21 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 01:11:21 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:09:04 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 01:09:04 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:05:34 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 01:04:51 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:04:45 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 01:04:04 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:03:19 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 01:02:21 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:01:59 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 01:01:15 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 01:01:13 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 01:00:31 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:59:58 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:59:03 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:58:41 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:57:45 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:57:35 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:56:51 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:56:33 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:56:33 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:53:58 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:53:15 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:53:09 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:52:23 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:52:20 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:52:20 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:48:47 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:47:47 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:47:27 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:46:47 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:46:39 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:45:57 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:45:08 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:44:19 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:43:44 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:43:04 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:43:00 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:42:15 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:41:56 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:41:08 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:40:41 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:39:49 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:39:20 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:38:37 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:38:31 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:37:34 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:36:47 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:35:51 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:35:08 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:34:36 3-Critical R005.0 Started Unicast Maintenance Ranging – No Response received – T3 time-out
1970-01-01 00:34:05 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:33:45 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:32:55 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:32:37 3-Critical T002.0 SYNC Timing Synchronization failure – Failed to acquire FEC framing
1970-01-01 00:32:36 3-Critical T001.0 SYNC Timing Synchronization failure – Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:36 3-Critical T002.0 SYNC Timing Synchronization failure – Failed to acquire FEC framing
1970-01-01 00:32:36 3-Critical T001.0 SYNC Timing Synchronization failure – Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:35 3-Critical T002.0 SYNC Timing Synchronization failure – Failed to acquire FEC framing
1970-01-01 00:32:34 3-Critical T001.0 SYNC Timing Synchronization failure – Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:34 3-Critical T002.0 SYNC Timing Synchronization failure – Failed to acquire FEC framing
1970-01-01 00:32:33 3-Critical T001.0 SYNC Timing Synchronization failure – Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:32:25 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:32:25 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:29:19 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:28:40 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:28:35 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:27:53 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:27:46 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:27:46 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:23:47 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:22:43 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:22:03 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:21:19 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:21:07 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:20:05 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:19:27 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:18:26 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:17:46 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:17:03 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:16:57 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received – T4 timeout
1970-01-01 00:16:17 3-Critical R002.0 No Ranging Response received – T3 time-out
1970-01-01 00:16:06 3-Critical T001.0 SYNC Timing Synchronization failure – Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:15:52 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:15:52 3-Critical R002.0 No Ranging Response received – T3 time-out
Dit zijn weer andere meldingen dan de periode hiervoor. HET PROBLEEM IS DUS NIET ECHT OPGELOST.
Ik heb alleen een stukje service ontvangen voor geleden schade. (wanneer het afgesproken bedrag daadwerkelijk wordt overgemaakt).
Graag zou ik een afdoende oplossing willen ontvangen. Die de klachten voorgoed doen verdwijnen.
Gewenste oplossing
Een verklaring van de oorzaak.
Een werkende oplossing voor 24/7 internetverbinding.

