Ripperingo
join:2004-09-02
Champaign, IL
| reply to Meeble
Re: Champaign - 8/17 packet loss ?
hmm, well, my outage was caused by an overheated network card (it's about to die i guess). I switched lines on my nic's and it works again. However, i had to register the new nic with insight to get on line, and speeds are absolutely in the crapper now (like 33k6 modem-style bad) :( Latency was never better though, strangely enough.
C:\ping 66.165.113.2 -n 15
Pinging 66.165.113.2 with 32 bytes of data:
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=17ms TTL=119
Reply from 66.165.113.2: bytes=32 time=17ms TTL=119
Reply from 66.165.113.2: bytes=32 time=17ms TTL=119
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=18ms TTL=119
Reply from 66.165.113.2: bytes=32 time=20ms TTL=119
Reply from 66.165.113.2: bytes=32 time=19ms TTL=119
Reply from 66.165.113.2: bytes=32 time=17ms TTL=119
Ping statistics for 66.165.113.2:
Packets: Sent = 15, Received = 15, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 20ms, Average = 18ms |
