hangs on updating financial information

I've been trying all sorts of different things, and still no joy - turned off the firewall, the virus scanner, etc Schwab - NG, all other accounts - OK

Also, have the new IE 7.0 loaded.... in case they might have hosed Schwab.

BTW - Brought up a protocol analyzer, and it seems to just be ping-ponging packets for 443 to ofx.schwab.com which is the SSL web port vs port 80

All the other accounts access their hosts the same way - but they work ok

222 9668 body

I've been trying all sorts of different things, and still no joy - turned off the firewall, the virus scanner, etc Schwab - NG, all other accounts - OK

Also, have the new IE 7.0 loaded.... in case they might have hosed Schwab.

BTW - Brought up a protocol analyzer, and it seems to just be ping-ponging packets for 443 to ofx.schwab.com which is the SSL web port vs port 80

222 9668 body

I've been trying all sorts of different things, and still no joy - turned off the firewall, the virus scanner, etc Schwab - NG, all other accounts - OK

Also, have the new IE 7.0 loaded.... in case they might have hosed Schwab.

BTW - Brought up a protocol analyzer, and it seems to just be ping-ponging packets for 443 to ofx.schwab.com which is the SSL web port vs port 80

All the other accounts access their hosts the same way - but they work ok

ok - it's 1:20am - time for bed :) but the problem appears to be something blocking access to the Schwab website from one laptop. The protocol analyzer showed the target website is -

I even un-installed IE 7.0 in case something was internally modified The two laptops are sitting side by side - both with IE 6.0 running I typed the URL - - and......the home laptop brings up the Netscape install page,and the travel laptop does not display the page - it is like it is beingfiltered somehow... So... I guess I'll have to try and see what the heck is going on - BTW - the normal Schwab website comes up just fineusing SSL

WELL - ok, it's now 2:45am - the resolution was a checkmark for SSL 2.0 in the IE 6.0 / tools / internet options / advanced / So how does that interface with the usage of Quicken ????

Phil:

Are you saying there IS or IS NOT a checkmark by SSL 2.0? I have checkmarks by both SSL 2.0 and 3.0, and Schwab works fine on my desktop.

Bob

WELL - ok, it's now 2:45am - the resolution was a checkmark for SSL 2.0 in the IE 6.0 / tools / internet options / advanced / So how does that interface with the usage of Quicken ????

There was no checkmark for SSL 2.0 - and it failed I then checked it - and IE 6.0 worked - as did Quicken 2004.

BUT - if this is for some "internet access API filtering", vs just for IE 6.0 access settings, then the other weird thing is that the Firefox browser worked fine on the same laptop... Accessing the Schwab OFX site with IE failed, but Firefox worked...

Phil:

Good job figuring out the glitch. Good to know the special handshakes needed to make everything behave.

Bob

BUT - if this is for some "internet access API filtering", vs just for IE 6.0 access settings, then the other weird thing is that the Firefox browser worked fine on the same laptop... Accessing the Schwab OFX site with IE failed, but Firefox worked...

The settings in IE are the important ones as Quicken uses them instead of FF even if FF is your default browser.

Since the only thing that changed in this scenario was the install of IE 7.0 beta2, on XP/SP2. I'm wondering if IE 7.0 turned on SSL 3.0 and turned off the SSL 2.0 checkbox. Now that I know what to look for, I think I'll go back and re-install IE 7.0 and see what happens.

I just checked my IE6 settings and I have both ssl 2.0 and ssl 3.0 checked and my schwab accounts download fine. I do have TLS disabled. For security, all zones are set at the default level.

You might deactivate the account and try reactivating it.

Phil,

As you already knew, Quicken uses the IE engine for all of its internet access. The Tools | Options | Advanced tab governs the behavior of that engine and any applications that use it.

PCT 1.0, SSL 2.0, SSL 3.0, TLS 1.0, and now TLS 1.1 are all security suites providing encrypted transport of data between client PC's and remote servers [1]. Your settings should be SSL 3.0 and TLS 1.0 enabled. PCT 1.0 & SSL 2.0 disabled. Also, check the box instructing IE to not save encrypted pages to disk. Note these are not the defaults. IE versions through IE 6 SP2 enable SSL 2.0, not TLS and _do_ cache pages received via https.

PCT 1.0 and SSL 2.0 have been deprecated due to vulnerability to attack. A quick search did not reveal the exact date or the authoritative document but enough results to believe they are no longer reliable.

It would be a significant concern if Schwab did not work with SSL

3.0 or TLS 1.0.

//Tom S. [1]

> There was no checkmark for SSL 2.0 - and it failed

FWIW, I tried disabling SSL 2.0 and both Bank of America and CS would not download my transactions. When I enabled ssl 2.0 it worked again. So it looks like CS is using SSL 2.0 at the moment and have not advanced to using

3.0 yet.

Here is an email update from Schwab - regarding Quicken downloads from their site.

I spoke to Technical Support and was advised that you are correct, and we are aware that at this time our site only supports IE SSL 2.0.

We have forwarded your comments to the Web Development Team for further review in future enhancements.

ofx.schwab.com