Previous 1 3 4 5 6 7 Next 966 Replies Latest reply: Sep 15, 2014 6:52 AM by miroslavfromprague 9 Go to original post
  • toabi Level 1 Level 1 (0 points)
    I found out a funny thing. Don't know if it this normal but:

    Ping times are jumping around like crazy. If signal is weak there are timeouts and ping time goes up to a few seconds.

    time=70.990 ms
    time=197.233 ms
    time=118.374 ms
    time=40.085 ms


    If I open a second Terminal window and there start a

    sudo ping -i 0.2 airport.local

    the ping time is <1ms and the time in the first opened window goes down too!

    In places where the signal is bad this also shows effect. Not to <1ms - but noticeably. I didn't try it long enough to see if the timeouts and connection interruptions are not occuring while constantly pinging the router in short intervals. I'm also no expert in WiFi/Networking so this all could mean nothing.

    I'm just a bit annoyed that my new device has some weird issues.
  • TomB01 Level 1 Level 1 (0 points)
    Yeah, my ping times were all over the planet, too. The Genius (actually was one, I think) verified it easily, getting results like:

    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=3.383 ms
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=3.727 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=3.354 ms
    64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=3.460 ms
    64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=135.359 ms
    Request timeout for icmp_seq 5
    Request timeout for icmp_seq 6
    64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=2223.518 ms
    64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=2680.255 ms
    64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1715.300 ms
    64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=765.192 ms
    64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=485.578 ms

    using the network utility.

    Then plugged in the wired ethernet port and pinged the same router, and got consistent 3.4ms times. Definitely something going on with the wireless card. They are replacing my machine, and it is at the Apple store so should be able to see if the trouble went away this weekend when I have had a chance to pick it up and migrate (again) to it...
  • wantafanta Level 1 Level 1 (0 points)
    PING 192.168.1.254 (192.168.1.254): 56 data bytes
    64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=140.118 ms
    Request timeout for icmp_seq 1
    64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=55.322 ms
    64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=1.118 ms
    64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=138.421 ms
    64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=126.810 ms
    64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=48.469 ms
    64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=140.133 ms
    64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=137.847 ms
    64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=119.606 ms
    Request timeout for icmp_seq 10
    64 bytes from 192.168.1.254: icmp_seq=11 ttl=64 time=140.082 ms
  • TomB01 Level 1 Level 1 (0 points)
    Looks familiar, wantafanta. Do you have the capability to try it with a wired connection to the same router?

    This behavior reduces my network throughput by a factor of 5. My 2009 macbook pro gets about 25 mbps on my FIOS network connection, but my 'new' 2011 got 5mbps or less. Will report back when I am able to test my new system this weekend, but looks like a systemic problem with the new machines (sigh).
  • LaraJones Level 1 Level 1 (0 points)
    Did the update yesterday...Three hours downloadtiime...with several interruptions but it worked...
    BUT no change in the networkbehavoir.
    Would have made my day!!
    Apple, please give us a clou what to do.
  • wantafanta Level 1 Level 1 (0 points)
    Same router as above, over ethernet cable. I think I'm going to take it in for a refund on saturday, and get another at a later date.

    PPING 192.168.1.254 (192.168.1.254): 56 data bytes
    64 bytes from 192.168.1.254: icmp_seq=0 ttl=64 time=0.799 ms
    64 bytes from 192.168.1.254: icmp_seq=1 ttl=64 time=0.664 ms
    64 bytes from 192.168.1.254: icmp_seq=2 ttl=64 time=0.509 ms
    64 bytes from 192.168.1.254: icmp_seq=3 ttl=64 time=0.689 ms
    64 bytes from 192.168.1.254: icmp_seq=4 ttl=64 time=0.565 ms
    64 bytes from 192.168.1.254: icmp_seq=5 ttl=64 time=0.657 ms
    64 bytes from 192.168.1.254: icmp_seq=6 ttl=64 time=0.548 ms
    64 bytes from 192.168.1.254: icmp_seq=7 ttl=64 time=0.503 ms
    64 bytes from 192.168.1.254: icmp_seq=8 ttl=64 time=0.485 ms
    64 bytes from 192.168.1.254: icmp_seq=9 ttl=64 time=0.775 ms
  • wonslung Level 1 Level 1 (0 points)
    hrm, my wifi is working fine. I wonder if some of the macs have a batch of bad chips. This thread isn't nearly as huge as the "2011 15/17 freeze" thread....Did anyone get a replacement laptop to check this issue?
  • yozhbk Level 1 Level 1 (0 points)
    I replaced my about a week or so ago and the issue is the same, the thing is I replaced at the same store I bought about 10 days later, so could be from the same batch..... I dont know if replacing again would do the trick.

    @wonslung when you are saying working fine, did you try the ping times ? Did you try transfering larger files ?

    Which Band are you on A/B/G/N ? 2.4 or 5GHz ? What speed are you connected on ?

    Message was edited by: yozhbk
  • toabi Level 1 Level 1 (0 points)
    I have a replacement here which has the same problem as the first one.

    Annoying. Don't know what to do…
  • wonslung Level 1 Level 1 (0 points)
    I'm connecting as n but i've also connected as g

    I've connected 2.4 and 5ghz

    I'm connecting wpa2

    my ping times are find, here's an example:


    PING 192.168.1.1 (192.168.1.1): 56 data bytes
    64 bytes from 192.168.1.1: icmp_seq=0 ttl=64 time=1.587 ms
    64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=1.244 ms
    64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=1.221 ms
    64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=0.963 ms
    64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=0.862 ms
    64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=0.778 ms
    64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=0.699 ms
    64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=1.557 ms
    64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=4.455 ms
    64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=2.651 ms
    64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=1.059 ms
    64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=0.955 ms
    64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=0.859 ms
    64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=0.716 ms
    64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=0.636 ms
    64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=1.620 ms
    64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=1.195 ms
    64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=1.144 ms


    Large transfers seem fine.

    Message was edited by: wonslung
  • camcole Level 1 Level 1 (0 points)
    Have a new 13" MBP that performs beautifully wirelessly with Siemens Gigaset router, fabulous speed ... for about 10 minutes, and then drops the signal.
    After five, 10 minutes, signal comes back. Its not the ISP, because other laptops do not drop the signal from the same location.
  • Btotheoomer Level 1 Level 1 (0 points)
    I'm glad to see I'm not alone. Hopefully an extra case will get apple to take a look at the issue. My Macbook worked fine for the first week, but now my Wifi signal will drop out intermittentely, prompting me to restart airport and try again.
  • wonslung Level 1 Level 1 (0 points)
    So is this an issue which is affecting specific types of routers? I have no problem with my old g router, and i recently bought an airport extreme base station which works fine for me as well in 2.4 Ghz n and 5 Ghz n

    I'd wonder if this is a really small issue...also, what locale are people in? I know that different locales use different "channels"

    I'm in the US.
  • TomB01 Level 1 Level 1 (0 points)
    Sigh, just got the replacement machine they gave me because of the network irregularity. Unfortunately, it is no better. So, will call Applecare and get it registered as an issue, and see what they say...
  • iGas2 Level 1 Level 1 (0 points)
    Spare a thought for this mac newbie who thought he was entering the 21st century with the purchase of a shiny new macbook pro!! Two days have been spent trying to achieve the impossible - simply networking a machine! Something my PCs have been doing seamlessly for years.

    Hold out for a fix if you wish. I'm off to my Apple retailer for a refund!
Previous 1 3 4 5 6 7 Next