Take the 2-minute tour ×
SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. It's 100% free, no registration required.

I need help and it would be great if anyone suggest/help.

The Problem is:

We added a blog sub-site in a SharePoint 2010 publishing site. now the site is browseable in the authoring version. But it is showing 401 on the public facing, the URL is

http://wwwqa.nextdocs.com/en-us/blogs/default.aspx

instead http://wwwqa.nextdocs.com/ is working.

Do you have any idea how to make the blog site available in the public facing. Well appreciated for help.

share|improve this question
    
I got a 503, then a 404, then the SharePoint 2010 error trying to get to wwwqa.nextdocs.com/en-us/blogs. Something weird is going on.. :/ –  Kit Menke Apr 6 '12 at 14:18
add comment

2 Answers 2

My guess would be that only anonymous access is enabled on this Web Application (configurable within "Authentication Providers"), and that the sub site has anonymous access disabled (go to the permissions of the sub site to change this).

share|improve this answer
    
Thanks for reply. No we are not using a reverse proxy like ISA Server. How to enable anonymous access for subsite. Any idea? –  Feroze Apr 10 '12 at 7:37
add comment

If you are using a reverse proxy like ISA Server 2006 you likely need to add the new sites to the "public names" tab.

Here is an example of the dialog.

enter image description here

share|improve this answer
    
I'm not sure that's correct - my understanding it that the public site tab is for distinct host names and IP addresses. The examples above are "Paths" in my opinion. In any case the OP didn't mention a proxy server. –  Benjamin J Athawes Apr 6 '12 at 16:40
    
Without them in that dialog I am unable to access them from outside the LAN and I receive a 401 unauthorized error. With them in that dialog, I am able to access them fine. Each is a separate site collection. So it is not really a matter of opinion. –  Robert Kaucher Apr 6 '12 at 19:22
    
@Benjamin - This wasn't always the case for us. So that might be why it isn't in line with your experience. When we were using HTTP internally we did not need to place individual site collections in that tab. it was only after we switched over to HTTPS and modified the AAMs accordingly. I'm not certain off had exactly what change we made that required that, but I am certain that within our configuration we get 401 unauthorized if the site collections are not explicitly defined there. –  Robert Kaucher Apr 6 '12 at 19:49
1  
FWIW I have managed a farm with 1000 + site collections and a dozen or so Web apps available over SSL and have never had to manually alter that tab so it may be a AAM issue. We have gone off on a tangent from the OPs question though :-) –  Benjamin J Athawes Apr 6 '12 at 20:26
add comment

Your Answer

 
discard

By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.