My business and personal banking is mostly done with chase.com. Up until about a year ago, I had no problem reaching my accounts pages on chase.com (actually, chaseonline.com) with Safari. Suddenly, one day I couldn't log on ... after entering my username/pw, it would chug and chug with a blank browser window, even though the URL showed
https://blahblah/logon=success/blahblah. Then it would say "Done" with a blank screen.
Many many calls to chase.com support were of no avail. No Mac browsers could access the pages. None of the other three macs in the office could get to the accounts page. (Though we could reach other banking sites.) BUT my old Compaq running WindowsXP had no problem with either IE or Firefox. I gave up, thinking it was a mac thing. These days I keep the Compaq on my desk mainly to do my online bills at chase.com.
Fast forward to 2 weeks ago. On my newish MacBook Pro, which couldn't reach chase.com either, I had my trusted local Apple service co. install Bootcamp and Parallels, running Parallels off the Bootcamp partition, bought a new copy of Windows XP etc. I was positive this would solve my chase.com problems ... if Parallels couldn't reach them, booting into Windows sure would. Answer is no!!! Same stupid symptoms. But the Compaq still has no problems.
I posted this to the Parallels forum and many people there said they had no problem reaching chase.com on their Macs, this was not the proper forum for my question, and they referred me to here to diagnose the *mac* problem.
Sigh. Today on a lark I did a search for my problem and found a thread on ebay forums about people who couldn't log on to ebay or paypal with the exact same symptoms. A user there said this:
check your host files.
The only thing listed should be 127.0.0.1 local host
I bet you you have a few sites that are underneath it.
Spyware will redirect your browser, and if the site has been moved, you will get an error page.
to get there go to C:/windows/system32/drivers/etc
open your hosts files, (you may have more than 1 and delete everything after 127.0.0.1 local host
DO NOT Delete Imhosts.sam, do not need to open this host file.
This should work.
Good Luck.
After that post, about 20 people posted things like THANK YOU and I LOVE YOU and YOU ARE MY HERO. That post solved their problem.
So... is there an equivalent file (a "hosts" file) in MacOSX that I should be checking? I'm thinking it *could* be possible that a problem here on one Mac propogated itself to others because I always use the Migration Assistant when setting up new Macs, including my new Intel Mac.
FWIW I've tried connecting via Airport vs. ethernet, normal user account vs. a test account, deleted cookies and private data, increased/decreased security settings, tried Opera and FF and IE and Safari ... nothing is solving the prob.
Thanks...
Cap
Top
