Fehler im Modem-Logfile

[sbe]

Moin,

mein Internetzugang ist seit ca. 4 Wochen nicht mehr zuverlässig, auch nach mehreren Anrufen bei der Hotline gibt es keine Lösnug seitens KDG. Das Modem-Logfile weist die folgenden Fehlermeldungen auf. Was könnte die Ursache sein?

Gruß
stefan

2010-05-11 17:01:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 17:00:53 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:39:37 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:34:38 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:30:17 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:26:57 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:21:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:20:14 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:19:32 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:17:46 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:17:05 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:17:04 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:17:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:17:02 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:16:39 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:12:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:11:55 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:11:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:10:45 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:10:35 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:10:34 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:10:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 13:10:06 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 11:20:51 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 11:20:50 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:50:16 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:50:12 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:50:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:44 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:32 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:31 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:30 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:29 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:28 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:27 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:24 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:23 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:21 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:49:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:48:40 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:48:20 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:48:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 10:47:40 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:57:39 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:57:11 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:56:37 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:56:36 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:56:17 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:56:16 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:56:15 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:56:05 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:55:48 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:55:27 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:55:06 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:54:46 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:54:26 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:54:06 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:53:46 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:53:26 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:54 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:36 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:35 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:34 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:33 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:32 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:31 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:30 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:29 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:28 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:03 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:01 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:39:00 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 08:38:59 3-Critical R02.0 No Ranging Response received - T3 time-out
2010-05-11 06:10:44 6-Notice I401.0 TLV-11 - unrecognized OID
2010-05-11 06:10:44 7-Information B401.0 Authorized

[kickdown]

habe genau das gleiche problem seit freitag.
No Ranging Response received - T3 time-out

[ihk.]

Warum zwei Beiträge zum selben Thema. ICh könnte mir vorstellen, dass es in Osdorf Ausbauarbeiten gibt. Eventuell könnte hier die "heiße Linie" helfen.

[sbe]

Bei mir wurde der ÜP getauscht, seitdem funktioniert es. Allerdings auch nur noch mit 10MBit/s.
Aber ich bin eh' in 2 Wochen weg von KDG, habe gerade noch rechtzeitig gekündigt und mir einen neuen Anbieter gesucht.

Gruß
sbe

[Master2]

T3 ( Ranging Request Retries Exhausted )

Explanation: The cable modem has sent 16 Ranging Request (RNG-REQ) messages without receiving a Ranging Response (RNG-RSP) message in reply from the CMTS. The cable modem is therefore resetting its cable interface and restarting the registration process. This typically is caused by noise on the upstream that causes the loss of MAC-layer messages. Noise could also raise the signal-to-noise ratio (SNR) on the upstream to a point where the cable modem's power level is insufficient to transmit any messages. If the cable modem cannot raise its upstream transmit power level to a level that allows successful communication within the maximum timeout period, it resets its cable interface and restarts the registration process. This error message is DOCSIS event message is R03.0, Ranging Request.


Quelle: http://www.dslreports.com/faq/13055