- Anzeige -

Keine IP Adresse via DHCP vom Kabelmodem

In vielen Netzen von Unitymedia sind Internet und Telefonie bereits verfügbar.
Wichtig:
  • Kunden aus Hessen und Nordrhein-Westfalen können über die Rufnummer 0221 / 466 191 00 Hilfe bei allen Problemen in Anspruch nehmen.
  • Kunden aus Baden-Württemberg können über die Rufnummer 0711 / 54 888 150 Hilfe bei allen Problemen in Anspruch nehmen.

Keine IP Adresse via DHCP vom Kabelmodem

Beitragvon thomasgb » 21.10.2007, 13:51

Ich habe seit dieser Woche Internet + Telefon von Unitymedia installiert bekommen. Leider funktioniert die Vergabe eine IP Adresse via DHCP an meinen Rechner nicht. Windows meldet daraufhin "eingeschränkte Konnektivität" (und hat eine IP Adresse aus dem privaten Bereich vergeben). Wer kennt dieses Problem? Lösungsvorschläge?

Modem-Daten:
Model Name: SBV5121E
Firmware Version: 2.17.1.2
Revision: 10
Vendor Name: Motorola
MTA Firmware name: SBV5121E-2.17.1.2-SCM10-SHNP
Boot Version: 8.5
Hardware Version: 1
BCMA Software Version: 49.46
MIB Version: II
GUI Version: 1.0
VxWorks Version: 5.4
Serial Number: 158155707218966101012004
Firmware Build Time: Jul 27 2006 18:37:16

Modem-Logfile:
2007-10-21 12:25:07 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:25:06 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:24:08 7-Information PROG: SW upgrade Failed in gradual download
2007-10-21 12:24:08 4-Error E104.0 SW Upgrade Failed Before Download - Server not Present
2007-10-21 12:24:08 5-Warning TFTP: Driver Open Error: received MSG_ERR from s2c queue.
2007-10-21 12:24:08 5-Warning TFTP: Driver Error select TFTP_TMOUT.
2007-10-21 12:23:18 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:23:17 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:22:08 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
2007-10-21 12:22:07 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
2007-10-21 12:22:07 6-Notice E102.0 SW Download INIT - Via Config file
2007-10-21 12:22:07 7-Information PROG: Software download file from server 10.126.128.1 started...
2007-10-21 12:22:06 7-Information B401.0 Authorized
2007-10-21 12:22:06 7-Information Starting software download...
2007-10-21 12:22:06 6-Notice I401.0 TLV-11 - unrecognized OID
2007-10-21 12:22:06 7-Information SEC: Mfg CVC from configuration file was verified
2007-10-21 12:22:06 7-Information REGISTRATION COMPLETE - Waiting for Operational status
2007-10-21 12:22:06 7-Information REG: Capability type <16> incorrectly negotiated by CMTS
2007-10-21 12:22:06 7-Information REG: Capability type <15> isn't supported by CMTS
2007-10-21 12:22:06 7-Information Registration file - downloaded
2007-10-21 12:22:05 7-Information Trying to download Configuration file ...
2007-10-21 12:22:05 7-Information Time of day - retrieved
1970-01-01 00:00:14 7-Information DHCP - parameters acquired
1970-01-01 00:00:14 7-Information DHCP: ACK: Setting (*) CM TFTP Boot file: BE_Gold_2_SBV5121_d.cfg
1970-01-01 00:00:14 7-Information DHCP: Setting CM IP address to: 10.126.138.137
1970-01-01 00:00:14 5-Warning D03.0 DHCP WARNING - Non-critical field invalid in response
1970-01-01 00:00:14 5-Warning DHCP: Missing Syslog server
1970-01-01 00:00:14 7-Information DHCP: Setting (*) CM Time Server address to: 10.126.128.1
1970-01-01 00:00:14 7-Information DHCP: Setting (*) CM Subnet mask to: 255.255.224.0
1970-01-01 00:00:14 7-Information DHCP: Setting (*) CM Gateway address to: 10.126.128.1
1970-01-01 00:00:14 5-Warning D03.0 DHCP WARNING - Non-critical field invalid in response
1970-01-01 00:00:14 5-Warning DHCP: Missing UTC Time Offset
1970-01-01 00:00:14 7-Information DHCP: OFFER: Setting (*) CM TFTP Boot file: BE_Gold_2_SBV5121_d.cfg
1970-01-01 00:00:14 7-Information DHCP select: Setting (*) CM TFTP Server address to: 10.126.128.1
1970-01-01 00:00:14 7-Information DHCP: Offered (*) CM IP address to: 10.126.138.137
1970-01-01 00:00:10 7-Information Trying to register through CMTS...
1970-01-01 00:00:10 7-Information SYNCHRONIZED - 586000000 Hz , ucd 4
1970-01-01 00:00:08 7-Information Starting Ranging On Channel 4
1970-01-01 00:00:04 7-Information Downstream Locked - Collecting Upstream Information
1970-01-01 00:00:01 7-Information Scanning frequency 586000000Hz
1970-01-01 00:00:01 7-Information Trying to synchronize ...
1970-01-01 00:00:01 7-Information Vendor Cold Start
2007-10-21 12:15:11 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:15:10 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:14:08 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:14:07 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:14:07 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:14:06 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:14:05 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:14:01 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:14:00 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:01:15 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 12:01:14 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 11:59:52 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 11:59:52 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 11:11:12 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 11:11:11 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:54:52 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:54:52 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:53:13 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:53:13 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:46:11 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:46:10 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:43:35 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:43:35 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:41:22 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:41:22 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:37:53 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:37:52 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:36:45 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:36:44 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:35:28 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:35:27 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:34:19 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:34:18 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:34:18 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:34:15 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:34:14 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:34:14 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:24:31 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:24:30 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:22:28 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:22:27 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:20:33 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:20:32 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:14:29 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:14:29 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:12:05 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:12:04 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:10:26 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:10:25 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:07:24 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:07:23 4-Error IGMP: ERROR - Group address 0.0.0.1 is not a legal multicast
2007-10-21 10:07:18 7-Information PROG: SW upgrade Failed in gradual download
2007-10-21 10:07:18 4-Error E104.0 SW Upgrade Failed Before Download - Server not Present
2007-10-21 10:07:18 5-Warning TFTP: Driver Open Error: received MSG_ERR from s2c queue.
2007-10-21 10:07:18 5-Warning TFTP: Driver Error select TFTP_TMOUT.
2007-10-21 10:05:28 7-Information SNMP: Working in SNMP V1/2c Only NmAccess mode
2007-10-21 10:05:26 7-Information INITIALIZATION COMPLETE - MODEM IS OPERATIONAL
2007-10-21 10:05:26 6-Notice E102.0 SW Download INIT - Via Config file
Event Log has reached maximum size. Older log entries are lost.
thomasgb
Kabelneuling
 
Beiträge: 3
Registriert: 21.10.2007, 13:46

Re: Keine IP Adresse via DHCP vom Kabelmodem

Beitragvon mmmm » 21.10.2007, 15:23

leider kann ich dir auch keine lösung nennen. aber auch bei mir treten in letzter zeit schweirigkeiten auf. ich habe so den eindruck, dass der dhcp-server überlastet ist und mir keine ip-zuweisen kann. bei mir tritt folgendes auf: morgens habe ich problemlosen zugang. schalte ich den rechner abends ein, bekomme ich einfach keine ip zugeteilt (über stunden).

eine auskunft der hotlinie war: muss an mir liegen. das modem wird von außen erkannt. ich hätte eine firewall installiert. ich verändere aber nichts an der konfiguration und morgens geht es problemlos und abends eben nicht. ?????????

nähere daten:
wohnort roßdorf bei darmstadt
SB5101E Modem
di-524 wireless lan router
desktop rechner windows 2000 mit kabelverbindung
laptop mit xp und wirlessverbindung

gruss
mmmm
mmmm
Kabelneuling
 
Beiträge: 25
Registriert: 18.10.2007, 08:04

Re: Keine IP Adresse via DHCP vom Kabelmodem

Beitragvon thomasgb » 21.10.2007, 15:49

Puh, wenn das die Erklärung ist hätte ich ein Problem damit, denn damit könnte ich nicht gut leben!

Merkwürdigerweise habe ich übrigens gerade eben (vor ein paar Minuten) eine IP Adresse zugewiesen bekommen, d.h. gerade eben läuft es - zufällig mal - gute Frage wie lange noch bzw. ob es beim nächsten Start des Rechners wieder geht oder nicht.

Mein Standarort: Darmstadt
thomasgb
Kabelneuling
 
Beiträge: 3
Registriert: 21.10.2007, 13:46

Re: Keine IP Adresse via DHCP vom Kabelmodem

Beitragvon EvoX » 21.10.2007, 20:09

Hallo

Habe genau das selbe Problem.
Bis ich morgens eine Ip zugewiesenbekomme kann es schon mal 30 min. dauern.
Dananch keine Probelme mehr.
Kann auch nicht an der Firewall oder anderem liegen da ich die nur am Rechner rechner habe jedoch nicht auf dem modem.
Auf das hat man ja eh nur begretzt zugriff.
Wohne in Dreieich also ganz in der nähe....
Könnte ja auch ein Lokales Problem Frankfurt und umgebung sein.....
Unitymedia 3 Play 16000
Motorolla SBV5121E
Digital TV Plus
TT Micro C-254
EvoX
Kabelneuling
 
Beiträge: 26
Registriert: 16.07.2007, 16:11

...und nun....

Beitragvon mmmm » 21.10.2007, 20:24

.... scheint ja tatsächlich ein problem im rhein-main-raum zu sein.

nur: was soll man jetzt tun? die hotlinie von unitymedia ist ja ein kathastrophe und auf fax und e-mail reagieren die ja auch nicht.

ich bin ratlos. und nun denken wir auch noch daran, das fernsehen von analog auf digital umzustellen. ob wir das sollen?
mmmm
Kabelneuling
 
Beiträge: 25
Registriert: 18.10.2007, 08:04

Re: Keine IP Adresse via DHCP vom Kabelmodem

Beitragvon Jolander » 21.10.2007, 20:34

thomasgb hat geschrieben:Modem-Daten:
Model Name: SBV5121E
Firmware Version: 2.17.1.2
Firmware Build Time: Jul 27 2006 18:37:16

Modem-Logfile:

2007-10-21 12:24:08 4-Error E104.0 SW Upgrade Failed Before Download - Server not Present
2007-10-21 12:24:08 5-Warning TFTP: Driver Open Error: received MSG_ERR from s2c queue.
2007-10-21 12:24:08 5-Warning TFTP: Driver Error select TFTP_TMOUT.

Bei Dir wird versucht eine neue Firmware zu installieren, aber der Server scheint ein Problem zu haben...wie wohl öfter. Wenn die Firmware erstmal richtig installiert ist, sollten die Probleme behoben sein. Gibt auch eine Suchfunktion hier, die z.B. den hier gebracht hätte
viewtopic.php?f=53&t=1682

Ob es bei den anderen Usern auch daran liegt...keine Ahnung :smile: Mal ins Log schauen, ob da was mit TFTP-Error auftaucht.
Ab Januar 2011 Netcologne auch in Düsseldorf. Schau' mer mal.

"Du hast zwar recht, aber ich finde meine Meinung besser"
Jolander
Übergeordneter Verstärkerpunkt
 
Beiträge: 769
Registriert: 07.06.2007, 06:04
Wohnort: Düsseldorf-Gerresheim

Re: Keine IP Adresse via DHCP vom Kabelmodem

Beitragvon mmmm » 22.10.2007, 08:03

klingt vielleicht etwas doff, aber wie kann ich denn den logfile des modems auslesen?

wenn bei mir auch versucht wird ständig eine neue firmeware draufzuspielen und das nicht klappt, dann sollte man da mal nachhelfen, oder?
kann ich da selbst was machen?

gruß
mmmm
mmmm
Kabelneuling
 
Beiträge: 25
Registriert: 18.10.2007, 08:04

Re: Keine IP Adresse via DHCP vom Kabelmodem

Beitragvon wolle08 » 22.10.2007, 08:47

Du gibt im Browser die Adresse http://192.168.100.1 ein.
Als Username admin, als Passwort motorola. Dann den Reiter Logs anklicken und Du kannst die Log-Datei einsehen.
Meines Wissens kannst Du in Sachen Firmware-Update nichts selbst machen, sondern bist auf UM angewiesen.
Schöne Grüße von Wolfgang
wolle08
Kabelneuling
 
Beiträge: 30
Registriert: 25.10.2006, 17:53
Wohnort: Olpe

Re: Keine IP Adresse via DHCP vom Kabelmodem

Beitragvon gemini » 22.10.2007, 11:39

Hallo,

ach das erleichtert mich jetzt doch enorm, dass ich nicht der einzige bin :smile:

Am Samstag ging garnichts, ich hab fast 5 Std. mit dem Mist gekämpft und auch ewig in der Warteschlange zugebracht. Sonntag morgen alles funktioniert wieder bestens. Sonntag abend das gleiche Spiel wieder. Eben hat der Techniker angerufen, ich wär jetzt der 43.ste Kunde mit dem er telefoniert, "sie arbeiten daran".

Übrigens ich wohne in Darmstadt-Arheilgen.
UM 2play SMART
gemini
erfahrener Kabelkunde
 
Beiträge: 75
Registriert: 31.05.2007, 16:31
Wohnort: 64291 Darmstadt

Re: Keine IP Adresse via DHCP vom Kabelmodem

Beitragvon mmmm » 22.10.2007, 19:51

das ist der logfile meines modems.
kann da jemand etwas rauslesen????

gruß
mmmm

p.s. leider konnte ich es nicht nach datum ordnen


1970-01-01 00:00:12 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:02:46 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:32 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
1970-01-01 00:02:32 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:55 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
1970-01-01 00:00:22 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:13 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:00:13 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-10-15 18:43:04 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-10-15 18:43:03 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-10-15 18:43:03 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-09-06 14:42:44 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-09-06 14:42:10 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-09-06 14:41:38 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-08-18 20:20:15 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-08-18 20:20:08 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-08-18 20:19:36 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:16 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-08-02 14:58:34 3-Critical D001.0 DHCP FAILED - Discover sent, no offer received
2007-08-02 14:58:28 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-08-02 14:58:24 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-08-02 14:58:18 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-08-02 14:57:45 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-08-02 14:16:46 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-08-02 14:16:40 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-08-02 14:16:14 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2007-08-02 14:16:14 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-08-02 14:15:27 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2007-08-02 14:15:27 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-08-02 14:14:45 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2007-08-02 14:14:45 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-08-02 14:14:05 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2007-08-02 14:14:05 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-08-02 14:12:22 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-08-02 14:11:50 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:07 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:09 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:22 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:09 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:09 3-Critical R002.0 No Ranging Response received - T3 time-out
1970-01-01 00:00:11 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-05-21 15:33:49 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-05-21 15:33:32 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-05-21 15:32:32 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2007-05-21 15:32:32 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-05-21 15:31:29 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-21 15:31:18 3-Critical U001.0 No UCD's Received - Timeout
2007-05-21 15:30:57 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-21 15:30:56 3-Critical U001.0 No UCD's Received - Timeout
2007-05-21 15:30:46 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-21 15:30:45 3-Critical U001.0 No UCD's Received - Timeout
2007-05-21 15:30:35 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-21 15:30:33 3-Critical U001.0 No UCD's Received - Timeout
2007-05-21 15:29:30 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-21 15:29:29 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-05-21 15:29:29 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-21 15:29:26 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-05-21 15:29:25 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-21 15:29:22 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-05-21 15:29:22 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-21 15:29:13 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-05-21 15:29:13 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-21 15:29:10 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2007-05-21 15:29:10 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-05-21 15:28:00 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2007-05-21 15:28:00 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-05-21 15:27:05 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2007-05-21 15:27:05 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-05-21 15:26:01 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-05-21 15:25:28 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
2007-05-21 15:25:12 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-05-21 15:24:08 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-05-21 15:23:36 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-05-09 14:39:21 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-05-09 14:39:16 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-09 14:39:01 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-05-09 14:37:46 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-05-09 14:37:27 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-05-09 13:38:54 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-05-09 13:38:53 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
2007-05-09 13:38:53 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-05-09 11:51:47 3-Critical R005.0 Started Unicast Maintenance Ranging - No Response received - T3 time-out
1970-01-01 00:00:14 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:18 3-Critical D002.0 DHCP FAILED - Request sent, No response
1970-01-01 00:00:15 3-Critical D003.0 DHCP WARNING - Non-critical field invalid in response.
2007-02-05 12:18:24 3-Critical R003.0 Init RANGING Critical Ranging Request Retries exhausted
2007-02-05 12:18:24 3-Critical R002.0 No Ranging Response received - T3 time-out
2007-02-05 12:17:41 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-02-05 12:17:17 3-Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2007-02-05 12:11:04 3-Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2007-02-05 12:11:03 3-Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
mmmm
Kabelneuling
 
Beiträge: 25
Registriert: 18.10.2007, 08:04

Nächste

Zurück zu Internet und Telefon über das TV-Kabelnetz

Wer ist online?

Mitglieder in diesem Forum: 0 Mitglieder und 71 Gäste