locked
How can I make my MOSS site available externally (Internet)? RRS feed

  • Question

  • Firstly, apologies, I have tried using the search, but it returns zero results regardless of what I search for!

    I am trying to make a MOSS site accessible (over https) via the Internet for users who are authenticated in my AD. MOSS is running on Server 2008.

    The following steps have been undertaken:

    1. Created a web application running on port 15000.
    2. Added an https binding (via IIS) to the web site on port 15001 and created a certificate
    3. Added an AAM for the Internet zone of https://portal.mycompanyname.com for the 15000 site collection
    4. Had the network admin add a DNS entry for https://portal.mycompanyname.com which points back to https://myservername:15001

    What happens?

    1. The website can be accessed externally, but URLs never resolve to the default page e.g. after authenticating the user receives an error trying to access https://portal.mycompanyname.com however if they append '/default.aspx' the page displays correctly.
    2. Some navigation works correctly, however in some (or all) cases where a source URL is passed in the URL it appends the port number 15001 to https://portal.mycompanyname.com which fails to redirect the user successfully upon completing an action e.g. uploading a document or adding a list item.

    I have read many different accounts on how to achieve external access & have also tried extending the web application with similar results. Some suggest that making changes manually in IIS (bindings etc) is not recommended and unnecessary. I am not an IIS expert and wonder if there are any differences in IIS 7.0 / Server 2008 which make some of the things I read redundant? Essentially however I'm looking for the missing link that will address the issues described above.
    • Edited by BarryC1976 Tuesday, November 10, 2009 11:16 PM even sillier typo
    • Changed type Mike Walsh FIN Wednesday, November 11, 2009 4:02 AM always use the question type so people get credit for their replies to you
    Tuesday, November 10, 2009 10:51 PM

Answers

  • Hi,

     

    From your post, it seems that your alternate access mapping isn’t correct.

     

    Alternate access mappings enable a Web application that receives a request for an internal URL, in one of the five authentication zones, to return pages that contain links to the public URL for the zone. You can associate a Web application with a collection of mappings between internal and public URLs. Internal refers to the URL of a Web request as it is received by Office SharePoint Server 2007. Public refers to the URL of an externally accessible Web site. The public URL is the base URL that Office SharePoint Server 2007 uses in the pages that it returns. If the internal URL has been modified by a reverse proxy device, it can differ from the public URL.

     

    When a user browses to https://www.contoso.com, the Web request will be received by the reverse proxy server and forwarded to http://sharepoint.perimeter.contoso.com. Office SharePoint Server 2007 will then receive the Web request, see that the URL of the request is http://sharepoint.perimeter.contoso.com, find that this URL is assigned to the Contoso Web application, and return the content from that Web application. In addition, because the http://sharepoint.perimeter.contoso.com URL is assigned to the Internet zone, Office SharePoint Server 2007 will generate links on the pages by using the public URL for that zone: https://www.contoso.com. This ensures that end users are taken to the proper URL when clicking links on the page.

     

    Please double check the internal URL and public URL, make sure they are both right.

     

    For more information about alternate access mapping, please refer to the following article:

     

    What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

    http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx

     

    Plan alternate access mappings (Office SharePoint Server)

    http://technet.microsoft.com/en-us/library/cc261814.aspx

     

    Hope this helps.

     

    Rock Wang


    Rock Wang– MSFT
    Thursday, November 12, 2009 2:31 AM

All replies

  • >Firstly, apologies, I have tried using the search, but it returns zero results regardless of what I search for!

    If this happens again, use Google (or Bing) Search and restrict where it will search with a site:http://social.technet.microsoft.com/Forums/en-US/sharepointadmin addition after the search string.

    FAQ sites: (SP 2010) http://wssv4faq.mindsharp.com; (v3) http://wssv3faq.mindsharp.com and (WSS 2.0) http://wssv2faq.mindsharp.com
    Complete Book Lists (incl. foreign language) on each site.
    Wednesday, November 11, 2009 4:04 AM
  • Hi,

     

    From your post, it seems that your alternate access mapping isn’t correct.

     

    Alternate access mappings enable a Web application that receives a request for an internal URL, in one of the five authentication zones, to return pages that contain links to the public URL for the zone. You can associate a Web application with a collection of mappings between internal and public URLs. Internal refers to the URL of a Web request as it is received by Office SharePoint Server 2007. Public refers to the URL of an externally accessible Web site. The public URL is the base URL that Office SharePoint Server 2007 uses in the pages that it returns. If the internal URL has been modified by a reverse proxy device, it can differ from the public URL.

     

    When a user browses to https://www.contoso.com, the Web request will be received by the reverse proxy server and forwarded to http://sharepoint.perimeter.contoso.com. Office SharePoint Server 2007 will then receive the Web request, see that the URL of the request is http://sharepoint.perimeter.contoso.com, find that this URL is assigned to the Contoso Web application, and return the content from that Web application. In addition, because the http://sharepoint.perimeter.contoso.com URL is assigned to the Internet zone, Office SharePoint Server 2007 will generate links on the pages by using the public URL for that zone: https://www.contoso.com. This ensures that end users are taken to the proper URL when clicking links on the page.

     

    Please double check the internal URL and public URL, make sure they are both right.

     

    For more information about alternate access mapping, please refer to the following article:

     

    What every SharePoint administrator needs to know about Alternate Access Mappings (Part 1 of 3)

    http://blogs.msdn.com/sharepoint/archive/2007/03/06/what-every-sharepoint-administrator-needs-to-know-about-alternate-access-mappings-part-1.aspx

     

    Plan alternate access mappings (Office SharePoint Server)

    http://technet.microsoft.com/en-us/library/cc261814.aspx

     

    Hope this helps.

     

    Rock Wang


    Rock Wang– MSFT
    Thursday, November 12, 2009 2:31 AM