- Zeitweiser Ausfall Internet Beitrag #1
dj2ub
- Beiträge
- 70
- Punkte Reaktionen
- 0
Hallo,
ich habe 3play von UM und bin bis jetzt sehr zufrieden gewesen.
In letzter Zeit habe ich immer wieder kurze Ausfälle vom Internet. Wenn ich in das Log von dem Motorola Kabelmodem sehen erscheinen dann folgende Fehlermeldungen:
2010-06-10 07:33:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:33:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:33:02 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:33:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:33:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:32:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:32:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:32:57 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:32:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:57 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:53 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:52 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:51 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:50 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:57 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:53 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 04:33:17 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 04:33:16 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 04:33:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 04:33:14 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:43 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:42 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:41 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:40 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:39 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:38 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:02 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:23 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:22 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:20 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:19 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:18 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:17 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:16 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:14 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:13 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:12 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:02 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:20:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:20:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 18:08:45 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:43 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:42 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:10 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:09 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:08 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:07 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:06 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:05 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:02 3-Critical R02.0 No Ranging Response received - T3 time-out
Folgende Signalwerte kann ich am Kabelmodem auslesen:
Frequency 642000000 Hz
Signal to Noise Ratio 35 dB
Downstream Modulation QAM256
Network Access Control Object ON
Power Level 4 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
Upstream Value
Channel ID 6
Frequency 42320000 Hz
Ranging Service ID 6302
Symbol Rate 2.560 Msym/s
Power Level 43 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM
Eine Überprüfung gestern durch UM hat ergeben, dass kein Fehler feststellbar ist.
Soll ich nochmals eine Störmeldung machen oder vielleicht gibt es eine andere Lösung.
Über Antworten würde ich mich sehr freuen.
DJ2UB
ich habe 3play von UM und bin bis jetzt sehr zufrieden gewesen.
In letzter Zeit habe ich immer wieder kurze Ausfälle vom Internet. Wenn ich in das Log von dem Motorola Kabelmodem sehen erscheinen dann folgende Fehlermeldungen:
2010-06-10 07:33:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:33:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:33:02 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:33:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:33:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:32:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:32:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:32:57 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:32:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:57 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:53 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:52 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:51 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 07:20:50 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:57 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 06:41:53 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 04:33:17 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 04:33:16 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 04:33:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-10 04:33:14 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:43 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:42 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:41 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:40 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:39 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 23:35:38 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:02 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 18:49:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:56 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 11:18:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:23 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:22 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:20 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:19 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:18 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:17 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:16 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:14 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:13 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:12 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 10:08:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:02 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:21:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:20:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-09 04:20:58 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 18:08:45 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:43 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:42 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:10 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:09 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:08 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:07 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:06 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:05 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-06-08 03:03:02 3-Critical R02.0 No Ranging Response received - T3 time-out
Folgende Signalwerte kann ich am Kabelmodem auslesen:
Frequency 642000000 Hz
Signal to Noise Ratio 35 dB
Downstream Modulation QAM256
Network Access Control Object ON
Power Level 4 dBmV
The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading
Upstream Value
Channel ID 6
Frequency 42320000 Hz
Ranging Service ID 6302
Symbol Rate 2.560 Msym/s
Power Level 43 dBmV
Upstream Modulation [3] QPSK
[3] 64QAM
Eine Überprüfung gestern durch UM hat ergeben, dass kein Fehler feststellbar ist.
Soll ich nochmals eine Störmeldung machen oder vielleicht gibt es eine andere Lösung.
Über Antworten würde ich mich sehr freuen.
DJ2UB