-
All replies
-
Helpful answers
-
Nov 18, 2014 7:03 AM in response to tomstephens89by NosTech,Same Macbook Pro Retina, actually I hadn't much trouble before using 10.10, just upgraded to 10.10.1 and now my connection has become incredibly slow (comparable with the old 56k modems, luckily it doesn't drop all the time, as I've read in some other posts). Tried restarting my Macbook router etc, but all stays the same (other devices are working at full speed). So indeed things have certainly become worse then it was before. I hope they fix this soon. First the RJ-45/ethernet port is removed from the devices, so you totally depend on wifi, and then this happens...
-
Nov 18, 2014 7:16 AM in response to tomstephens89by Panthertiger,Hi, I am still (after Update 10.10.1) having problems with Wifi, Bluetooth, Keychain, Handoff never worked, I tried to connect my iPhone (5s) with my MacBook Pro (2013) – it says, "not supported device", it is sooo annoying and disappointing.
-
Nov 18, 2014 7:26 AM in response to Savo9by maniacomer,I have the same issue and try your solution - it works!!
1. Resetting the System Management Controller (SMC)
Do both on restart your mac.
-
Nov 18, 2014 7:27 AM in response to tomstephens89by ayrtonf1,Stil the same S**T.
One month later, I'm starting to think Apple laught at us.
Or they are completely lost.
imac27,
every sleep or shut down, needs a :
click on wifi icon
open network preferences
assist me
diagnostics
continue
continue
always allow (in network diagnostics want to acces key... window pop-up)
-
Nov 18, 2014 7:27 AM in response to Panthertigerby njohan,... you must look how and witch account they are connected to... if it´s your E-mail/s or Phone numer, by then mean so your keychain, handoff will work. Because if they are connected differently.... in all your OS X/iOS devices then it will have hard to sync, the connection must be same... same e-mail or phone number.. and not.. "100 of different connection to your Apple-ID".
Anyhow that what solved my problem with Handoff, in my older computers to my iOS devices.. and also my iOS devices had different connection types as priority one, two, three and so on.
And also started a "new-life" with my latest Apple computer... fresh install with everything (-7 years ago last time, or 4 OS X ago) :-)
-
Nov 18, 2014 7:51 AM in response to njohanby Ron R,10.10.1 fixed the wifi issue. I had minor random wifi drops with Yosemite prior to the update. now it's smooth sailing. Very quick and responsive.
-
Nov 18, 2014 8:01 AM in response to tomstephens89by shumo1,I just did the update on my iMac 27" and all I get is silver screen.
Was having wi-fi issues, but now can't even see anything. Why can't they get this right?
Restoring from time machine. VERY DISAPPOINTED!
-
Nov 18, 2014 8:12 AM in response to shumo1by njohan,Remember always to do an.... "Repair permissions" to your OS X, before you do an OS update :-)
And also you can do this after the update.
Otherwise always good to do this once a month, to make the "repair permissions"
(sorry about the text on pic, its in Swedish) This is the "Disk Utility", you can find it in spootlight -
Nov 18, 2014 8:27 AM in response to tomstephens89by WilmBilly,I have problem with Wi-Fi issues after I got OS X Yosemite upgraded.. I have no problem with I-Pad and I-Phone on Wi-Fi. how could we fix this situation?
-
Nov 18, 2014 8:38 AM in response to tomstephens89by Mike_Ritter,My WI FI worked fine at home (Airport router) but failed at my University office. I just tried this and it works for me:
System Preferences > Network > Advanced: Click the checkbox next to “Require administrator authorization to: Change networks.”
Click OK. Click Apply.
-
Nov 18, 2014 9:07 AM in response to tomstephens89by bjelliot,I have found success in changing up the DHCP IP allocation of my home's router - changed from 192.168.x.x to 10.10.x.x. I noticed that when I was connected to my home's network, there were several IP addresses that were being "remembered" from my work's router. These addresses were on a different subnet and my theory is that the my router was having a hard time figuring out what to do with these addresses.
I was able to track down the issue by looking at my home's router "Attached devices" and noticed that there were some 192.168.76.x addresses (given to my iPhone and MBP at work) when my home router only allocates 192.168.1.x addresses.
Just my working theory and this may help some people track down the issue along the way.
-
Nov 18, 2014 9:27 AM in response to tomstephens89by InsufficientEvidence,Upgraded to Yosemite 10.10.1 (14B25). It did not fix the (seemingly) random dropping of wifi. Very disappointing. Ran an old ethernet cable across my house. My Macbook Pro is now just a tethered desktop.
-
Nov 18, 2014 9:30 AM in response to Mike_Ritterby Csikós Péter,I have the same problem. After reseting everything and after a full install nothing changed.
I have tried all settings, and still had the WIFI drop problem.
Now it looks, the following made my WIFI nearly good again. (I just tried lots of settings, without any technical background)
sudo sysctl -w net.link.ether.inet.max_age=1
If I want to use SSH it still said broken pipe, but I can use my MacBookAir.
-
Nov 18, 2014 10:06 AM in response to bjelliotby kevinski_uk,I'm pretty sure this whole issue is around DNS and with everyone having some sort of success by changing configs and rebooting routers all they are really doing is causing cache's to be flushed but the issue still returns for many so it's got to be a bug in the way Yosemite is resolving DNS.
my problem was solved by setting IPv6 to manual over a week ago and i haven't had a single issue since but as others have tried this without success they may have done things differently.
I noticed when running nettop in terminal that an established IPv6 was causing connectivity to hang and was also the cause of the slow shutdowns and since setting IPv6 to manual or local on all my macs i haven't seen the established IPv6 connection since so have no idea what it was as i don't recall the port it was trying to use at the time
The only other thing i did was to edit /etc/hosts which basically causes discoveryd to flush the hosts cache every time you boot your machine, so maybe this cache flushing helps, don't really know but these were the only things i did to get LAN and WIFI stable.
This is the event you will see if you search for discoveryd in Console after touching or editing your hosts file
Basic DNSResolver etc/hosts file changed: Event 0x0 Flushed /etc/hosts cache
Anyways all I'm really saying is, i believe it is a DNS bug that can't be resolved properly with just config changes.
Also we shouldn't have to do anything to routers as they all follow a standard
-
Nov 18, 2014 10:10 AM in response to kevinski_ukby ecotecit,If can't be DNS, when the wifi drops nothing gets through, not even ICMP.
