12-22-2011 06:51 AM
Thanks very much for the update.
I've been using the onlne ID safe since 2012 came out and apart from the one period I mentioned earlier with the routing problem on the internet I have not had any issues with it.
I believe that something happened the first time you tried to set this up that resulted in the data becoming corrupted in route to the Symantec server. This is not something that I would expect to repeat itself.
So hopefully you won't have any further problems.
As you might expect I would always recommend doing periodic backups of your ID safe such as when you add several new logins or change existing ones. Given the importance of the data contained therein, this is always a good precaution to take no matter how good the ID safe feature is.
Happy Holidays to you as well.
01-24-2012 06:26 AM
unfortunately it is time for me to dig out this old thread again Yep, it is just happening again. Until now everything worked fine, having the vault online and working off it both on the desktop and laptop.
This morning when I wanted to log into the Identity safe in the browser, it asked me to log into my Norton account, which it does from time to time without a problem. But today it will not accept my login. It just won't! So, I went online i.e. via url onto the account.norton webiste and logged in. With the correct and exactly the same credentials I was trying to log into the Norton account part of the Online Identity Safe before. How can that be?!
To summarize: I am logged into my NortonAccount on the web. I am logged into my Identity Safe online vault (https://identitysafe.norton.com/home) on the web, all passwords are there. But I cannot log into my Identity Safe via my Norton account on my desktop application.
What is going on?
Thanks for your help!
01-24-2012 08:28 AM
I am also seeing the same problem. In my case the problem appeared after the live update which required a restart.
We will keep you posted on status as we work with Symantec.
01-25-2012 12:03 AM
This problem has been reproduced and is being worked on by Symantec. Please see the following thread.
Hopefully we will have resolution soon.
01-25-2012 10:49 PM
As indicated in the following post, this latest issue should be resolved now.