Update: i have surfed the site with firefox and thus all was well.
i am making a few modifications to this article.
you dont need to enter the authentication nor change the provider from windows.
all you have to do is check the checkbox of anonymous access.
well it is working in FireFox but i cant get beyond the 401 in Internet Explorer.
Tried forms and any other authentication but for now they all seem to behave the same.
i even enabled anonymous login in the Internet Explorer security menu but it just expediates the display of the 401.
This guide is the extention of a Guide by Mark Harrison on configuring anonymous access to a Site in SharePoint 2007.
First you have to go to the administration site of the SharePoint server(You can look for its port in the IIS configuration on your server machine.)
after logging you will have to go to
1. Application Management (Tab or left list item).
2. Choose from application security the Authentication Providers item (on the right hand side of the screen)
3. Enable the Anonymous authentication.
Save the changes.
You might want now to restart the IIS. i found it saves time thinking what went wrong
4. Close the browser and open a new one pointing to the website you want to enable anonymous access.
5. In Site Actions (top right) open the sub menu Site Settings and in it choose Modify all Site settings
6. Under Users and Permissions choose Advanced Permissions
7. In the page choose Settings -> Anonymous Access
8. All that is left now is to set the level of access the Anonymous users will have to the site
Hope this one will save all of you the time i spent getting it done.
Enjoyed this article?
Follow me on twitter @yuvalararat!
{ 11 trackbacks }
{ 13 comments… read them below or add one }
I have tried this method but the Anonymous Access menu setting still does not appear. It is still the default menu item of ‘Access Requests’.
Any idea on the cause of this?
After following these instructions and then reloading my test portal, I get the error “401 Unauthorized” without any type of login prompt. Any ideas about how to fix this?
I might have forgot some thing.
let me update it.
Its really good but would appreciate if you can provide with authentication.aspx
you will be able to find authentication.aspx in the admin template foler at you server.
Most probably “C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\TEMPLATE\ADMIN”.
Gordon Dalgleish – I had the same problem. What you need to do is – after clicking “Advanced Permissions”(see above) and you have to select the member provider name, make sure that you have the correct Web Application selected (top right of that window). My Web Application was set to :12346 but my site was on :80. Click that and select change Web Application and select the correct one you are working on.
I have done all of this as it says, but I still get prompted for login name and password when going to to the site. Not sure what I missed.
I have done everything in this article. But, it didn’t work. It prompts for a login and password when I go to the site.
I have done everything in this article. But, it didn’t work. It prompts for a login and password when I go to the site.
i see that many of you have not been able to make it in the latest version of the Share Point.
Is it correct that you have done it in a newer version?
Our 401 issue was due to there still being the original “Default Website” in IIS. Yes the “Default Website” is “Stopped” after creating and extending a new MOSS site on Port 80, but this site still gets in the way of Anonymous Access on Port 80.
Delete the “Stopped” “Default Website” and Anonymous access miraculously starts working.
~bozo
Thanks budy,
I forgot that….you remember me and save my time.
Kuldeep Kadyan
I deleted the default IIS site and still get the 401 error on all subsites. The main site allows anon access, but subsites give a 401 error. I have also tried setting the subsites to allow anon access, but they should have inherited this anyway. Doesn’t matter, it still doesn’t work on subsites and I still get 401 error. Has anyone had an issue with subsites and overcome it? Again, the root site correctly allows anon access, but subsites give 401 error.