• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 676
  • Last Modified:

how to make 'http://intranet' point to site collection on sharepoint server

I've asked this question before, but i think i worded it incorrectly, so here goes again. I've created a site collection for which the address and port number is http://sharepointserve:28220/sites/portal. I want all of the staff to access it but don't want them to type in hte above address, further more when it is typed in from another computer they get error 404 anyway. So my question is:-

1. If I want staff to type in 'http://intranet' and get to the site above do i need to configure AAM, IIS or both?, if so what do I have to do?
2. when full address are typed in e.g http://sharepointserve/pages/default (the default port 80 site) it can be viewed from anywhere, but other ports come up with error 404.

I hope the question in a bit clearer now..please help! ;-)
0
r00ts
Asked:
r00ts
  • 2
  • 2
  • 2
  • +3
5 Solutions
 
Gonzalo BecerraCommented:
You have 2 options:

1- You can use Hostheaders on your site

2- You can make a redirect to your site (before you need make a cname on your dns)
0
 
r00tsAuthor Commented:
Thanks for the reply and sorry for the next question, but how do i go about doing both solutions above?
0
Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
Tray896Commented:
You should be able to do this with host headers and a DNS change along with a custom alternate access mapping.

Lets say the only IP on your server is 192.1.1.1 so thats what your websites are listening on.  Create a new DNS record so that 'intranet' resolves to 192.1.1.1.  To avoid modifying what is already there, click on Add to create a new host header.  Leave the default of port 80, and type intranet into the host header value.

For the alternate access mapping, open Central Admin and then click on alternate access mapping from the operations tab.  Click on edit public URL's.  Select your web app from the drop down, and then type http://intranet in the custom field.  Apply these changes and then try hitting your site.
0
 
dmogheCommented:
You can create a plain IIS site and have a re-direct code written to point to the site collection. For redirection of site collection, you need not have to do anything with AAM.

You can have a look at :
http://blogs.technet.com/harmeetw/archive/2009/09/08/redirecting-a-sharepoint-subsite-or-a-site-collection-to-a-different-url.aspx

For sites not opening on other ports, you might probably have firewall that might be blocking traffic on other port. Are you able to browse the sites on other port from the SharePoint server?

Hope this helps.
0
 
Greg BurnsSQL / SharePoint ConsultantCommented:
Something a bit more involved (but cleaner) would be to move the site collection to a new web application.  If I am reading you correctly, you have a site collection at the root of your http://sharepointserve/ webapp (on Port 80), and another webapp at http://sharepointserve:28220 with a site collection named "Portal" under the managed path "/sites/".

You could simply Extend the site, whcih takes care of alternate access mappings for you.  So http://sharepointserve:28220 and http://intranet would point to the same content database.  Note, however, that you would still be using the same managed path to get to the site collection (e.g. http://intranet/sites/Portal).  

If you do want this new site collection to be in its own namespace, you could try this:

1. Back up the new site collection
2. Create a DNS record for "Intranet" pointing to the SharePointServe server IP address
3. In Central Admin, create a new Web Application.  Use port 80, and specify "Intranet" as the host header.  The new website (http://intranet) will share port 80 with the other SharePoint site (http://SharePointServe).  
4. Restore your site collection into the root of the Intranet web applicationn.
5. Turn off the other web applications as desired.

There's a blog post here where a guy wrote an interesting PowerShell script to extend STSADM to move a site collection between webapps with a single command.  Haven't tried it yet, but it may be just the ticket:
http://stsadm.blogspot.com/2008/01/move-site-collection.html

The more conventional method is here:
https://technet.microsoft.com/en-us/library/cc263441.aspx
0
 
r00tsAuthor Commented:
Sorry for getting back to this issue so late, but was really tied up with other issues. OK I get most of the advice but can someone please tell me how to create or modify DNS records...many thanks
0
 
Tray896Commented:
Assuming you have access to the DNS servers, check out this article.  There is a section for creating the DNS records: http://support.microsoft.com/default.aspx/kb/324260
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 2
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now