What changes are needed to a public site with anonymous access to avoid name.dll gets executed on the client
I created a product information site and opened this to the public. I customized a master page for my public pages where I removed most of the navigators and menues. I customized the login button to hide it behind the site logo.
Now, if people access the site from IE 7.0 they are prompted to install name.dll or to allow it's execution. The problem seems to exist in IE 7.0 only, I have not seen it with IE 6.0. If you have IE 7.0 you can go to http://notes-development.net to see what I mean.
How can I stop this prompt for annomyous users visiting my site What is the piece of code that needs to be removed from the master page Is this standard behaviour
I'm aware that users can just ignore the message or add the site to the list of trusted sites. But in my opinion this is not a viable solution for a public Web site.
I hope someone has already fixed this.
Regards
Peter
----------------------------------------------------------------
Peter Gloor, Consultant
Notes Development AG
CH-9056 Gais, Switzerland

How to avoid getting prompted to install name.dll or to allow it's execution (IE 7.0 only)
Andrew J
The Mossman has a great post on this issue you should check out:
http://www.sharepointblogs.com/mossman/archive/2007/09/13/fixing-the-name-dll-activex-problem-the-mossman-way.aspx
John
SharePoint911: SharePoint Consulting
http://www.sharepointblogs.com/rossonmoss
Vassilux
I just went to your site using IE7 and was not prompted to run "name.dll"
overthetop
Thank you, Gary.
It looks like it has gone. I can no longer reproduce the error and the colleague who reported the problem cannot reproduce it either. I don't know what solved the problem, a Microsoft Update or my last changes to the site.
When I searched Google and SharePoint related news groups for the issue, I found it mentioned several times, but nobody had a solution for this.
Peter
Kain363399
mathewzhao
Peter, I was just prompted to install name.dll when I visited your site.
I found this post via a google search as I am looking for the solution to this issue, due to a client of mine experiencing this on one of their Sharepoint sites.
It appears that 'techjeff' may have provided the answer though.