Microsoft .net Security Warning : Never enter personal information or passwords ...

Question

So I have an ASP.net application, with an ActiveX Control which brings up a pop up

• When I point to the application directly through IP there is no problem with the pop up eg. xxx.xxx.xxx.xxx/MyApp (under Default Website in the IIS -- IIS 7)
• Problem arises when I set up the IIS to point it to a domain xxx.xxxxx.com which points to the above IP (under another "Site" i.e. not the "Default Site in IIS 7)

I then get this weird

Microsoft .net Security Warning Never enter personal information or passwords into a window unless you can verify and trust the source of the request.

Source: xxx.xxxxxx.com

The site is in the trusted list -- just like when I was using the IP only . Is there any setting in the IIS I need to tweak for IE to trust me fully.

Answer 1

May be you need some Certificate from third party associated with control

Answer 2

Ok, this was interesting me, so I di waht you should have done - google with the message.Got a ton of crappy ansers, but in this i found some explanations:

http://www.codeproject.com/Messages/2882928/how-can-i-suppress-Microsoft-NET-security-warning-.aspx

Basically, you can't disable the warning. You have no control over it at all. The only thign you CAN do is rewrite your control so your code doesn't trip the warning. Your control is doing something, or using something, that is not allowed in the restricted sandbox of the web browser.

So, it is about things you do in the control.

Thhere is a link to a MS support case:

http://support.microsoft.com/?scid=kb%3Ben-us%3B820637&x=8&y=12

But I am not sure it is so helpfull.

Sadly this is all information I did come along with. Is the control digitally signed and the signature trusted by the users?

Oh... and then there is:

http://www.ms-news.net/f1094/net-2-0-apps-think-theyre-being-run-internet-but-theyrebeing-run-intranet-6884147.html

which can relally be it.

Do you happen to use fully qualified domain names to reference the remote machine (ex: server.domain.local)? If so, does the problem go away if you use just the netbios name (server).

Solutions provided, included a link to the relevant MS documentation.