User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.12) Gecko/20050915 Get the foregoing error when attempting to access my account with the account name and password for that account. DO NOT get the error if I immediately try to access with Internet Explorer. Checked with webmaster and they are not reporting any problems. This also occurred starting last week with Mozilla (not suite) and I downloaded and installed the Suite to replace it and Eudora. Reproducible: Always Steps to Reproduce: 1. Access the web site. 2. Enter account name and password as usual 3. Actual Results: Get the error message. Expected Results: Should have gone to my bank account information. Call me at 800-486-9329 if you want me to try something.
Was that a message from the Operating System, or a message on an error page from the server? I found a few references to local hb.exe processes (everything from TrojanDropper.Win32.Small malware to the "Handy Backup" product), but in reference to online banking https://ibs.secure-banking.com/cgi-bin/hb.exe seems to come up quite a bit. I'm going to assume "error page from server" for the remainder of this comment. Do you block cookies? Apparently this can be one cause of this message http://www.ocnb.com/hbfaq.htm#What%20Internet%20browser%20can%20I%20use? Other sites said something about Java, but I didn't see any applets involved. I'm not sure what product you mean by "Mozilla (not suite)". Mozilla generally refers to the Suite (more recently continued on as a community project called "SeaMonkey"). Do you mean Firefox? Which version? (version wouldn't matter if it's the cookie thing mentioned above). What changed on your system between when it worked and when it didn't? Did you install other software, plugins, or extensions? Did you change any settings? There may or may not be a mozilla bug here (I'm thinking not), but there's definitely no mozilla security exploit described here. I think we should clear the security-confidential flag to get more potential people involved in finding the solution.
Never got the additional info we'd need.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.