The apple Icloud website takes forever to load, and once it does, I cannot access anything (contacts,etc..). I know its something to do with Norton 360 and recent LIVEUPDATES due to the following:
Uninstall Norton 360 (everything works fine)
Reloaded Norton 390 (everything works fine)
My live updates after reload are approx 52 days out of date
Spent an hour chatting and watching a person from Norton make a Norton 360 rule allowing anything to/from icloud. She must have done it before, because I could hardly keep up with what she was doing. When that didn't work she downloaded Google Chrome and tried it. The problem is not there under Google Chrome. Earlier I had tried IE9, IE8 and Firefox. They all show the same symptoms you describe. Prior to contacting Norton, I also determined that if I shut off the Norton firewall, disable the antivirus auto protect, and turn on silent mode I was able to get icloud to work. I am running the latest versions (with all updates) of Norton 360, Microsoft Window 7 Professional, IE9, IE8 and Firefox. Now for the bad news, the Norton support person says the problem is with Microsoft, Apple or Firefox. She would not explain why they all work with Norton 360 turned off. Personally, I think Norton is taking too long to do something and causing timeout problems. Maybe it is time to switch to AVG :-(
<< Now for the bad news, the Norton support person says the problem is with Microsoft, Apple or Firefox. She would not explain why they all work with Norton 360 turned off. >>
I know this sounds like a cop-out but it really and truly can happen and in fact I was part of it happening when N 360 went from V2 to V3 some years ago.
After the upgrade of N 360 the FIle Manager I use, PowerDesk, crashed any time I tried to right mouse click on a file to access the context menu. Remove N 360 and all was OK so obviously it was Norton's fault. It also was reported by other users than me and also for a couple of other applications than PowerDesk, neither concerned with file management.
Then someone discovered that PowerDesk had issued a fix but not told its users; it was just mentioned in a FAQ on their website and once they knew about this Norton pinned down the actual problem:
Microsoft had told its partners, like Norton, that it was updating a protocol in Windows so Norton updated to match (but Microsoft neglected to say that although they were issuing the new protocol they had not adopted it themselves ......) Norton was the odd man out and nothing went wrong until Microsoft caught up with itself and adopted the new protocol ... and the crashes started.
They stopped when PowerDesk users updated with the fix .... Of the other two applications with a similar problem one updated and all was OK and the other was no longer supported so the user changed to something that was more uptodate.
Norton have a close working relationship with Microsoft and other firms so I'd surprised if this sort of error was not being explored jointly but I'll mention it to someone who was involved in what I just described above.
Just became a member of the "Error: 6506, 421" club in addition to Norton's icloud problem. When the chat folks finally come on line, what software do you suppose they will blame that on :-(
Just became a member of the "Error: 6506, 421" club in addition to Norton's icloud problem. When the chat folks finally come on line, what software do you suppose they will blame that on :-(