Philippe - Swiss said:
Dear Robert Aldwinckle,
Thank you very much for your valid feedback!
Yep, this was indeed a typo (correct = shdocvw.dll) and now
it was able re-register it correctly too (but error still persisting!).
So, and then I tried to use this software from this German MVP
...but after having performed the whole scanning, this URL of
mine (
www.juliusbaer.com) can still not be displayed; yaks!!
But I think that it's more likely that this URL is "somewhere" being
blocked on my IE6 (but NOT on Firefox!), rather than being a DLL
problem or so, since up to now it's really the ONLY single site I'm
encountering this kind of problem...what you think??
It's possible that the request that IE is building is somehow not to the
liking of that site and it is just not responding to it.
If you can get the URL showing in the Address bar
try pressing Ctrl-F5 to repeat the request as a refresh.
That site has a Cookie which gets sent in with the request too
so if the Ctrl-F5 idea isn't sufficient, try finding the Cookie
for that site and delete it.
If that's not sufficient I would also try modifying your Language settings
at least temporarily as a test. E.g. IE sends in this with my request
<example>
Accept-Language: en-us
</example>
I'm using IE7b2; however I used FiddlerTool to spoof an IE6 User-Agent
so that at least proves that the site would not be ignoring your request
from that perspective.
Synchronicity? Just yesterday someone else had a related problem
which was caused by a corrupted User-Agent string, apparently
caused by a bad uninstall of the Maxthon IE add-on.
Let's take a look at your User-Agent. E.g. in an IE Address bar enter:
javascript:navigator.userAgent
(Note: the property name is case sensitive.)
In the problem scenario the user's OS information was replaced
by just the *platform* Win32 and that apparently was not to the
liking of the site that the user was trying to reach.
Alternatively, and in case there is something in the path to the site
which is modifying your User-Agent string, you can try this diagnostic
site:
http://www.fiddlertool.com/useragent.aspx
Notice that that site also provides a .reg file which could be used
to restore an IE6 User-Agent--usually used to allow an IE7 user
to spoof an IE6 User-Agent but I think it may be equally valid
for helping an IE6 user to repair theirs.
Frank and nass are correct that malware (e.g. spyware) could be causing
this symptom and that could explain why Firefox works but not IE6.
As for why only this particular site has a problem under that hypothesis
it could be several things. E.g. perhaps the spyware is only targeting
certain sites such as financial services or perhaps this site is normally
slower for you and the added delay caused by the spyware is enough
to cause the whole request to fail, etc.
You could try using FiddlerTool in hopes that you could detect where
your request is going but depending on the sophistication of the spyware
it might notice the diagnostics being used and just stop intercepting.
Then going there through FiddlerTool would be a workaround for you! <w>
HTH
Robert
---