1. Welkom op het onafhankelijke Ziggo Gebruikersforum. Een forum voor en door gebruikers van Ziggo.
    Registreer je gratis om direct zelf berichten te plaatsen en gebruik te maken van extra functies!
    Verberg deze melding

DHCP?

Discussie in 'Internet - Algemeen' gestart door maia, 1 nov 2008.

Niet open voor verdere reacties.
  1. Ik heb een hele berg vage meldingen in mijn modem log staan waarvan Ziggo niets ziet.. dus werk mijn modem prima volgens hun hoewel ik daar zo mijn twijfels bij heb.. mijn internet val om de zoveel tijd even weg..

    Ik krijg timeouts in mijn ping en soms paar keer achter elkaar met daartussen ook doelhost niet gevonden.. woensdag komt iemand van multikable langs maar ze zeiden dat het risico best groot was dat het aan mij lag en dus moest betalen ... dus heb ik gisteren een nieuwe kabel gekocht die verbonden en ik hield dezelfde problemen toen een nieuwe netwerk kaart gekocht maar ook daarmee hield ik dezelfde problemen modem meerdere malen gereset.. pc helemaal uitgepluist op virussen dus ik betwijfel echt dat het aan mij ligt maar ik wil toch echt alle opties nalopen voor ziggo langskomt...

    kan iemand me misschien uitleggen wat de meldingen in mijn modem inhouden en waarom ziggo zegt dat er niets aan de hand is? en eventueel hoe ik het kan maken.

    Alvast bedankt

    hieronder mijn modem logs:

    2008-10-31 14:47:516-NoticeI401.0TLV-11 - unrecognized OID1970-01-01 00:00:133-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.2008-10-28 13:09:225-WarningD103.0DHCP RENEW WARNING - Field invalid in response2008-10-25 01:09:266-NoticeI401.0TLV-11 - unrecognized OID2008-10-25 01:09:163-CriticalD003.0DHCP WARNING - Non-critical field invalid in response.2008-10-25 01:09:113-CriticalD001.0DHCP FAILED - Discover sent, no offer received2008-10-25 01:08:053-CriticalR002.0No Ranging Response received - T3 time-out2008-10-25 01:07:473-CriticalT005.0SYNC Timing Synchronization failure - Loss of Sync2008-10-25 01:07:373-CriticalD001.0DHCP FAILED - Discover sent, no offer received2008-10-25 01:07:013-CriticalR002.0No Ranging Response received - T3 time-out2008-10-25 01:06:533-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:533-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:523-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:523-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:513-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:503-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:493-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:473-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:473-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:463-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:463-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:453-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:453-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:443-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:443-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:433-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:433-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:433-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:423-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:423-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:413-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:393-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:383-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:383-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:383-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:373-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:373-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:363-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:363-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:353-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:353-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:313-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:303-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:303-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:06:293-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:233-CriticalR004.0Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 timeout2008-10-25 01:06:233-CriticalT001.0SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing2008-10-25 01:06:213-CriticalT002.0SYNC Timing Synchronization failure - Failed to acquire FEC framing2008-10-25 01:05:593-CriticalT005.0SYNC Timing Synchronization failure - Loss of Sync
     
  2. had precies dezelfde melding, ook last van lage snelheden en wegvallende verbinding..

    bij mij hebben ze het up en downstream signaal hier in de straat aangepast.. nadien is die melding weg, wat ook geld voor de wegvallende verbinding.. toch helaas nog last van lage snelheid, heel af en toe loopt het goed..
     
Niet open voor verdere reacties.

Deel Deze Pagina