vhkim

Q: New Macbook Air - wifi connectivity problems

Hey guys,

 

Hope someone can help?

 

I have a brand new Macbook Air which is able to connect to the internet for just a minute or two before suddenly it drops out. This is even though the signal still shows at full strength and all my other devices are still able to surf the net as per normal.

 

This device is straight out of the box so no 3rd party applications have been installed. I heard that the wifi has been upgraded to 802.11n on this machine, could that be an issue?

 

Do i need to return the machine or is there is a software fix for this problem?

 

Thanks heaps!

 

Vicky

MacBook Air, iOS 6.1.4

Posted on Jun 13, 2013 5:55 AM

Close

Q: New Macbook Air - wifi connectivity problems

  • All replies
  • Helpful answers

first Previous Page 73 of 145 last Next
  • by andyman2,

    andyman2 andyman2 Aug 17, 2013 5:57 AM in response to dogschool
    Level 1 (0 points)
    Aug 17, 2013 5:57 AM in response to dogschool

    Bring up terminal and ping a host, eg. if in uk, maybe type ping google.co.uk

     

    let it run for say 20 lines then press ctrl-c, it'll give you a summary.

     

    The eg. from tpkirkpatrick is a good result.  all pretty consistent.  As an fyi, ping is dependant upon internet connection, wireless etc.  At my house, I get pretty consistent under 20ms responses from google.co.uk.  The air does this but interpolates them with +100ms responses as well, up to 2 seconds....

  • by eric5899,

    eric5899 eric5899 Aug 17, 2013 6:25 AM in response to andyman2
    Level 1 (0 points)
    Aug 17, 2013 6:25 AM in response to andyman2

    Here is another example.  I have an i5/8gb that I ordered the first week they were available in June.  Got it a week later.  One year old ISP provided g band DSL router.

     

    64 bytes from 74.125.225.116: icmp_seq=0 ttl=56 time=55.509 ms

    64 bytes from 74.125.225.116: icmp_seq=1 ttl=56 time=21.713 ms

    64 bytes from 74.125.225.116: icmp_seq=2 ttl=56 time=101.264 ms

    64 bytes from 74.125.225.116: icmp_seq=3 ttl=56 time=125.012 ms

    64 bytes from 74.125.225.116: icmp_seq=4 ttl=56 time=45.681 ms

    64 bytes from 74.125.225.116: icmp_seq=5 ttl=56 time=214.000 ms

    64 bytes from 74.125.225.116: icmp_seq=6 ttl=56 time=194.622 ms

    64 bytes from 74.125.225.116: icmp_seq=7 ttl=56 time=115.328 ms

    64 bytes from 74.125.225.116: icmp_seq=8 ttl=56 time=35.529 ms

    64 bytes from 74.125.225.116: icmp_seq=9 ttl=56 time=24.310 ms

    64 bytes from 74.125.225.116: icmp_seq=10 ttl=56 time=81.896 ms

    64 bytes from 74.125.225.116: icmp_seq=11 ttl=56 time=104.744 ms

    64 bytes from 74.125.225.116: icmp_seq=12 ttl=56 time=226.729 ms

    64 bytes from 74.125.225.116: icmp_seq=13 ttl=56 time=152.014 ms

    64 bytes from 74.125.225.116: icmp_seq=14 ttl=56 time=71.688 ms

    64 bytes from 74.125.225.116: icmp_seq=15 ttl=56 time=94.674 ms

    64 bytes from 74.125.225.116: icmp_seq=16 ttl=56 time=220.451 ms

    64 bytes from 74.125.225.116: icmp_seq=17 ttl=56 time=143.386 ms

    64 bytes from 74.125.225.116: icmp_seq=18 ttl=56 time=61.769 ms

    64 bytes from 74.125.225.116: icmp_seq=19 ttl=56 time=85.156 ms

    64 bytes from 74.125.225.116: icmp_seq=20 ttl=56 time=308.357 ms

    64 bytes from 74.125.225.116: icmp_seq=21 ttl=56 time=130.929 ms

    64 bytes from 74.125.225.116: icmp_seq=22 ttl=56 time=50.612 ms

    64 bytes from 74.125.225.116: icmp_seq=23 ttl=56 time=74.824 ms

    64 bytes from 74.125.225.116: icmp_seq=24 ttl=56 time=201.492 ms

    64 bytes from 74.125.225.116: icmp_seq=25 ttl=56 time=122.732 ms

    64 bytes from 74.125.225.116: icmp_seq=26 ttl=56 time=42.033 ms

    64 bytes from 74.125.225.116: icmp_seq=27 ttl=56 time=64.575 ms

    64 bytes from 74.125.225.116: icmp_seq=28 ttl=56 time=187.021 ms

    64 bytes from 74.125.225.116: icmp_seq=29 ttl=56 time=109.801 ms

     

    I've also noticed something interesting on the activity monitor network tab while downloading files.  It hits 800KB/sec received for a couple of seconds and then drops to 100-150KB/sec for the remaining of the download.  It happened both with an update from the App Store and an app download from Adobe directly.  My standard internet connection is 6Mb/sec tested on my Windows laptop and iPad2.  Then I checked from my new MB Air and it was .32Mb/s with 318ms latency.

  • by andyman2,

    andyman2 andyman2 Aug 17, 2013 6:27 AM in response to eric5899
    Level 1 (0 points)
    Aug 17, 2013 6:27 AM in response to eric5899

    try the ping test on the windows laptop, then you'll get a comparison which should make more sense.  The above looks really erratic, but it depends on what you should normally be expecting in your environment.

  • by dogschool,

    dogschool dogschool Aug 17, 2013 6:57 AM in response to andyman2
    Level 1 (0 points)
    Aug 17, 2013 6:57 AM in response to andyman2

    Here it is

     

    PING google.com (74.125.228.46) 56(84) bytes of data.

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=1 ttl=58 time=1.17 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=2 ttl=58 time=1.20 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=3 ttl=58 time=1.21 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=4 ttl=58 time=1.24 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=5 ttl=58 time=1.19 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=6 ttl=58 time=1.17 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=7 ttl=58 time=1.18 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=8 ttl=58 time=1.19 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=9 ttl=58 time=1.24 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=10 ttl=58 time=1.18 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=11 ttl=58 time=1.26 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=12 ttl=58 time=1.25 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=13 ttl=58 time=1.18 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=14 ttl=58 time=1.21 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=15 ttl=58 time=1.25 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=16 ttl=58 time=1.18 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=17 ttl=58 time=1.20 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=18 ttl=58 time=1.25 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=19 ttl=58 time=1.18 ms

    64 bytes from iad23s06-in-f14.1e100.net (74.125.228.46): icmp_seq=20 ttl=58 time=1.27 ms

     

    --- google.com ping statistics ---

    20 packets transmitted, 20 received, 0% packet loss, time 9500ms

    rtt min/avg/max/mdev = 1.178/1.214/1.270/0.048 ms


  • by M. R.,

    M. R. M. R. Aug 17, 2013 7:18 AM in response to dogschool
    Level 2 (330 points)
    Aug 17, 2013 7:18 AM in response to dogschool

    dogschool wrote:

     

    can you explain how to do the ping test?.

    instead of Terminal, just search in Spotlight: Network Utility (it's in the utility folder) and click on Ping

  • by lunaticitizen,

    lunaticitizen lunaticitizen Aug 17, 2013 7:18 AM in response to dogschool
    Level 1 (0 points)
    Aug 17, 2013 7:18 AM in response to dogschool

    That was a really good result, dogschool. You must live pretty close to a Google data center You can't expect a better result that that. Now if only your MBA could maintain a stable connection...

  • by andyman2,

    andyman2 andyman2 Aug 17, 2013 7:20 AM in response to lunaticitizen
    Level 1 (0 points)
    Aug 17, 2013 7:20 AM in response to lunaticitizen

    What internet connection is that dogschool and is this wireless now wired...!?  Seems incredibly quick.

  • by dogschool,

    dogschool dogschool Aug 17, 2013 7:22 AM in response to andyman2
    Level 1 (0 points)
    Aug 17, 2013 7:22 AM in response to andyman2

    No, its Centurylink wireless thrugh a Zyxel router-I guess Apple can`t blame my ISP`s speed

  • by dogschool,

    dogschool dogschool Aug 17, 2013 7:23 AM in response to dogschool
    Level 1 (0 points)
    Aug 17, 2013 7:23 AM in response to dogschool

    central N.C.

  • by dogschool,

    dogschool dogschool Aug 17, 2013 7:26 AM in response to dogschool
    Level 1 (0 points)
    Aug 17, 2013 7:26 AM in response to dogschool

    110 miles to the Google data center in Lenoir NC

  • by andyman2,

    andyman2 andyman2 Aug 17, 2013 7:32 AM in response to dogschool
    Level 1 (0 points)
    Aug 17, 2013 7:32 AM in response to dogschool

    so is that from your macbook air?  seems a very good connection.  I'm guessing you havent had connection/voip issues...?

  • by dogschool,

    dogschool dogschool Aug 17, 2013 7:40 AM in response to andyman2
    Level 1 (0 points)
    Aug 17, 2013 7:40 AM in response to andyman2

    No-everything but this macbrick air works like its supposed to here...still no fix or admitting there is a problem from apple

  • by andyman2,

    andyman2 andyman2 Aug 17, 2013 7:51 AM in response to dogschool
    Level 1 (0 points)
    Aug 17, 2013 7:51 AM in response to dogschool

    And the result above is from the macbook air? Seems like a brilliant connection from that result only.

  • by dogschool,

    dogschool dogschool Aug 17, 2013 7:57 AM in response to andyman2
    Level 1 (0 points)
    Aug 17, 2013 7:57 AM in response to andyman2

    Right...= hardware issue

  • by andyman2,

    andyman2 andyman2 Aug 17, 2013 8:03 AM in response to dogschool
    Level 1 (0 points)
    Aug 17, 2013 8:03 AM in response to dogschool

    would expect it to show up in your network response times though.  But they seem excellent.

     

    Not sure what your reply means above.

first Previous Page 73 of 145 last Next