i am using norton internet security 2010 with windows 7.
i create a password and save my log ins but the next time i connect to ie8 and login, it says wrong password!!!
i know what the bloody password is i have used it enought times but i have to reset my password and lose all my log ins and re do all of them. then the next time i log in it happens again. looks like i'm gonna have to get rid of norton and use roboform and kaspersky
i am using norton internet security 2010 with windows 7.
i create a password and save my log ins but the next time i connect to ie8 and login, it says wrong password!!!
i know what the bloody password is i have used it enought times but i have to reset my password and lose all my log ins and re do all of them. then the next time i log in it happens again. looks like i'm gonna have to get rid of norton and use roboform and kaspersky
Hi Jduk,
I would suggest that you repost this in the NIS forum at: http://community.norton.com/norton/board?board.id=nis_feedback for better visibility. I have NIS myself and have had on both Windows XP and Windows Vista Ultimate with no problems. I currently have NIS2010 on Vista.
I have never experienced a similar problem. The forum I referenced includes those who are more intimately familiar with NIS and I'm sure can help you solve this problem.
Can you provide the URL of the login page for which the saved login isn't working? If privacy is a concern, feel free to send me a private message. The reason that I'd like to know the page is because this can occur if the login form performs some pre-processing on the username and/or password before it is actually submitted. I have seen some login forms that use JavaScript to convert the username and/or password to different values. These transformations usually occur in response to mouse or keyboard focus events in the page, such as clicking in or out of a text or password field. Since Identity Safe fills the form automatically, with no mouse or cursor focus changes, no preprocessing occurs. The site then rejects the submitted values because they didn't undergo the site-specific transformation. See this thread for some workarounds: