-
All replies
-
Helpful answers
-
Dec 29, 2014 4:10 PM in response to Refael Nby Dan2012abc,I can confirm the following works good. I had so many problems with wifi stopping working, safari doing nothing, dns/bonjour not responding, meanwhile IMCP was still working...
This fixed it for me. The main important part is to click "Apply" when you have removed wifi before you re-add it.
This absolutely fixed it 100% for me. I think it came back one, when iCloud synced some wifi network settings somehow and I had to do it again.
nicknish wrote:
- Creating a New Wi-Fi Service (this solution worked for me!)
- Copy and paste these instructions, because you'll be disconnected from the Internet and you'll need to reboot.
- Go into your Network Preferences > Select Wi-Fi Service (in the list in the left column) > Click on the options (cog icon) > Select "Make Service Inactive" > Select Apply.
- Select the same Wi-Fi Service > Delete It ( – ). Reboot.
- Return to Network Preferences > Create a New Service ( + ).
- Inside the prompt select Wi-Fi under Interface, name the Service Name something other than Wi-Fi. (I named mine Wi-Fi2. Apparently if you retain the previous Wi-Fi name the WiFi dropping will return on reboot.) > Click Create.
- Click Apply.
- Delete and Reconnect to your Preferred Network
- Go into your Network Preferences > Advanced > Select Your WiFi Network and Delete It ( – ). Reconnect to it.
- Creating a New Wi-Fi Service (this solution worked for me!)
-
Dec 29, 2014 4:18 PM in response to therealiktby PFJ30,Lets hope that one outcome of this whole debacle is that Apple decides keeping quiet is not the appropriate response. Join me on Twitter

Paul Johnson (@dairymews) 30/12/2014 00:12#YosemiteProblems #Apple #NewYearsResolution How about: "Openness by default, secrecy a last resort." Join in.
Download the official Twitter app here
-
Dec 29, 2014 4:29 PM in response to hexdiyby jndupuis1,10:4 - Acknowledged.
My Mini is still running Yosemite well. The best I can tell, is my coax is a straight run to my Cable Modem at the shortest possible distance. I am using a high end Certified Cat 6 shielded cable from my Cable Modem to my Router. The shielded Cat 6 is the type they use in Server rooms. It's only approx. 3 foot. This may explain why my 5 GHz has
Tx Rate: 405 Mbps
Noise: -91 dBm
RSSI: -31 dBm
My PHY Mode: 802.11n
MCS Index: 23
Channel: 44
Throwing this out there. I'm in a populated neighborhood with a huge amount of broadcasting SSID's running on the 2.4 GHz band. Which is why I chose the 5 GHz band for my Mini and iPhone. Using Shielded Cat 6 for extra measure against noise. My 2.4 GHz is only used for my Android phone and printer because they cannot detect and connect to the 5 GHz bandwidth. Of course, Guest is 2.4 GHz by default.
-
Dec 29, 2014 4:52 PM in response to jndupuis1by hexdiy,Dear all, I've input some feedback to Apple on https://www.apple.com/feedback/macosx.html
Here's how it reads:
Dear Apple,
I've been following some Yosemite WiFi issues closely prior to some major hardware purchases on my part. Mainly on: https://discussions.apple.com/message/27375745#27375745
Page # 125 (sic).
After a poll on a Dutch Apple forum, it seems ± 42% of the users are still affected by this WiFi bug which makes Yosemite WiFi
1. Probably slow.
2. Disconnect every 5 minutes or so from the WiFi network.
3. Not (properly) connect to the WiFi network on wakeup.
Due to these flaws, which are unallowable on a corporate network, I am hereby compelled not to foresee any new purchases of Apple hardware. Ever so sorry.
Yours truly,
Hexdiy
Former Apple Fanboy.
All of this is true/ plausible. Duplicate this in your own language/ formulation to the same URL and you may create a minor datastorm just to be heard. Good luck to you all! And yes you can! (no political implications included).
<Link Edited by Host>
-
Dec 29, 2014 5:02 PM in response to Dan2012abcby wombat2k,Of all the workarounds I've seen, this one looks the most probable. It's similar to one that was posted previously, but this one seems more complete and has a few extra steps that actually make sense. The renaming of the Wifi service is probably the part I was missing
Will give it a spin. Thanks.
-
Dec 29, 2014 5:12 PM in response to hexdiyby hexdiy,Thank you, Host, for editing my link. Now we know somebody important enough is reading along- provided you're not a bot. I knew it!
-
Dec 29, 2014 5:50 PM in response to hexdiyby jndupuis1,Saw that, did you? I too, have had a feeling this thread is being followed, for it is too big for Apple to deny or ignore. I may be running Yosemite just fine but I upgraded my equipment and spent time erasing and installing to find the "magic trick" that works for me. Small Business and Corporations cannot have there time wasted in this manner. Critical business data and customer data at stake. Yosemite 10.10 and 10.10.1 released due to Apple deadline or not.
In my own words:
Yosemite 10.10/10.10.1 is not ready for Businesses, let alone the Average User. The Average User, at this point, in this "OS X WIFI Issues" thread, has gone places in OS X and adjusted Advanced Settings; used Terminal Command Line that they would, under normal circumstances, never use or even be comfortable using. It MUST be noted that the ONLY true fix here to the issues in Yosemite is for Customers to revert their Macintosh Computers back to the OS X that shipped with the machine. Whether it be with Internet Recovery or a trip to the Genius Bar.
-
Dec 29, 2014 6:23 PM in response to wombat2kby wombat2k,Aww, didn't work. Was able to make it fail the first time it woke up from sleep. To be fair, a I had re-installed my computer at one point and it didn't help, but the Wifi service renaming thing sounded promising.
Ah well, back to disabling sleep when powered.
-
Dec 29, 2014 6:26 PM in response to jndupuis1by jndupuis1,What I have in bold print in my reply to you, hexdiy, has been submitted to Apple Feedback with some added notes. It is time to direct our voices as a choir to Apple Feedback. We are talking amongst ourselves but it is the time for our choir of voices to be heard directly by Apple. Cheers!
-
Dec 29, 2014 7:30 PM in response to tomstephens89by CarpeMeh,Wi-Fi Sharing From Ethernet Doesn't Work Either!
And has been deteriorating steadily since installing yosemite on my mac pro (black). This suggests there is something more fundamental than a lot of the solutions I have been seeing. Couldn't find anyone discussing this, sorry if I missed it earlier in the thread.
-
Dec 29, 2014 8:01 PM in response to jndupuis1by hexdiy,Good, John. In the mean time I've narrowed this down to a probable Multicast DNS issue. Up to Mavericks this would be up to an mDNSResponder problem, but under Yosemite this has become a genuine Discoveryd issue. Largely undocumented.
A good way of testing would be to turn off Multicast without loosing DNS lookups under Yosemite (I do realize this may present a problem with iDevices). A delicate .plist, for those not afraid of the Terminal:
Post #2, the rest may not be aware yet.
Are we getting somewhere? I may be malleable but not quite a fool.
Nice testing, bro!
-
Dec 30, 2014 5:05 AM in response to tomstephens89by JTFCD,Just thought I'd add my experiences:
Bought a refurb MacBookAir 13" for my son at Xmas and right out of the box, without syncing accounts, I had the wi-fi issue.
I updated to 10.10.1 and transferred the account from his old MacBookAir 11" - this didn't solve the issue at all.
All the other Mac's, iMac (which came with Snow Leopard), MacBookAir 11” (which came with Mountain Lion) and various iDevices all with latest iOS and latest Yosemite) all work fine on wifi and ethernet.
I connect to a Virgin Superhub on modem via an ASUS dual band router.
The MacBookAir connects when it first boots up and either drops the connection in the first 5-10 minutes, or will be OK until it's woken from sleep.
Only a restart brings the wi-fi back.
It's very odd - the wifi says it's ‘on’ in the menubar, but there's no connection when you click on it, there's not even any ssid's listed.
Opening the network prefs, shows the wifi being off. Clicking it on, does nothing. Restarting brings it back.
I’ve tried everything, except replacing the kext file with one from Mavericks (which I don’t think is wise or I should have to) and I don’t want to reinstall Mavericks, not even sure I could as it shipped to me with Yoesmite.
I’ve tried deleting system config folder, changing settings in NetworkPrefs, removing and re-adding the network service, fixed IP’s, new DNS, separated the bands on the router, turned off app nap & airdrop & handoff, a few terminal commands - nothing works - I've had a great Xmas thanks Apple.
I buy refurb on the understanding that they are fully checked before sending, to sell me a product which has a defect fresh out of the box is very sloppy and I’m sure it’s illegal.
I’ve got a Genius Bar appointment next week, where I’m hoping to exchange it with an identical MBA that works, as this Mac is a doorstop if wifi doesn’t work.
I'll report back after this to see if new hardware solves it.
-
Dec 30, 2014 7:30 AM in response to JTFCDby jndupuis1,Truly, this is beyond the point of irreproachable. I hope all joins in at Apple Feedback to let them hear directly from us. If the best Apple can do is leave Mac users with a mere memory of how reliable and powerful their computers once were, Snow Leopard and prior OS's, is a shame and very sorrowful. That was the bottom line in the decision to switch to Macintosh to begin with. Mac was, no Antivirus, no fuss, no nonsense....was! Yosemite, what a name! Sinking like a rock in the ocean.
-
Dec 30, 2014 7:37 AM in response to jndupuis1by ofeuillerat,I am sad I have to agree with this.
Choosing a Mac when I needed a new machine was a no brainer option for many years, now I'll think twice...
Bugs, issues happen all the time on every platform, it is normal, but the response (or lack of) by Apple is the concern here.
-
Dec 30, 2014 7:40 AM in response to tomstephens89by OzziesMAC,Also notice how UNDER-REPORTED this issue is on all the Apple or Mac Magazines out there.
It's either downplayed or flat out not mentioned. Same thing happened during the Mavericks Firewire
issue.