There's nowhere near enough info in the question to provide a sure answer to your problem, but there are clues pointing to possible issues. But since my first version of this, I have been pointed at by someone too polite to call m stupid in public, and that has strong sign of iCloud/SN linkage. Apple cares most about people buying hardware, so the only "piracy" of MacOSX that they interfere with in code is running it on non-Apple hardware. no DRM with keys and mandated validation with the vendor as with Windows. There's no lockdown of an installation of MacOSX to a particular Mac, i.e. non-Apple) hardware it usually has far more severe problems. When MacOSX thinks it is running on dodgy (i.e. Sadly I am out of AppleCare coverage, but maybe a Genius would see the fault is Apple's and re-serialize the board.
Would this affect iMessage/iCloud in Mountain Lion? It worked in Lion despite this. Of note: the serial number listed in About this Mac/System Information is incorrect and does not match the SN on the case (off by one letter–I think it was serialized incorrectly once after the logic board was replaced once). I checked Keychain Access > System for anyīack to My Mac keys to delete.Checked that my time is set, in the correct time zone, and set to.Please check your network connection and try again." Please check your network connection and try again."Īttempting to sign in yields "Could not sign in. Turning on Back to My Mac gives the error "iCloud server not responding." (though it didn't seem to try very hard, looking at the network monitor)Īttempting to sign in yields "Could not sign in to iMessage. I am running Little Snitch (version 3.0.4) though turning it on or off has no effect on these results.
After doing a clean install of Mountain Lion on my MacBook Pro (13" unibody, MacBookPro5,5) and upgrading to 10.8.3 I'm having trouble with iMessage, Facetime and Back to My Mac.
0 kommentar(er)
