02-10-2012 01:10 PM
Thanks all,
I will watch the thread and future updates for a fix.
David
02-10-2012 01:47 PM
David,
At this stage, that is about all we can do -- wait as patiently as one can for a solution that we expect to be coming out shortly.
This said, though, I find it hard to understand why this is turning out to be so troublesome as it seems to be turning out to be, considering that this very same issue came around with NIS 2011; considering that it was so extensively discussed in these forums; and considering that a patch was then applied that successfully resolved the issue.
In a few words: The problem is not new, a solution had been previously found, what makes it appear to be so difficult to apply now about the same remedy as before?
If something was lost (or not properly added) to this most recent update 19.5 of NIS 2012, like it seems to be the case, since the previous versions 19.0, 19.1 and 19.2 all were doing fine on this issue, what may be hampering a quicker resolution?
Or what am I missing?
Lin Yu
02-10-2012 02:42 PM
<< In a few words: The problem is not new, a solution had been previously found, what makes it appear to be so difficult to apply now about the same remedy as before? >>
There's a logical fallacy there I'm afraid; if the same remedy worked it would not need to be applied since it would be there already!
What I see is that there is a different trigger -- which might be related to increased Bank security for example; I know my BoA was almost impossible to log into the Password box for more than a week about 10 days ago so they may have changed something at their end.
I'm not saying that is actually it but just that if it were simple Norton would have done it ages ago. They don't like this situation any more than you all do!
I've had repeated experience, including with Norton products, of the Law of Unintended Consequences where a third party changes something (or in the Norton example failied to change to a later Microsoft standard) and all logic indicates the fault is with Norton .... until one finds out where the change took place!
02-10-2012 02:46 PM
One gets the impression that the bank techies intentionally seek to defeat auto-logins to assure liability for transactions rests with customers. Trouble is - like all institutions, they are consumed with their own self-importance: they don't grasp that if I call up my encrypted passwords list I have to scroll down 613 separate logins!
/Diatom
02-10-2012 04:27 PM
Folks, It appears that the problem is with any site with a 2 page login. For example, in addition to banks, the login to Vanguard.com (2 pages) also no lonfer gets filled in. It is impossible to believe all 2 page login sites somehow conspires to defeat Norton. The problem has to be Norton's.
02-10-2012 04:52 PM
"One gets the impression that the bank techies intentionally seek to defeat auto-logins to assure liability for transactions rests with customers. Trouble is - like all institutions, they are consumed with their own self-importance: they don't grasp that if I call up my encrypted passwords list I have to scroll down 613 separate logins! "
Absolutely agree - good comment Datum
I have a second computer with NIS 18.7.0.13 ruinnning Win XP SP3 and the Log In ID works fine with all sites including the bank sites that I cannot access with NIS 19.5.0.145 on my Win 7 - 64 bit.
I provide this not to criticise Norton, just to add information to help them solve the problem.
02-10-2012 06:42 PM - edited 02-10-2012 06:44 PM
Just a note that mozilla has released a critical security update from ff 10.0 to 10.01 to fix a security issue for more info go to https://www.mozilla.org/security/announce/2012/mfs
02-10-2012 09:09 PM
Hi Folks,
There have been some parts of ID safe which had design changes in 2012. As a result I don't know if the same fix as was applied in 2011 and earlier can be directly applied to 2012 - I suspect not.
I realize that the issues with the two page web sites (username/password on different pages) are irritating but I have faith that Norton will resolve these as quickly as possible.
My two cents worth. ![]()
Best wishes.
Allen
02-10-2012 11:27 PM
Not so much a case of "NIS-IDS 2011 worked flawlessly" - it had its limitations too - I have multiple personal/business accounts at two separate banks - both of them (Mozilla/NIS2011) accumulated each login as a new credential, offering a dropdown list apparently comprising every instance of login prior! Inelegant, though workable. I can't imagine the 2012 team is unaware of the issue as they grapple with the new bank-bounce problem.
02-11-2012 03:10 AM
AllenM wrote:Hi Folks,
There have been some parts of ID safe which had design changes in 2012. As a result I don't know if the same fix as was applied in 2011 and earlier can be directly applied to 2012 - I suspect not.
[...]
My two cents worth.
Allen
Allen,
In trying to add my two cents worth to yours...
I beg to disagree... Actually, 2012 worked flawlessly till the day 19.5 came along! As you well know, the issue had been resolved somehow by Symantec's programmers and there was no signs of the issue before we started applying this last upgrade. So, whatever it is and for whatever reason, it is definitely something that resurfaced with the 19.5 version of 2012, and not before...
Again, like someone already wrote before, we are not posting these comments for the purpose of criticizing the people at Symantec who certainly hate these problems at least as much as we all do. But I still believe that the issue resides on the side of Norton's and not on the side of the Banks.
Why?
Taking BOA's example, it was one of those where the issue was present last year, then it started working perfectly AFTER the patch was applied to NIS 2011, no problem with NIS 2012 when it originally came out, and it shows up now again with the 2012 upgrade.
And yes, we all look forward for an early resolution. Patiently. No bad feelings... ![]()
Lin Yu
