none
Alternative Access Mapping in SharePoint 2010 or 2013

    Question

  • Hi Folks,

    I created a http://testsite.com on our SharePoint 2013 server and its been registered in DNS too. But Its not accessible from out side of the network..like from my local computer/laptop. Are there any steps should be followed in Alternative access mapping. Please let me know in detail.. It will be good, if you type the steps instead the links. So that, it will be crystal clear for us...

    Thanks in Advance,

    Ronan

    Thursday, July 25, 2013 10:51 AM

Answers

  • Any additional access mappings you add to a web application that is NOT extended, you need to manually add a corresponding binding in IIS.  

    Web App A:
    ------------
    Default zone: www.abc.com (you extend the web application and you select custom zone for www.123.com)
    Custome zone: www.123.com

    Both of the above URLs will be added to IIS

    Web App B:
    -------------
    Default zone: www.chicken.com (you manually add an additional access mapping in intranet zone called: www.cow.com)
    Intranet zone: www.cow.com <-- would require you to manually add this to IIS binding

    The are many different purposes for AAM.  From SSL offloading to authentication to just wanting multiple URL's for the same site.


    MCITP-EA | "Never test how deep the water is with both feet"

    • Marked as answer by ronan22 Thursday, August 01, 2013 6:29 AM
    Saturday, July 27, 2013 2:19 PM
  • > why do we use AAM?

    suppose that your site is accessible by url http://example.com, and you want to make it accessible also by http://example1.com. First of all you need to configure DNS and IIS bindings, but it is not enough. Without AAM when you will open your site using http://example1.com url, internal links on html page will point to http://example.com. In most cases it means that when users will click on these links they will get http 401
     unauthorized exception (or browser won't load the target page at all, because url http://example.com may not be public url). In order to fix all links in html output to the correct http://example1.com you need to add AAM.

    From my experience, in Sharepoint 2007 and 2010 it was possible to open site by another url without AAM (just all links were broken in this case), but in Sharepoint 2013 site is not opened at all without AAM: it shows Oops, something went wrong problem. Here is good guide:

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


    Blog - http://sadomovalex.blogspot.com
    Dynamic CAML queries via C# - http://camlex.codeplex.com

    • Marked as answer by ronan22 Thursday, August 01, 2013 6:30 AM
    Monday, July 29, 2013 8:36 AM

All replies

  • Do you mean outside of the network as in from home or somewhere? If so, then no that won't work as you would need to purchase the domain name "testsite.com" which is very unlikely to be available, and then point that domain name to your external IP address with port forwarding to your SharePoint server. I can give further details as to how to do this if this is what you are meaning?


    Brendan Lee

    Thursday, July 25, 2013 10:59 AM
  • Thanks for the reply. Let me clear few points.

    1. The name of  the site is not  http:\\testsite.com. Its an example..I cant provide the real site name.

    2. I am testing on my test server. We have separate AD team. So the test SharePoint server and the domain, site info registered in DNS too.

    3. Network means, Yes its a private network. But even we can access through VPN right.

    4. We are accessing the site from the same domain only but not on the SharePoint server. From our office computer.

    What I am looking for is, create a test site on your sharepoint test server and register in dns and access form a local computer. Here, how do I configure the alternative mapping.

    For suppose: I created http\\welcometosharepoint.com on a sharepoint test server

    Actual Result- Its opening on the same server

    Expecting Result- We need to open the same site from our local desktop/laptop

    Thursday, July 25, 2013 11:36 AM
  • hi

    before to start investigate alternate access mappings your domain name should point to the correct IP address. Try to ping "testsite.com" domain name and see will it show IP address of the correct server. If it doesn't DNS doesn't work properly. If it is - your next step should be adding of host header in the IIS manager for the Sharepoint site (choose the site from the left tree and then click Bindings on the right panel of the IIS manager. Then click Add: type = Http, IP address = All Unassigned, Port = 80, host name = testsite.com). And only after that go to CA and add alternate access mapping for testsite.com.


    Blog - http://sadomovalex.blogspot.com
    CAML via C# - http://camlex.codeplex.com

    Thursday, July 25, 2013 12:10 PM
  • Thanks. But I have the idea of IIS bindings. Could you please let me know the steps of configuring Alternative access mapping in CA.

    Friday, July 26, 2013 9:29 AM
  • Go to Central administration -> Configure Alternate Access Mappings -> Select your Web Application from the drop down, then enter the full URL of the AAM.

    Trevor Seward, MCC

    Follow or contact me at...
      

    This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

    Friday, July 26, 2013 1:45 PM
  • Guys Thanks for your inputs. But still I haven't recevied any proper answer from anybody.

    I understand the navigation steps in AAM, but my question is why do we use AAM? What purpose? Secondly I need the sequential steps to configure AAM.

    For example: From IIS binding to till configure AAM in Central Administration. Anybody can answer this in-detail? Please share..at earliest.

    example of a site name is: http://welcometosharepoint2013.com...(shoud be accessed from outside of the server too)

    thanks in advance

    Ronan

    Saturday, July 27, 2013 10:29 AM
  • I will suggest you to take a look at this AAM configuration guide

    http://gallery.technet.microsoft.com/The-final-guide-to-551bd75b



    Mark ANSWER if this reply resolves your query, If helpful then VOTE HELPFUL
    Everything about SQL Server | Experience inside SQL Server -Mohammad Nizamuddin

    Saturday, July 27, 2013 10:41 AM
  • Any additional access mappings you add to a web application that is NOT extended, you need to manually add a corresponding binding in IIS.  

    Web App A:
    ------------
    Default zone: www.abc.com (you extend the web application and you select custom zone for www.123.com)
    Custome zone: www.123.com

    Both of the above URLs will be added to IIS

    Web App B:
    -------------
    Default zone: www.chicken.com (you manually add an additional access mapping in intranet zone called: www.cow.com)
    Intranet zone: www.cow.com <-- would require you to manually add this to IIS binding

    The are many different purposes for AAM.  From SSL offloading to authentication to just wanting multiple URL's for the same site.


    MCITP-EA | "Never test how deep the water is with both feet"

    • Marked as answer by ronan22 Thursday, August 01, 2013 6:29 AM
    Saturday, July 27, 2013 2:19 PM
  • > why do we use AAM?

    suppose that your site is accessible by url http://example.com, and you want to make it accessible also by http://example1.com. First of all you need to configure DNS and IIS bindings, but it is not enough. Without AAM when you will open your site using http://example1.com url, internal links on html page will point to http://example.com. In most cases it means that when users will click on these links they will get http 401
     unauthorized exception (or browser won't load the target page at all, because url http://example.com may not be public url). In order to fix all links in html output to the correct http://example1.com you need to add AAM.

    From my experience, in Sharepoint 2007 and 2010 it was possible to open site by another url without AAM (just all links were broken in this case), but in Sharepoint 2013 site is not opened at all without AAM: it shows Oops, something went wrong problem. Here is good guide:

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


    Blog - http://sadomovalex.blogspot.com
    Dynamic CAML queries via C# - http://camlex.codeplex.com

    • Marked as answer by ronan22 Thursday, August 01, 2013 6:30 AM
    Monday, July 29, 2013 8:36 AM
  • Thanks all for your inputs..


    • Edited by ronan22 Thursday, August 01, 2013 6:31 AM
    Thursday, August 01, 2013 6:30 AM