Try this one:

- Disable all other users on your Mac device

- create a guest account

- log in in the new guest account and log out from your main account

- log out again from the guest account

- check if WiFi is working properly

- if not, disable bluetooth, reconnect WiFi

- just use a couple of minutes your Mac, till it´s reconnected again to the WiFi and it seems regular in the connection

- bluetooth on and continue surfing on the web

Does this walk around works for anyone?

Thank you, praeceptor_cgn. This workaround should indeed solve the issue- for a limited amount of time, alas. Like other workarounds, it renews the discovery process. But for how long? Any change to network settings in Yosemite will set WiFi connectivity in motion again for some time, it seems.

Apple should really fix this Discovery bug. That being said, let al the plaintiffs here run Namebench (http://code.google.com/p/namebench/) as a diagnostic tool to realize that probably their current DNS and most of the alternatives are being hijacked/redirected, in many/most cases by their local ISPs (e.g. to block some content deemed illegal or dangerous). A highly complex and irreproducable situation. It is my firm belief that Yosemite ( maybe in combination with iCloud services) cannot handle DNS redirection, in particular NXDOMAIN ("IP adress not in DNS lookup table") redirection.

Amongst other issues, probably. Some Pandora's box has been opened, try to get the lid back on, Apple...

Yosemite surely seems to have a very short DNS lookup timer in the problematic cases. Or something of the sort. If you do not believe me read this article:

Non-responsive DNS server or invalid DNS configuration can cause long delay before webpages load - Apple Support

Wait until your Wifi gets unresponsive, then search your web page by IP instead of its DNS network name. Apple's own example, quote:

If there's an issue with your DNS configuration (for example by endless redirects because of your ISPs own quirks, or a slow internet connection- [between the brackets is my own addition]), trying to access a website via its DNS name, such as www.apple.com might seem slower than accessing the same site from its numerical IP address, such as http://17.172.224.47.

If your unresponsive WiFi gets through to the Apple website in this way, you may be certain your computer has a DNS resolving problem. No WiFi/network connectivity issue. Under Yosemite probably Discoveryd, or its lookup timers. Or your own ISP...

To be continued, I'm afraid...

Something extra: in an attempt at extreme power saving, the Yosemite DNS lookup timers will probably have been turned back to the bare minimum. Would anybody care to find out with me how to stretch those, please? Command line is fine. Not much documentation on the net about that. 

Hi

Here there is a great article about what we are discussing :

Why DNS in OS X 10.10 is broken, and what you can do to fix it :

"For 12 years, the mDNSResponder service managed a surprisingly large part of our Mac's networking, and it managed this task well. But as of OS X 10.10, the mDNSResponder has been replaced with discoveryd, which does the same thing. Mostly. Here are some strange networking problems we've observed since installing 10.10"

http://arstechnica.com/apple/2015/01/why-dns-in-os-x-10-10-is-broken-and-what-yo u-can-do-to-fix-it/

Personally, I did not even try to reinstall yet the OS X 10.9 mDNSResponder on a 10.10 system ...

But the author of the article seems to say that "all the problems listed above magically go away"

Cut my speed in half. Went from over 100 download to under 50.

Been running 10.10.2 since it came out and still the same problem.

Close the lid,bingo. That is, when I open the lid and try to connect to internet nothing.

Turn Wifi on off, reboot, etc, etc have tried all of the fixes from all of the threads and same problem keeps reappearing.

Very frustrating. I have 2 iPads and 2 iPhones (all software up to date) and they work perfectly on the same network that I am running my Macbook Pro, Retina, Late 2012 model. Not what I expect from Apple - have spent hours trying to solve this problem to no avail. There is just something deep down in the OS that is screwing everything up (by everything, the ability to connect to the internet when I open the lid to my beautiful brick).My internal network is working perfectly (hopefully Apple will not screw up my Time Capsule and AEX's). My problem is a pure "connecting to the internet" and it is a reoccurring one - it never goes away - unlike my internet connection which constantly goes away.

APPLE HELP!!!!

Once again: I don't have the problem anymore, but am still following the thread.

I'm getting the OSX daily newsletter and they had a suggestion how to get rid of the problem.

Remove Bluetooth PAN Helps Resolve Wi-Fi Conflict in OS X Yosemite?

http://feedproxy.google.com/~r/osxdaily/~3/OWOKt2xIv7A/?utm_source=feedburner&ut m_medium=email

Maybe someone would like to try it - it's definitely simple enough....

Good luck.

Just simple questions for Apple OS X Development Team and us Users.

1) Must we, as average Mac Users, Frankintosh Bits of OS X Mavericks to Yosemite just to get Yosemite to work?

2) Must we, as average Mac Users, render Bluetooth or other OS X inherent items useless just to get Wi-Fi to work in Yosemite?

3) Must we, as average Mac Users, do Terminal Command Line and other work a rounds in Advanced settings just to get Yosemite to work?

Ask yourself:

4) Would an average Mac User expect to open their brand new Apple Macintosh that they just spent thousands of dollars for, set up, turn on, Set up User Account, update and start using with no problem?

5) Must we as, average Mac Users, have to upgrade our Home or Business Network/Internet equipment just to get Yosemite to work?

Finally:

Why is their no stable release of OS X for all Mac Users to fall back on in times like this, readily available, FREE?

My Two Cents:

FREE Linux Distributions don't leave people or their Core Customers in this situation who choose to download their Distro of Linux. Microsoft has NEVER left their Users and Core Customers in this type of situation, like this, for this length of time. Just because there are posts just in this thread of Wi-Fi issues, doesn't mean the problem is confined nor isolated. One unhappy customer will cause a loss of 10 + or more customers and a bad reputation. That's business 101.

I am glad to know Yosemite ran well on my Mac. I don't use it's features and my Mac shipped with Mavericks. I'm sticking to Mavericks until it's bitter end as did Snow Leopard users. It is my hope that Apple Development Team will have a resolve for all very soon.

Hi jndupuis - couldn't agree more - I'm with you all the way.

One bad apple spoils the barrel!

I AM A USER NOT A TECHNICIAN!!!

Furious and disappointed apple victim.

<Edited by Host>

I remember my first computer. Reliable, user friendly, highly supported and regarded as the most advanced of it's kind in the business and broadcast world. Due to their misjudgement of their consumer base and mismanagement of the company; folded in the year 1993-94. The technology bought out by other corporate intities that be, still, to this day on market. Yes, that's right. I'm talking about Commodore Business Machines/Commodore Amiga Inc. This is highly reminescent of that era. To think that I could have spent my 2+ grand on a NEW Amiga One X1000 system with the new OS 4.1 and Ubuntu  Remix Linux installed is upsetting. System 76 is also slowly becoming the Macintosh of the 21st Century.

Apple?

Sitting on a gold mine as we, there customers, squirm to get our Macs running with, now, the world's worst Unix based OS anyone has EVER seen past or present. How Mac has any toe hold in the business and server world, is beyond me. The hardware on the market is more advanced than ever as Apple is scuffing around trying to get this virus called Yosemite to work. Rewriting and fixing an OS X that wasn't broken to begin with.

I'm not on social media for personal and private reasons, however, I know my opion counts. I know that this and other posts I've made are free to use at anyone's discression. So be it. Apple, do not become another Commodore, Inc. That's about all I have to say.

Hear, hear, John!

Rewriting and fixing an OS X that wasn't broken to begin with.

"If it ain't broke, don't fix it" is my signature on a lot of fora. OSX Tiger was great. Snow Leopard was great, I'm still running it as we speak, BTW. Mavericks runs fine. They that still can are massively retrograding to it. Actually, did the verb " to retrograde" exist in a software context before Yosemite?

And what would be the cause of all this? I've mentioned this before: "kindergartening" OSX to get it closer to iOS, or get it to connect more intricately with iCloud (which is kind of of a crippled Frankenstein itself). And Apple very stubbornly continuing to use Broadcom WiFi/Bluetooth chips that are not up to par to what the manufacturer specifies, on Airport cards that are poorly designed RFI wise (as you have pointed out before). With Yosemite overloading the already crippled chipset, not realizing it does not quite deliver.

The professional AV industry is also thrilled by A(udio)V(isual)B(ridging), a spearpoint technology that uses Ethernet to stream AV data, relying heavily on Q(uality)O(f)S(ervice). Great. But what does Apple do with it in Yosemite? They pigheadedly do not follow the AVB standard, and use AVB over WiFi. Thus mis-mastering or overtaxing the AVB protocol, which has not been designed for wireless use at all. Guess on what chipset? Right, the same Broadcom one.

Probably with code borrowed from some Broadcom hocus-pocus called "Broadsync" http://www.broadcom.com/products/technologies/BroadSync-HD

Considered like this, Yosemite appears to try to achieve spearpoint status, based on false promises and maybe lame firmware by the chip manufacturer Broadcom. These chips may perform well under Mavericks, Linux and Windows (they seem to do so anyhow), because these OSes are not overtaxing them. Yosemite on the other hand, clearly is overtaxing the Broadcom chipset, probably because of false expectations toward it or too optimistic specs published by its manufacturer.

As we all know, Apple is working on patches for specific issues, probably with teams of developers for each isolated issue. As is probably standard in the software industry. What I mean to say Apple is now in dire need of lateral thinking. A whole amalgamate of issues seems to be caused by the wrong choice of components, or writing software pushing those components to the utmost without verifying/testing the manufacturer's optimistic/ exaggerated specs. And that is a very tough nut to crack...  

Danm those edit timers: here is the edited version:

Hear, hear, John!

Rewriting and fixing an OS X that wasn't broken to begin with.

"If it ain't broke, don't fix it" is my signature on a lot of fora. OSX Tiger was great. Snow Leopard was great, I'm still running it as we speak, BTW. Mavericks runs fine. They that still can are massively retrograding to it. Actually, did the verb " to retrograde" exist in a software context before Yosemite?

And what would be the cause of all this? I've mentioned this before: "kindergartening" OSX to get it closer to iOS, or get it to connect more intricately with iCloud (which is kind of of a crippled Frankenstein itself). And Apple very stubbornly continuing to use Broadcom WiFi/Bluetooth chips that are not up to par to what the manufacturer specifies, on Airport cards that are poorly designed RFI wise (as you have pointed out before). With Yosemite overloading the already crippled chipset, not realizing it does not quite deliver.

The professional AV industry is also thrilled by A(udio)V(isual)B(ridging), a spearpoint technology that uses Ethernet to stream AV data, relying heavily on Q(uality)O(f)S(ervice). Great. But what does Apple do with it in Yosemite? They pigheadedly do not follow the AVB standard, and use AVB over WiFi. Thus mis-mastering or overtaxing the AVB protocol, which has not been designed for wireless use at all. Guess on what chipset? Right, the same Broadcom one.

Probably with code borrowed from some Broadcom hocus-pocus called "Broadsync" http://www.broadcom.com/products/technologies/BroadSync-HD

BroadSync HD Technology is Broadcom's custom implementation of the IEEE 802.1 Audio Video Bridging (AVB) draft standard, which provides guaranteed QoS, frame synchronization and timing that is necessary to stream professional-quality audio and video traffic over Ethernet.

Considered like this, Yosemite appears to try to achieve spearpoint status, based on false promises and maybe lame firmware by the chip manufacturer Broadcom. And on blatant custom misuse of the AVB draft standard. WiFi AVB not even being promised by Broadcom.

These chips may perform well under Mavericks, Linux and Windows (they seem to do so anyhow), because these OSes are not overtaxing them. Yosemite on the other hand, clearly is overtaxing the Broadcom chipset, probably because of false expectations toward it or too optimistic specs published by its manufacturer.

As we all know, Apple is working on patches for specific issues, probably with teams of developers for each isolated issue. As is probably standard in the software industry. What I mean to say Apple is now in dire need of lateral thinking. A whole amalgamate of issues seems to be caused by the wrong choice of components, or writing software pushing those components to the utmost without verifying/testing the manufacturer's optimistic/ exaggerated specs. And that is a very tough nut to crack...

Just on the positive side, one more workaround for the geeks here. It has been posted Yosemite WiFi does not play along with WPA2enterprise passwords. Researching why, I've stumbled upon the fact that at least some AVB audio devices indeed cannot handle WPA2enterprise passwords.

Please disable AVB on the WiFi interface (en0) to see if that makes a difference; command line in Terminal:

avbdeviced --disable-interface en0

To turn it back on:

avbdeviced --enable-interface en0

It seems Yosemite has a whole Pandora's box full of bugs for us poor users. Great gift it was... Anyhow, this trick might eliminate at least one bug, maybe more. 1 bad element in the WiFi chain/ discovery process might break the whole network stack... So for testing purposes, eliminating AVB device discovery seems vital. My, the more I read about this issue, the more intricate it gets.

We'll see. Thank you all.

NB: this workaround has not been mentioned in this whole, long thread.

Hex, yes indeed!

And what would be the cause of all this? I've mentioned this before: "kindergartening" OSX to get it closer to iOS, or get it to connect more intricately with iCloud (which is kind of of a crippled Frankenstein itself).

OS X Yosemite is nothing more than an App Sandbox. A child's virtual sandbox to play in, minus the bucket and shovel. This cannot be a real GUI based on such a dinky unstable OS! A glorified cell phone OS that works well on machines with iPad and iPhone type specs, Hmm, somewhat. It has come time for me to just come out and say all this. Scared? Of what!? Apple kicking me off this post? Shutting down my OS X or Apple ID? Look at me, I'm shaking. I'm scared and frightened. Time to also let another cat out of the bag that I found during all my testing. Boot Camp Windows 7 Pro. using as much disk space as possible Update it. Make sure it's working. Then hocus pocus with Command+R and Disk Utility erase the Macintosh Partition and make it MBR MSDOS. Restart in Windows 7 and claim it as extra storage. Now you got a highly efficient most reliable Windows machine. Then use Windows Backup on an external HD. If my stupid USB SuperDrive had an EJECT button! I downloaded all the Hacintosh stuff to install Snow Leopard on Ivy Bridge. However, as I stated, I will run Mavericks until the bitter end. I will not be heckled or badgered by a blinking flashy "Download OS X Now" radio button at the Apple Store - EVER AGAIN!

With you all the way, John. Always have been. Pity though, not being able to play along with the young ones. However, I'll find a way to run the software I need on an obsolete system. I have ever. Even use cloud facilities that do work.

Using my Mac professionally means staying on an antiquated system. No two ways about it. At least I do not have to beta test there. It just worked. Out of the junk yard.

The way it's going now, look at my avatar.