Currently Being ModeratedMay 9, 2013 8:48 PM (in response to toddwest24)
Thanks I wasted alot of time on this this until I read your post. This worked!!! iMessage and Face Time finally working properly on a late 2010 macbook air running mountain lion. Thanks again for providing an actual solution.
Currently Being ModeratedMay 10, 2013 7:51 AM (in response to toddwest24)
YES, toddwest24 that worked!
Currently Being ModeratedMay 23, 2013 9:41 PM (in response to ndpendnc)
dude, toodwest24 it works great men... Thanks a lot.
Currently Being ModeratedMay 28, 2013 3:44 PM (in response to ndpendnc)
- Step 1 - REBOOT your machine.
- Step 2 - Login to FaceTime
- Step 3 - Enjoy
This has worked everytime for me. I've encounted this issue on three MacBooks, apparently after a software update. If this doesn't work for you, then toddwest24's solution seems to have helped a lot of other folks.
Currently Being ModeratedJun 19, 2013 6:43 AM (in response to ndpendnc)
I wish I could share everyone elses enthusiasm here. I have tried all the recommendations (Host file reset, clearing cache, looking for iphone certificates, auto time settings etc etc) and still continue to get the error..! I've all but given up.
Currently Being ModeratedJul 31, 2013 7:07 AM (in response to applecable)
Absolutely I have tried all these solutions listed here and imessages on the Mac (not on the OTHER MAC, nor on my iOS devices) is HOSED.
Currently Being ModeratedJul 31, 2013 4:18 PM (in response to ndpendnc)
Thanks alot man!!! That worked! I ended up having to restart after fixing the hosts file, but Facetime and messages works great now!
Currently Being ModeratedJul 31, 2013 5:59 PM (in response to William Mckelvy)
Thanks for posting this; I tried replacing the hosts file with no luck but after your post about the serial number, I checked that too. I recently had my MBP logic board replaced (twice) as the video card was defective. As you suggested, the machine doesn't know it's serial number. I will make an appt to take it in unless someone can tell me how to fix it myself. I'm traveling for the next couple of weeks and neither Facetime nor Messages work.
Currently Being ModeratedAug 1, 2013 3:33 PM (in response to ndpendnc)
I've read this entire thread and gone through ToddWest24's process, but I am getting a different response than I've seen here: when I try to move the Hosts file back into my Finder from my desktop, here's the message I get: "The item “hosts” can’t be moved because “etc” can’t be modified."
Currently Being ModeratedAug 2, 2013 5:01 PM (in response to toddwest24)
Thanks Todd, it worked for me as well.
Be sure to reboot your computer for it to take effect. WHEW!
Currently Being ModeratedAug 2, 2013 5:03 PM (in response to Kelly the ex-PC user)
It asked me to authenticate, which I did, and then had to put in my login password, and then was prompted to replace the file. Once I clicked replace, it did. Then I tried FT and it didn't work. After reboot, it worked like a charm.
Make sure to reboot after doing it.
Currently Being ModeratedAug 2, 2013 5:06 PM (in response to rgummy)
By the way, once I got FT working, I unclicked the auto time zone feature so it wouldn't screw up my calendar and so far so good!
Currently Being ModeratedAug 2, 2013 5:47 PM (in response to toddwest24)
After I did all this (for the second time) and rebooted with a PRAM reset iMessage finally came alive and allowed me to login again.
Currently Being ModeratedAug 6, 2013 12:29 PM (in response to toddwest24)
Todd, you are my hero.
Also, I'd like to point out that your experience with Apple Support seems to be common - remember when the iPhone 4 came out and it was tearing through data? Every call we made to Apple was met with a "I've never heard of this issue" but it was all over the forums. Drives me crazy!!
Currently Being ModeratedAug 8, 2013 12:00 PM (in response to toddwest24)
Thanks toddwest24. Worked for me. Other people say they did not need to restart after fixing the hosts file, but it wouldn't work for me until I restarted, so if todd's solution isn't fixing the problem, try restarting.