locked
Setting up Alternate Access Mapping. RRS feed

  • Question

  • Hello Experts,

    Recently, I have moved from shared hosting to a server solution to host my SharePoint (WSS 3.0) site. I have two sites. After a lot of struggle, I have restored the site from the shared hosting and it is up and running inside the server. Now my actual requirement is as follows. 

    In the server I am able to access the site with the URL - http://site1.tld:port1 and http://site2.tld:port2. In the Shared Hosting environment, I accessed it via http://site1.tld (without port) and http://site2.tld (without port). So I think the same can be configured in this server, if so, how?

    I referred a few tutorials and they says I need to setup ISA or a Proxy server and publish the URL. Well, in my current infrastructure, this is not possible. Is there any other way I can do this, to pull the SharePoint site, just by calling the http://site1.tld (without port) and http://site2.tld (without port).

    Please help me and thanks in advance. 

    Cheers!

    Wednesday, October 17, 2012 5:03 AM

Answers

  • Hiya,

    If your trying to access it from the server, you need to disable loopback check.

    http://support.microsoft.com/kb/896861

    I prefer method 2, although something else is stated in the KB.

    When you assign the admin user from the CA (Site collection Administrator) in terms of SharePoint, it should have access. So if its not working, its not directly SharePoint related :)

    • Marked as answer by arunv707 Monday, October 22, 2012 4:50 AM
    Thursday, October 18, 2012 6:02 AM

All replies

  • Hiya,

    When navigating sites, you can use either a hostheader or a port(or both) to identify the site.
    In your case you want more than one site to run on port 80 - This is only possible if you assign a hostheader.

    This is simplified in understand in the IIS bindings.

    Initially when you create your web application you can choose port and hostheader for the web application. If this was not done correctly, you either recreate your web application or extend it to use correct information. It is preferred in that order.

    Wednesday, October 17, 2012 10:16 AM
  • Hey Jesper!

    Thank you for your reply!

    So, if I were to create an alternate mapping to bind a webapp to a URL, I must use the Extend web app. Right?

    Here’s what I’ve tried:

    Extend web app > Selected the web app > Configured the port to a random number >  Didn’t use host header (first time) >  URL – I put the mydomain.com:that-random-port > Zone – I selected Extranet first time and followed the same steps and selected the Internet second time.

    So, at this point, the AAM for my account shows the following:

    http://mywebapp:2048 ---------- Default ---------- http://mywebapp:2048
    http://mydomain.com ----------- Intranet --------- http://mydomain.com 
    http://mydomain.com:2222 ------ Extranet --------- http://mydomain.com:2222

    This didn't work, I was unable to access the SharePoint site by using http://mydomain.com. So I thought to create a host header by extending the web application to include a Host Header. I’ve given the same – mydomain.com as host header. It failed and it displayed the Default IIS page. 

    When I checked to create an IIS binding, I was unable to see the website. But all of them are listed under the Default Website > wss > VirtualDirectories > Respective PortNumbers. 

    What am I doing wrong here? Also, you may please note that I have configured IP mapping for the mydomain.com to the server IP address in the %windows%\drivers\etc\hosts file.  

    Could you please assist me in this. 
    Thank you for your time.

    Wednesday, October 17, 2012 1:42 PM
  • Hiya,

    Wow - you really had some fun there :)

    First I will describe the steps of moving your site. Then you can cross check, if you did something else :)

    1: Backup your site content database. (SQL Backup file)
    2: Create a new Web Application with the port and hostheader you want. (Here you need to create a dummy database to the new web application)
    3: Restore the database in SQL
    4: Mount the database to the web application using stsadm -addcontentdb
    5: Then you should be able to access your site on the address without port or anything.

    You should create a new IIS site with a separate application pool account when you create your Web Application. Default http port is 80 and as long as you use a hostheader value, you can have multiple sites on port 80. (which is properly what you want)

    The reason I write this, is because your properly better off recreating your site, using the above method, than trying to get it to work :)

    If you don't want to go down that path, show me what you got on your IIS bindings, on the IIS site that is connected to your web application. Then we take it nice and slow from there.

    Wednesday, October 17, 2012 3:39 PM
  • Thank you so much for your reply, Jesper. I am checking this now.

     

    However, the shared hosting guys have provided me with the Sharepoint backup using the following command:

     

    stsadm -o backup -url http://site1.com -filename c:\backup\site1.net.bak

     

    I was actually restoring the SP site from this backup. I had issues while doing this and it was fixed. I have documented it here:

     

    http://social.technet.microsoft.com/Forums/en-US/sharepointadmin/thread/15b821b7-79b5-4973-bbc1-fb65012d03ab

     

    So, in order to follow the steps you have mentioned here, I would have to ask the shared hosting guys for the SQL specific backup of the SP site, right? Or, can this be restored and the previous settings be retained through some magic?

    Expecting your reply...


    • Edited by arunv707 Wednesday, October 17, 2012 4:40 PM format
    Wednesday, October 17, 2012 4:39 PM
  • If I'm not mistaken, that is actually an SQL backup you got there. Using the stsadm command, basically sends the SQL backup command to the database server. - So you should be able to restore it using SQL tools.

    Secondly remember that your coming from a different domain, meaning that all security set up on the site needs to be mapped to users in your current domain.

    Third, why not use the SharePoint 2010 Foundation? - Its also free but tons better than the WSS 3.0. (which is basically the SharePoint 2007 version of SharePoint 2010 Foundation)

    Sorry for not answering all your question directly, just there is a lot of things that could be improved for you :)

    Wednesday, October 17, 2012 5:02 PM
  • Thank God! So I have the file that was created via stsadm there in place. 

      

    Now, I have created the web application, this time with host headers. Do you want me to create site collection now, and then run the following command:

     

    stsadm -o restore -url http://site1.com:port -filename c:\backup\site.com.bak -hostheaderwebapplicationurl http://site1.com -overwrite

     

    Yes, I do remember this and I was told to create new users and assign permissions. However, this is not a domain environment. This is a standalone member server (joined to the domain of the hosting provider for centralized management)

     

    SharePoint 2010 Foundation would need more hardware resources and currently we are running out or money to buy a server hardware. :( 

     

    Your time is much appreciated and thanks for all your help so far. 

    Wednesday, October 17, 2012 5:54 PM
  • 1: You should be able to restore using the following line:

    For site collection restore:
        stsadm.exe -o restore -url http://site1.com -filename c:\backup\site.com.bak

    That should restore your site into the root of the web application.

    2: It still applies for user accounts - not system accounts.

    3: I would still go for SharePoint 2010 Foundation. Its simply a better product :)

    Your very welcome :)

    Wednesday, October 17, 2012 6:11 PM
  • I am trying this right now :) I will update you when I get some update from the black window :) 

    You rock!


    -- Best Regards | Arun V | http://twitter.com/arunv707

    Wednesday, October 17, 2012 6:19 PM
  • Hi Jesper, 

     

    I have restored it this way and it now asked for the username and password to get in. I have assigned a new admin user (local computer user account) to the site via Central Administration > Site Collection Administrators. But it's not letting me in. 

     

    Any thoughts on this?


    -- Best Regards | Arun V | http://twitter.com/arunv707

    Wednesday, October 17, 2012 7:07 PM
  • Hiya,

    If your trying to access it from the server, you need to disable loopback check.

    http://support.microsoft.com/kb/896861

    I prefer method 2, although something else is stated in the KB.

    When you assign the admin user from the CA (Site collection Administrator) in terms of SharePoint, it should have access. So if its not working, its not directly SharePoint related :)

    • Marked as answer by arunv707 Monday, October 22, 2012 4:50 AM
    Thursday, October 18, 2012 6:02 AM
  • Sorry for the delay in replying, but I am running Windos Server 2008 and that article is for the older versions. In such a case, could you please let me know how would you like me to proceed?

    Awaiting your reply,


    -- Best Regards | Arun V | http://twitter.com/arunv707

    Sunday, October 21, 2012 7:14 AM
  • Hiya,

    Its still a consideration for windows server 2008, so you can proceed. Its not irreversible :)

    Sunday, October 21, 2012 12:10 PM
  • AMAZING I SHOULD SAY!!!

     

    **** IT IS WORKING!!!!! ****

     

    Thank you sooooo much Jesper. 


    -- Best Regards | Arun V | http://twitter.com/arunv707

    Monday, October 22, 2012 4:49 AM
  • Glad it all worked out :)
    Monday, October 22, 2012 7:24 AM