Thor. Skrevet 5. mars 2011 Del Skrevet 5. mars 2011 Har store problemer med nettet, det har jeg hatt i hele dag uten å finne noen fornuftig forklaring. Symptomer: Høy ping på Vood boksen (500ms og mer). Akkurat nå er det to maskiner på nettverket, den ene har ingen programmer åpne som tilsier å bruke mye nett. Den andre er den jeg sitter på, jeg har avsluttet µTorrent, Steam, skype og lignende uten at det ble bedre. Vood boksen (modemet) har blitt restartet flere ganger idag uten at det hjelper. Nettverket ser slik ut: telefonlinje->vood boks(192.168.1.1)->Dlink(192.168.0.1)->pc 50 ping til 192.168.1.1: Pinging 192.168.1.1 with 32 bytes of data: Reply from 192.168.1.1: bytes=32 time=382ms TTL=254 Reply from 192.168.1.1: bytes=32 time=402ms TTL=254 Reply from 192.168.1.1: bytes=32 time=441ms TTL=254 Reply from 192.168.1.1: bytes=32 time=471ms TTL=254 Reply from 192.168.1.1: bytes=32 time=515ms TTL=254 Reply from 192.168.1.1: bytes=32 time=533ms TTL=254 Reply from 192.168.1.1: bytes=32 time=239ms TTL=254 Reply from 192.168.1.1: bytes=32 time=231ms TTL=254 Reply from 192.168.1.1: bytes=32 time=275ms TTL=254 Reply from 192.168.1.1: bytes=32 time=334ms TTL=254 Reply from 192.168.1.1: bytes=32 time=381ms TTL=254 Reply from 192.168.1.1: bytes=32 time=406ms TTL=254 Reply from 192.168.1.1: bytes=32 time=456ms TTL=254 Reply from 192.168.1.1: bytes=32 time=472ms TTL=254 Reply from 192.168.1.1: bytes=32 time=490ms TTL=254 Reply from 192.168.1.1: bytes=32 time=540ms TTL=254 Reply from 192.168.1.1: bytes=32 time=573ms TTL=254 Reply from 192.168.1.1: bytes=32 time=585ms TTL=254 Reply from 192.168.1.1: bytes=32 time=593ms TTL=254 Reply from 192.168.1.1: bytes=32 time=671ms TTL=254 Reply from 192.168.1.1: bytes=32 time=667ms TTL=254 Reply from 192.168.1.1: bytes=32 time=684ms TTL=254 Reply from 192.168.1.1: bytes=32 time=713ms TTL=254 Reply from 192.168.1.1: bytes=32 time=742ms TTL=254 Reply from 192.168.1.1: bytes=32 time=763ms TTL=254 Reply from 192.168.1.1: bytes=32 time=743ms TTL=254 Reply from 192.168.1.1: bytes=32 time=785ms TTL=254 Reply from 192.168.1.1: bytes=32 time=827ms TTL=254 Reply from 192.168.1.1: bytes=32 time=849ms TTL=254 Reply from 192.168.1.1: bytes=32 time=876ms TTL=254 Reply from 192.168.1.1: bytes=32 time=628ms TTL=254 Reply from 192.168.1.1: bytes=32 time=428ms TTL=254 Reply from 192.168.1.1: bytes=32 time=463ms TTL=254 Reply from 192.168.1.1: bytes=32 time=532ms TTL=254 Reply from 192.168.1.1: bytes=32 time=561ms TTL=254 Reply from 192.168.1.1: bytes=32 time=564ms TTL=254 Reply from 192.168.1.1: bytes=32 time=2ms TTL=254 Reply from 192.168.1.1: bytes=32 time=2ms TTL=254 Reply from 192.168.1.1: bytes=32 time=13ms TTL=254 Reply from 192.168.1.1: bytes=32 time=2ms TTL=254 Reply from 192.168.1.1: bytes=32 time=2ms TTL=254 Reply from 192.168.1.1: bytes=32 time=472ms TTL=254 Reply from 192.168.1.1: bytes=32 time=517ms TTL=254 Reply from 192.168.1.1: bytes=32 time=601ms TTL=254 Reply from 192.168.1.1: bytes=32 time=634ms TTL=254 Reply from 192.168.1.1: bytes=32 time=794ms TTL=254 Reply from 192.168.1.1: bytes=32 time=681ms TTL=254 Reply from 192.168.1.1: bytes=32 time=437ms TTL=254 Reply from 192.168.1.1: bytes=32 time=496ms TTL=254 Reply from 192.168.1.1: bytes=32 time=544ms TTL=254 Ping statistics for 192.168.1.1: Packets: Sent = 50, Received = 50, Lost = 0 (0% loss), 50 ping til 192.168.0.1: Pinging 192.168.0.1 with 32 bytes of data: Reply from 192.168.0.1: bytes=32 time=14ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=21ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=5ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=3ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=8ms TTL=64 Reply from 192.168.0.1: bytes=32 time=22ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=9ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=2ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Reply from 192.168.0.1: bytes=32 time=1ms TTL=64 Ping statistics for 192.168.0.1: Packets: Sent = 50, Received = 50, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1ms, Maximum = 22ms, Average = 2ms Fant noe som ble kalt for modem test inne på Vood, her ble resultatene følgende uten at jeg skjønner noe av det: Dette er forhåpentlig nok informasjon, håper noen kloke hoder har en forklaring og en løsning på hva det er som skjer. Lenke til kommentar
Anbefalte innlegg
Opprett en konto eller logg inn for å kommentere
Du må være et medlem for å kunne skrive en kommentar
Opprett konto
Det er enkelt å melde seg inn for å starte en ny konto!
Start en kontoLogg inn
Har du allerede en konto? Logg inn her.
Logg inn nå