Currently Being ModeratedAug 29, 2013 12:58 AM (in response to DougsPlace)
@ DougsPlace: I'm sorry to be the one that bursts your Steve Jobs bubble. He would've probably done exactly what Tim Cook does now: nothing. Just recall the iPhone 4 "antenna-gate" and Jobs's answer: "you're holding it wrong".
"It's not our fault" seems to be an Apple company policy, no matter who's in charge.
Currently Being ModeratedAug 29, 2013 12:58 AM (in response to DougsPlace)
Like others are saying, if you have a burning desire to talk about how great another product is from another vendor or the level of innovation currently underway from Apple vs. Google or whoever, go write a blog or something.
This thread is specifically to address customer issues with wireless networking on the 2013 MBA.
And as I've said in my previous posts on this thread as someone who works in the networking industry, wireless networking as a technology has multiple complexities due to its very nature, and even goes beyond the complexities of wired networking, with such variables as:
- hundreds of different wireless routers / access points in the market, each running different (and often buggy) firmware, and then set up with different user settings, resulting in literally thousands of permeations
- the proliferation of Wi-Fi devices and non-Wi-Fi devices that occupy the same shared RF spectrum causing interference on the network
- issues caused by trying to connect to a faulty or unstable router / AP, including weak RF that results in dropped packets or dropped connectivity
- poorly designed wired & wireless network which results in unstable connectivity or poor performance (e.g. multiple routers on in the same LAN path, with DHCP issues or multiple firewalls to then address via port forwarding)
- the list goes on & on...
So when a particular wireless laptop or other mobile device demonstrates connectivity issues, I'm not quick to blame the manufacturer of the wireless client device, as there are often many other factors beyond a problematic driver that are in play.
And if you really want something that "just works", buy an Ethernet cable.
Currently Being ModeratedAug 29, 2013 1:11 AM (in response to headcase)
MBA is sold as a very portable computer. You are supposed to travel with it and to connect it WIRELESSLY to different routers. And when you spend some money (in this case, a lot of money) you expect that one of the computer's main features to work. And for many people it doesn't!
I understand your point that are too many routers for Apple to be able to test them all. But guess what: it's not my problem!! They should've release the MBA with a list of wifi routers that they are sure it works with. And for the rest of them just say that it might work. Let's see who would buy a MBA in this case!
Currently Being ModeratedAug 29, 2013 1:14 AM (in response to raducan.mihai)
You missed my point... the issue isn't with the 2013 MBA or even Apple. The issue is really with the industry.
If you peruse the support forums of other mobile devices from other manufacturers, you will see these types of threads of "My xxxxxx won't connect to my WiFi! This thing is a piece of junk!" literally every day of the week. If you don't believe me, go look.
Currently Being ModeratedAug 29, 2013 2:07 AM (in response to richard_vd)
Why is it removed?
After applying the new update and entered the syntax you suggest, my machine works well.
This is the best notebook I had.
To note, the wifi signal is weak never before or since.
Currently Being ModeratedAug 29, 2013 2:59 AM (in response to ihawk83)
I disagree with you.
Dougsplace regular Chromebook update posts here will have helped focus Apple's mind in an additional way to the main-stream posts.
This is why I have posted here. My June 2013 MBA has worked fine out of the box, so perhaps I should not be posting. But I'm hoping that my posts have helped rule out potentail causes. I have repeatedly said my MBA has always worked because some visitors don't have time to read all the posts (an almost unprecidented number in just 10 weeks). I have implemented all the fixes posted here to demonstrate what happens to a working MBA - this will have helped others with a working MBA to make their decision about Update 1.0 for example.
So, I welcome Dougsplace's posts here.
M r C o o k , F I X I T !
Currently Being ModeratedAug 29, 2013 3:17 AM (in response to Cloudi)
there is no way to compare an apple with a pear...
Of course he can post, free country. But if he has something to add to the problem. He doesn't even have a "problematic" mac.
Again I wouldnt compare both computers as he does...
Currently Being ModeratedAug 29, 2013 3:20 AM (in response to headcase)
@ headcase: I would agree with you if, for example, all the devices (in a household) connected to wifi router have problems. But all of the wifi problems reported here sound something like this: my iPhone, my iPad and my 5 year old computer all work fine, only my new MBA keeps disconnecting. Do you see a pattern here? Because I do, and it has nothing to do with the routers or interferences or buggy router firmware or whatever...
Currently Being ModeratedAug 29, 2013 3:24 AM (in response to vhkim)
Okay, I followed this thread from the beginning and please forgive me I am a rookie when it comes to OS X and MBA. Yeah, I came from that other environment but don't hold that against me.
Here are my ping times:
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=16.074 ms
64 bytes from 192.168.1.1: icmp_seq=1 ttl=64 time=45.197 ms
64 bytes from 192.168.1.1: icmp_seq=2 ttl=64 time=63.344 ms
64 bytes from 192.168.1.1: icmp_seq=3 ttl=64 time=82.638 ms
64 bytes from 192.168.1.1: icmp_seq=4 ttl=64 time=11.209 ms
64 bytes from 192.168.1.1: icmp_seq=5 ttl=64 time=25.957 ms
64 bytes from 192.168.1.1: icmp_seq=6 ttl=64 time=47.364 ms
64 bytes from 192.168.1.1: icmp_seq=7 ttl=64 time=81.628 ms
64 bytes from 192.168.1.1: icmp_seq=8 ttl=64 time=99.661 ms
64 bytes from 192.168.1.1: icmp_seq=9 ttl=64 time=16.561 ms
64 bytes from 192.168.1.1: icmp_seq=10 ttl=64 time=38.733 ms
64 bytes from 192.168.1.1: icmp_seq=11 ttl=64 time=59.979 ms
64 bytes from 192.168.1.1: icmp_seq=12 ttl=64 time=87.740 ms
64 bytes from 192.168.1.1: icmp_seq=13 ttl=64 time=18.263 ms
64 bytes from 192.168.1.1: icmp_seq=14 ttl=64 time=28.612 ms
64 bytes from 192.168.1.1: icmp_seq=15 ttl=64 time=50.549 ms
64 bytes from 192.168.1.1: icmp_seq=16 ttl=64 time=77.335 ms
64 bytes from 192.168.1.1: icmp_seq=17 ttl=64 time=94.432 ms
64 bytes from 192.168.1.1: icmp_seq=18 ttl=64 time=17.827 ms
64 bytes from 192.168.1.1: icmp_seq=19 ttl=64 time=58.981 ms
Are you saying I should re-image my MBA or wait until the next upgrade? I don't notice any slow down while browsing the web but I don't have anything to compare it to.
Good thread by the way!
Currently Being ModeratedAug 29, 2013 3:42 AM (in response to ihawk83)
Troubleshooting WiFi networks that work flawlessly for every other device - except the MBA - points to.....let's see.... the MBA?
While dedicated forum members have made heroic efforts to find a work-around, the majority of those with the WiFi problem report every other device on their network works flawlesslly - holding constant for router/AP and RF variables. So, if the only device not working for them is MBA, I'm not sure how excoriating router manufacturers, network congestion, and better customer service models troubleshoots the MBA WiFi problem. What some long term customers are 'gonna do' is not buy/return 3 times, or spend months playing musical macbricks. Some will not be so accepting of mediocrity. Troubleshooting also means telling Apple they need to fix the problem as many times as it takes to make that happen. The geniuses will tell you Apple does monitor these forums, and they do pay attention to profile stats. Like mine.
Currently Being ModeratedAug 29, 2013 3:46 AM (in response to DougsPlace)
It's actually incredible that people spend all that money on a laptop. That laptop is the only device not working on their wireless network and they blame the router.
You can blame Maxwell for what it matters, but thing is Apple has to fix this bug in the laptop!
I am still waiting to buy one, but they have to fix this issue before I do so.
Currently Being ModeratedAug 29, 2013 3:48 AM (in response to jeets68)
This is exactly the result before I had entered the syntax that richard_vd had proposed. Neither do I, before that, I did not notice any slow down but compared it to my macbook core 2 duo 2007, the new machine was downloading less flowing. Now, it works well. But we must recognize that there is a hidden problem.
There is no more explanation from APPLE after the last update ...It's a little weird.
More Like This
- Retrieving data ...
- This solved my question - 10 points
- This helped me - 5 points