Currently Being ModeratedJul 21, 2011 11:45 PM (in response to KLNG)
I have the exact same problem. I get this message in Console:
AppleIDAuthAgent: Unable to determine if Apple ID certificate is trusted.
com.apple.message.domain: com.apple.coreservices.appleidauthentication.checkAccountCertificateTrustRecove rableTrustUnspecified
Currently Being ModeratedJul 22, 2011 12:46 AM (in response to dreyln)
Yes, apparently the upgrade has really mess up the authentication process. I have learnt from other discussion that if you open a new account, the file sharing works fine and I have tried it myself and it works too.
Apple really need to get this fix immediately today, this is serious! I cannot just start a new account because all the printers and scanners are set up with this existing one. Everything has to be reconfigured and I don't have the whole day.
So how to determine an Apple ID certificate is trusted? I have three machines in my name and same Apple ID, why it is not trusted?
Currently Being ModeratedJul 22, 2011 1:47 PM (in response to KLNG)
I found a work Around -
Turned on file sharing , went to Advanced Tab and
turned on SMB (Windows Sharing),
Turned OFF (Unchecked) AFP
I can now connect to all Macs.
It definetly looks like an AFP issue.
See my original Issue at:
Currently Being ModeratedJul 22, 2011 2:22 PM (in response to spettinger)
Even the workaround doesn't work for me.
Non of my macs can talk to each other anymore.
Currently Being ModeratedJul 22, 2011 8:45 PM (in response to KLNG)
I don't know if this will help any of you but I got connections working by:
1. making a new account on my tower computer (Not sure if that did anything)
On both computers:
2. Deleting all the shared folders in the sharing preferences
3. Then editing the drives/folders settings in get info ie. adding administrator read write at the bottom
4. re-added the folders/drives in the sharing preferences
I also changed the user name of my account on my mac book, but I doubt that had anything to do with it.
To note the disabling AFP and leaving SMB on worked for me, but messed up my time machine backup, so i did all this stuff.
Currently Being ModeratedJul 22, 2011 9:32 PM (in response to nckmd)
Similar to what you did, I followed what I found on this post:
I use Mobile Me (Back to my Mac) to connect, which always seems to give full access to the file system anyway, so removing all the shared folders did not change this, but did restore file sharing somehow
Currently Being ModeratedJul 23, 2011 9:14 AM (in response to dreyln)
Turning off AFP in the option window does it for me, thx! spettinger.
Apple is doing all these hidden little things in the upgrade that disrupt the normal workflow, someone working in the Lion team is a trickster.
Currently Being ModeratedJul 23, 2011 4:07 PM (in response to spettinger)
Nope, didnt work for me. I disabled all sharing, removed all shares from the list, reenabled SMB only shareing on one folder, and I was still unable to mount it properly. However, my linux desktop could mount the devault volume share that appeared, I was able to authneticate with my admin user but I could not open any files on it - Nautalus reported "Error - unsupported feature".
Currently Being ModeratedJul 24, 2011 4:49 AM (in response to Mista2)
Found this on another board....
Submitted by HD BOy on July 10, 2011 - 8:30 P.M.
This problem is very real, but it is *NOT* an OS X Lion (10.6.8) issue. I think it is an Airport software issue. I just had the very same problem appear under Snow Leopard 10.6.7 on two separate LAN WiFi networks, one in Albuquerque and another in Sacramento. I've been able to replicate the problem on the two different networks:
Albuquerque (new Airport Extreme with Qwest/Motorola DSL modem)
1. Upgraded Airport Utility to v7.5.2.
2. Added a new Airport Express to extend (5GHz) Airport Extreme signal for network 1 (Albuquerque).
3. WiFi network worked for a few minutes and then ground to a halt. WiFi dead on Macs, Windows 7 and Vista PCs, iPhone 4s and iPads.Network down for a couple of days, trying to fix it. We finally had to disconnect the Airport Express. Choosing "extend a network" is the problem...
Sacramento (2nd generation Time Capsule with old, Comcast Scientific Atlanta or new RCA DOCIS 2.0 modems)
1. Upgraded Airport Utility to v7.5.2.
2. Added a new Airport Express to extend (5 GHz) Time Capsule signal for network 2 (Sacramento).
3. WiFi network worked for a few minutes and then ground to a halt. WiFi dead on Macs, iPhone 4s and iPads. After a few minutes, even Ethernet access died — the router kills the DSL or cable modems since they get caught in a communications loop. This network also went down for a couple of days. We finally had to disconnect the Airport Express. Choosing "extend a network" is the problem...
4. To test this theory, I reconfigured a second Time Capsule on this network from Wireless "Off" to extend the network.
5. Same problem — network fails and the main DHCP router can't communicate with the cable modem. Even Ethernet died.
When this occurs, the network slows to a crawl. Web pages stop loading or take minutes to load. You can't communicate with the "extended" routers at all — they get stuck while Airport attempts to read or save the Airport configuration file. Disconnecting them is the only option. Even resetting these devices doesn't work properly.
Three different people configured these networks and we all had the same problems. Apple, you have a problem.
Currently Being ModeratedJul 24, 2011 4:50 AM (in response to Pagemakers2)
I have an Airport Extreme and the problems stated above are excatly what I am having.
Currently Being ModeratedJul 24, 2011 5:26 AM (in response to KLNG)
No need to disable AFP. This is resolved by simply unsharing your home folder (presuming it is shared).
The home folder is automatically shared in Lion.
Currently Being ModeratedJul 24, 2011 5:47 AM (in response to spettinger)
spettinger: Your suggestion worked for me. Many thanks
Currently Being ModeratedJul 24, 2011 5:51 AM (in response to BigChops)
BigChops: This works too. The home folder was shared by default. Many thanks again to everyone who has contributed
Currently Being ModeratedJul 24, 2011 7:40 AM (in response to BigChops)
This worked for me too. So simple when you know how. 1 minute's work solved it after spending all day yesterday, playing around with every other setting I could think of and trying every different method of getting my Macs to talk to each other.