internet slipt dicht na ongeveer 24 uur dl met bittorrent ??

Status
Niet open voor verdere reacties.
G

Gijs

hallo mensen.. nieuw lid met een vraag ;D

Als ik een nachtje en een dag dl met bittorrent (heb meerdere gehad die het primma deden voor de nieuwe snelheid) dan slipt het intenet helemaal dicht en kan ik de hele avond niet internetten. ook modem router resets of instellingen veranderen helpt niet voor zover ik weet. Waar kan dit aan liggen en hebben meer gebruikers hier last van?

Ik heb na zo'n 60 a 70 euro bellen naar de :-X helpdesk eindelijk een ander moden gekregen.. maar ook die heeft dat soor kuuren (hie doet het verder wel al een stuk beter dan met die gare com21)
 
T

tweaker

kan je dan ook niet meer internetten met een andere pc op het zelfde netwerk?
 
L

lowlands

heb ik ook gehad, heb toen het aantal connecties omlaag geschroefd tot dat het wel bleef werken. schijnt te maken te hebben met je eigen netwerkkaart of de nic in je modem die het aantal connecties niet meer aankunnen.
 
K

killing attack

Dabuzz zei:
hallo mensen.. nieuw lid met een vraag  ;D

Als ik een nachtje en een dag dl met bittorrent (heb meerdere gehad die het primma deden voor de nieuwe snelheid) dan slipt het intenet helemaal dicht en kan ik de hele avond niet internetten. ook modem router resets of instellingen veranderen helpt niet voor zover ik weet. Waar kan dit aan liggen en hebben meer gebruikers hier last van?

Ik heb na zo'n 60 a 70 euro bellen naar de  :-X helpdesk eindelijk een ander moden gekregen.. maar ook die heeft dat soor kuuren (hie doet het verder wel al een stuk beter dan met die gare com21)

SP 2 geinstalleerd pas geleden toevallig ?
 
Topicstarter
Topicstarter
G

Gijs

ineens herriner ik me dat om ongeveer 20:00 1 minuut (minimaal) nodig om een pagina te openen en nu is het 23:16 en begint het beetje bij beetje weer normaal te worden en dat gebeurt dus al (op 1 dag na) sins ik het nieuwe modem heb. ??? En die log is ook heel erug vaag als je het mij vraagt.

Code:
1970-01-01 00:00:11 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
1970-01-01 00:00:06 3-Critical 0x04E33948 No Ranging Response received - T3 time-out 
1970-01-01 00:00:12 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
2004-10-16 20:27:16 3-Critical 0x0459E508 REG RSP not received 
1970-01-01 00:00:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
2004-10-16 18:49:30 3-Critical 0x0459E508 REG RSP not received 
1970-01-01 00:02:24 4-Error 0x040D9A93 ToD request sent- No Response received 
1970-01-01 00:02:17 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
1970-01-01 00:02:16 3-Critical 0x040D99C8 DHCP FAILED - Request sent, No response 
1970-01-01 00:00:10 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
1970-01-01 00:00:17 4-Error 0x040D9A93 ToD request sent- No Response received 
1970-01-01 00:00:15 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
1970-01-01 00:00:04 3-Critical 0x04E33948 No Ranging Response received - T3 time-out 
2004-10-15 20:30:24 3-Critical 0x0459E508 REG RSP not received 
1970-01-01 00:00:11 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
1970-01-01 00:00:05 3-Critical 0x04E33948 No Ranging Response received - T3 time-out 
2004-10-15 20:17:08 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 
1970-01-01 00:00:11 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
1970-01-01 00:00:12 3-Critical 0x040D9964 DHCP FAILED - Discover sent, no offer received 
2004-10-13 18:23:28 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 
1970-01-01 00:00:14 4-Error 0x040D9A93 ToD request sent- No Response received 
1970-01-01 00:00:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
1970-01-01 00:00:05 3-Critical 0x04E33948 No Ranging Response received - T3 time-out 
1970-01-01 00:00:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
1970-01-01 00:00:11 3-Critical 0x04E33948 No Ranging Response received - T3 time-out 
1970-01-01 00:01:40 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:37 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:33 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:25 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:23 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:13 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:12 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:06 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:05 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:05 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:04 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:01:01 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:01:00 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:59 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:58 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:57 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:53 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:53 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:52 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:51 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:51 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:50 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:50 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:46 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:44 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:40 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:39 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:38 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:33 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:33 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:32 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:32 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:31 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:31 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:29 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:29 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:28 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:28 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:23 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing 
1970-01-01 00:00:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing 
1970-01-01 00:00:19 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
 
S

sander V

Ben je niet teruggezet in snelheid? Ik heb die meldingen ook nl. in mijn surfboard. Kweetni..

Heb je meer dan 40 gig gedownload?
 

Johnny54

Moderator
Berichten
19.200
Internet
  1. Ziggo
Digitale TV
  1. Ziggo
Zo ziet mijn logfile van de 5100E (zie onder) er ook ongeveer uit.
Ik vond het ook vreemd en heb het aan de helpdesk gevraagd, maar die vonden het normaal.
Code:
2004-10-16 18:45:58 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 
2004-10-16 04:53:17 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response 
2004-10-14 11:23:30 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 
2004-10-12 16:53:16 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response 
2004-10-11 18:16:43 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 
2004-10-09 04:53:17 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response 
2004-10-09 00:23:59 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 
1970-01-01 00:00:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response. 
2004-10-05 12:34:34 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 
2004-10-04 01:00:16 5-Warning 0x040DC13C DHCP RENEW WARNING - Field invalid in response 
2004-10-03 16:50:53 3-Critical 0x04E33A74 Started Unicast Maintenance Ranging - No Response received - T3 time-out 
1970-01-01 00:00:12 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
 
Topicstarter
Topicstarter
G

Gijs

sander V zei:
Ben je niet teruggezet in snelheid? Ik heb die meldingen ook nl. in mijn surfboard. Kweetni..

Heb je meer dan 40 gig gedownload?

uh nee dat heb ik niet .. en ik heb ook geen mail gehad. En de volgende ochtend is de snelheid weer volle bak.

Uw data verbruik
    error   
   
  1131 , Sun Oct 17 10:44:16 2004 
  Voor deze gebruikersnaam is er op dit moment nog geen dataverbruik gemeten. 
 
Status
Niet open voor verdere reacties.
Bovenaan