Ständige Disconnects

In diesem Forum geht es um alle Störungen im Kabelnetz von Unitymedia, egal ob analoges TV und Radio, digitales TV und Radio, Internet oder Telefonie.
Forumsregeln
  • 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.
Antworten
leipos
Kabelneuling
Beiträge: 3
Registriert: 05.09.2011, 14:57

Ständige Disconnects

Beitrag von leipos » 05.09.2011, 15:09

Hi,

unsere Internet bzw Telefonverbindung bricht in unregelmässigen Abständen, ca 5mal pro Tag, weg. Kurzfristige Abhilfe bringt ein Powerrestart des Ciscos + Ab- und Dranschrauben des Singnalkabels, nur Schrauben oder nur Restart alleine bringt nix! Mittlerweile waren die UM- Techniker 2mal hier und haben jeweils das Modem, sowie den Verstärker im Keller ausgetauscht. Keine Besserung! Das TV Bild ist überigens nicht betroffen.

Sind für jeden Ratschlag dankbar.

Werte des Cisco EPC3212:

Downstream Channels

Channel 1:
Channel ID: 130
Downstream Frequency: 626000000 Hz
Modulation: 256 QAM
Power Level: -0.2 dBmV
Signal to Noise Ratio: 37.5 dB
Channel 2:
Channel ID: 129
Downstream Frequency: 618000000 Hz
Modulation: 256 QAM
Power Level: 0.6 dBmV
Signal to Noise Ratio: 37.6 dB
Channel 3:
Channel ID: 131
Downstream Frequency: 634000000 Hz
Modulation: 256 QAM
Power Level: 0.3 dBmV
Signal to Noise Ratio: 37.5 dB
Channel 4:
Channel ID: 132
Downstream Frequency: 642000000 Hz
Modulation: 256 QAM
Power Level: 0.3 dBmV
Signal to Noise Ratio: 37.5 dB
Channel 5:
Channel ID: Not used
Downstream Frequency: 0
Modulation: unknown
Power Level: 0.0 dBmv
Signal to Noise Ratio: 0.0 dBmv
Channel 6:
Channel ID: Not used
Downstream Frequency: 0
Modulation: unknown
Power Level: 0.0 dBmv
Signal to Noise Ratio: 0.0 dBmv
Channel 7:
Channel ID: Not used
Downstream Frequency: 0
Modulation: unknown
Power Level: 0.0 dBmv
Signal to Noise Ratio: 0.0 dBmv
Channel 8:
Channel ID: Not used
Downstream Frequency: 0
Modulation: unknown
Power Level: 0.0 dBmv
Signal to Noise Ratio: 0.0 dBmv
Cisco Logo

Upstream Channels

Channel1:
Channel ID: 1
Upstream Frequency: 36960000 Hz
Modulation: 64 QAM
Bit Rate: 15360 kBits/sec
Power Level: 47.0 dBmV
Channel 2:
Channel ID: Not used
Upstream Frequency: 0 Hz
Modulation: 0 QAM
Bit Rate: 0 kBits/sec
Power Level: 0.0 dBmV
Channel 3:
Channel ID: Not used
Upstream Frequency: 0 Hz
Modulation: 0 QAM
Bit Rate: 0 kBits/sec
Power Level: 0.0 dBmV
Channel 4:
Channel ID: Not used
Upstream Frequency: 0 Hz
Modulation: 0 QAM
Bit Rate: 0 kBits/sec
Power Level: 0.0 dBmV

addicted
Kabelkopfstation
Beiträge: 3829
Registriert: 15.03.2010, 02:35

Re: Ständige Disconnects

Beitrag von addicted » 06.09.2011, 23:09

Modemlog?

leipos
Kabelneuling
Beiträge: 3
Registriert: 05.09.2011, 14:57

Re: Ständige Disconnects

Beitrag von leipos » 08.09.2011, 10:38

Evt noch zusätzliche Info, ist ein privates Netzwerk mit Desktop/iPhone/Notebook über WLAN + TV über LAN.


Modemlog D-LINK DIR600:

Sep 8 10:24:28 PING-FLOODING flooding attack from WAN (ip:95.114.76.143) detected.
Sep 8 10:24:24 PING-FLOODING flooding attack from WAN (ip:95.114.76.143) detected.
Sep 8 10:24:20 PING-FLOODING flooding attack from WAN (ip:95.114.76.143) detected.
Sep 8 10:22:43 PING-FLOODING flooding attack from WAN (ip:93.134.15.215) detected.
Sep 8 10:22:39 PING-FLOODING flooding attack from WAN (ip:93.134.15.215) detected.
Sep 8 10:22:31 PING-FLOODING flooding attack from WAN (ip:93.134.15.215) detected.
Sep 8 10:21:32 DHCP: Client receive ACK from 80.69.97.200, IP=meine, Lease time=3600.
Sep 8 10:19:59 PING-FLOODING flooding attack from WAN (ip:90.214.226.91) detected.
Sep 8 10:19:51 PING-FLOODING flooding attack from WAN (ip:90.214.226.91) detected.
Sep 8 10:18:33 PING-FLOODING flooding attack from WAN (ip:91.67.48.83) detected.
Sep 8 10:18:26 PING-FLOODING flooding attack from WAN (ip:91.67.48.83) detected.
Sep 8 10:17:48 PING-FLOODING flooding attack from WAN (ip:90.222.30.58) detected.
Sep 8 10:17:45 PING-FLOODING flooding attack from WAN (ip:87.198.113.180) detected.
Sep 8 10:17:41 PING-FLOODING flooding attack from WAN (ip:90.222.30.58) detected.
Sep 8 10:17:03 PING-FLOODING flooding attack from WAN (ip:77.10.87.12) detected.
Sep 8 10:17:03 PING-FLOODING flooding attack from WAN (ip:87.198.113.180) detected.
Sep 8 10:16:53 PING-FLOODING flooding attack from WAN (ip:87.198.113.180) detected.
Sep 8 10:16:01 PING-FLOODING flooding attack from WAN (ip:95.88.106.178) detected.
Sep 8 10:15:56 PING-FLOODING flooding attack from WAN (ip:95.88.106.178) detected.
Sep 8 10:15:52 PING-FLOODING flooding attack from WAN (ip:95.88.106.178) detected.
Sep 8 10:15:33 PING-FLOODING flooding attack from WAN (ip:46.223.73.57) detected.
Sep 8 10:15:26 PING-FLOODING flooding attack from WAN (ip:46.223.73.57) detected.
Sep 8 10:10:32 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine:80) by default rule.
Sep 8 10:10:16 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine) by default rule.
Sep 8 10:10:08 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine:80) by default rule.
Sep 8 10:10:04 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine:80) by default rule.
Sep 8 10:10:02 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine:80) by default rule.
Sep 8 10:10:01 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine:80) by default rule.
Sep 8 10:10:00 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine:80) by default rule.
Sep 8 10:09:59 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine:80)
Sep 8 10:09:58 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine:80) by default rule.
Sep 8 10:09:57 Drop TCP packet from WAN (src:89.182.170.11:52271, dst:meine:80) by default rule.
Sep 8 10:09:18 PING-FLOODING flooding attack from WAN (ip:90.214.226.91) detected.
Sep 8 10:09:13 PING-FLOODING flooding attack from WAN (ip:90.214.226.91) detected.
Sep 8 10:06:56 PING-FLOODING flooding attack from WAN (ip:90.222.30.58) detected.
Sep 8 10:06:51 PING-FLOODING flooding attack from WAN (ip:90.222.30.58) detected.
Sep 8 10:06:48 PING-FLOODING flooding attack from WAN (ip:90.222.30.58) detected.
Sep 8 10:06:30 PING-FLOODING flooding attack from WAN (ip:87.198.113.180) detected.
Sep 8 10:06:18 PING-FLOODING flooding attack from WAN (ip:87.198.113.180) detected.
Sep 8 10:05:46 PING-FLOODING flooding attack from WAN (ip:meine) detected.


edit:

Nachdem alles für 5min vom Strom war (jetzt 11:04)

Sep 8 10:55:24 DHCP: Server sending ACK to 192.168.0.102. (Lease time = 86400)
Sep 8 10:55:24 DHCP: Server receive REQUEST from 54:e6:fc:ac:65:c3.
Sep 8 10:55:24 DHCP: Server sending ACK to 192.168.0.102. (Lease time = 86400)
Sep 8 10:55:24 DHCP: Server receive REQUEST from 54:e6:fc:ac:65:c3.
Sep 8 10:55:24 DHCP: Server sending ACK to 192.168.0.102. (Lease time = 86400)
Sep 8 10:55:24 DHCP: Server receive REQUEST from 54:e6:fc:ac:65:c3.
Sep 8 10:55:24 DHCP: Server sending ACK to 192.168.0.102. (Lease time = 86400)
Sep 8 10:55:24 DHCP: Server receive REQUEST from 54:e6:fc:ac:65:c3.
Sep 8 10:55:24 DHCP: Server sending ACK to 192.168.0.102. (Lease time = 86400)
Sep 8 10:55:24 DHCP: Server receive REQUEST from 54:e6:fc:ac:65:c3.

addicted
Kabelkopfstation
Beiträge: 3829
Registriert: 15.03.2010, 02:35

Re: Ständige Disconnects

Beitrag von addicted » 08.09.2011, 22:54

Das ist nicht das Modemlog, das ist das Log vom Router.

leipos
Kabelneuling
Beiträge: 3
Registriert: 05.09.2011, 14:57

Re: Ständige Disconnects

Beitrag von leipos » 09.09.2011, 06:15

Tschuldigung, sollte dann das sein:

Fri Sep 09 02:57:38 2011 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Thu Sep 08 10:45:47 2011 69010200 Notice (6) SW Download INIT - Via Config file be_diamond_1_epc3212.bin
Thu Sep 08 10:45:39 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...
Wed Sep 07 07:39:52 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...
Tue Sep 06 05:31:33 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...
Mon Sep 05 11:43:10 2011 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Mon Sep 05 10:53:47 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...
Mon Sep 05 04:21:26 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...
Mon Sep 05 03:01:47 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...
Mon Sep 05 01:53:23 2011 2436694064 Critical (3) Booting up the cable modem
Mon Sep 05 01:50:57 2011 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Sep 04 06:21:40 2011 2436694064 Critical (3) Booting up the cable modem
Sat Sep 03 15:50:15 2011 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sat Sep 03 14:46:27 2011 2436694064 Critical (3) Booting up the cable modem
Fri Sep 02 18:05:46 2011 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Sep 02 17:47:35 2011 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...
Fri Sep 02 17:47:18 2011 82000600 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries...
Fri Sep 02 17:47:18 2011 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Sep 02 17:01:10 2011 2436694064 Critical (3) Booting up the cable modem
Fri Sep 02 15:42:32 2011 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Sep 02 14:57:41 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...
Fri Sep 02 14:53:59 2011 82000600 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries...
Fri Sep 02 14:53:59 2011 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Sep 02 14:48:26 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 68000100 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=44:58:2...
Fri Sep 02 14:44:27 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Sep 02 14:04:09 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...
Fri Sep 02 14:02:30 2011 82000600 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries...
Fri Sep 02 14:02:30 2011 82000500 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Fri Sep 02 06:10:15 2011 2436694064 Critical (3) Booting up the cable modem
Time Not Established 82000200 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=44:58:29:bf...

Grothesk
Kabelkopfstation
Beiträge: 4802
Registriert: 13.01.2008, 16:00
Wohnort: Köln-Bayenthal

Re: Ständige Disconnects

Beitrag von Grothesk » 09.09.2011, 08:01

Ein Fall für die Techniker.

Antworten

Wer ist online?

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