There's NOTHING you SHOULD do to resolve the message (unless you want to disable ALL security).
When someone decides to officially put SSL on their web server, they need a 'purchased certificate' from a 'certificate authority' like Thawte, Verisign, etc.
The 'domain name' assigned to the certificate MUST MATCH the 'domain name' given in the application at the time they purchase the certificate. Certificates usually are in the $100 to $300 range depending on WHERE (what certificate authority)you get them from.
So, what happens (sometimes) is a company (say techrepublic.com) decides they want SSL, and apply using the domain name 'secure.techrepublic.com' or something....
Then for some reason later they decide they want to use that certificate on 'techrepublic.com' WITHOUT the secure. in front. That CAN cause the error you describe, but IN THIS CASE is no concern for alarm.
Another scenerio would be 'johns.domain.com' using a forged certificate from 'someother.domainname.com'(NAMES DON"T EVEN COME CLOSE) -- then there IS cause for concern and you should probably DENY access in THIS CASE!
See what I mean... It's another internet 'screwed-up' thing. It's really up to you to decide (based on the domain names, and using common-sense) whether to allow the certificate or not!
You CAN disable IE from checking for this, but I'm NOT going to recommend it or explain how because you shouldn't do it.
Good Luck,
Hope this helps you understand WHAT'S going on :)
Steve
