Secure Pages 'NOT'

[MikeM]

Please help someone!
I use a Windows XP Pro and IE 6 and have, up until
recently, been using Norton Antivirus. I recently change
to McAfee Antivurus and Firewall because of the problems
that Norton caused with my new Dreamweaver 2004 Edition.
Since (I think) loading McAfee I have been unable to
see "Secure Pages" like those used by mail order
companies fro payments etc. All I get is the
standard 'Page not available' page. I spoke to McAffe who
told me to disable the AntiVirus and Firewall, which I
did, but this made no difference. They suggested that I
speak to my ISP (Demon UK-THUS) and I spoke to a very
helpful person who asked me to check my ADVANCED page in
TOOLS (IE6). He went over the settings with me and
suggested that all looked ok. He asked me to check HELP
and my "Cyber" level which was fine. He was at a complete
loss but suggested that I go to the Microsoft site and
download any IE6 upgrades. I just did that and loaded the
latest patch to my hard drive. I then tried to RUN the
upgrade program but it informed me that it was unable to
use my current proxy server settings...whatever that
means..PLEASE HELP!
Mike

 

[Michael Solomon \(MS-MVP Windows Shell/User\)]

The problem is likely a setting in the firewall. No way to know for sure
which one, at least for me since I don't use that firewall but check the
firewall options and start enabling things that are disabled and or blocked
one by one and then return to the sites. By the way, you'll need to clear
the cache each time as well as follows: Open IE, go to tools, select
Internet Options, on the General tab, click Delete Cookies, Delete Files,
accept the option to clear all offline content and Clear History. This is
necessary because any blocked pages left in the cache could show up instead
of the site if you don't clear the cache first.

This problem is not an XP problem. Note, it began when you install McAffee,
it's something that application is blocking.

It's not uncommon to have a firewall be the cause of this type of issue but
usually it's because of something the user has blocked and not something
blocked by default by the firewall which appears to be the case here.