Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

theahnman

macrumors member
Original poster
Here is the output from my pingtest via Network Utility...
Is anyone else having the same issues?


PING 192.168.1.1 (192.168.1.1): 56 data bytes
Request timeout for icmp_seq 0
64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1473.547 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=474.457 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=0.735 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.762 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=2.799 ms
Request timeout for icmp_seq 6
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=2530.812 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=1531.551 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=531.861 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=0.738 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=0.769 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=0.743 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=2586.053 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=1587.668 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=587.912 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=0.741 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=0.738 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=0.746 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=2627.496 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=1629.225 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=630.138 ms

--- 192.168.1.1 ping statistics ---
20 packets transmitted, 20 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.735/809.975/2627.496/943.875 ms

Pingtest.net will typically give me an "F" rating and indicate that almost 30% of my 200 packets sent didn't make the trip back.

Any thoughts?
On a related side note, there will be a memorial service for all packets lost in the aether of the Intertubes in the near future...
 
What are your results when using a wire? That's pretty important in identifying what might be the problem. 🙂
 
Well, there is no problem with the wire. I more or less wanted to see if there was a similar issue with other people, and if they had figured out a solution to the problem. In addition, I want to get some sense of whether this is a small problem in contrast to the greater pool of 21.5" iMac ALs. I'm hoping it's a simple hardware issue. I really hope it is not a software issue... because we ALL know how Apple is when it comes to marginal software issues... 🙁
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.