I have been trying to change the default url for a sharepoint site from the //<server name>:<port #> to something a little more user friendly like //randomname.lan. I have moss 2007 installed on a windows server 2003 box with iis 6 and sql server 2005. this is the only server that sharepoint is installed on, but the dns servers are both server 2000 boxes. I have tried adding a host(a) record in dns, i've added host headers in iis, i've use alternate access mappings, and i've tried these individually and together, but i either get a page cannot be displayed error or a google search page. What am I doing wrong?
Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Changing the default url for a sharepoint site
- Thread starter cloksin
- Start date
Hello,
First of all, do not modify IIS. In fact, doing so will likely ruin any chance you have of getting this done 'properly'. The reason is that SharePoint handles all the IIS stuff for you, and if you have made modifications to IIS there is no way for SharePoint to detect or understand what you were trying to do and thus it will fail to make corrections required to support alternate mappings.
I do not know what you are doing wrong, but I can tell you how to do it right
Make sure your DNS is working properly and pointing to the right place. A simple 'c:\>ping randomname.lan' resolving to the correct IP is all you need.
Next, set up AAM in SharePoint. You need to either set up what SharePoint calls a Public URL or set up an additional internal URL. Make sure you select the correct AAM collection, ie the web aplication to which you want the traffic to be directed.
After this you can access your site from the new URL. I just followed this exact setup whie writing this post just to make sure it works. Granted I have the DNS set up on the same computer but that does not affect the result.
.b
Blog for my upcoming SharePoint book
"Building the SharePoint User Experience":
First of all, do not modify IIS. In fact, doing so will likely ruin any chance you have of getting this done 'properly'. The reason is that SharePoint handles all the IIS stuff for you, and if you have made modifications to IIS there is no way for SharePoint to detect or understand what you were trying to do and thus it will fail to make corrections required to support alternate mappings.
I do not know what you are doing wrong, but I can tell you how to do it right
Make sure your DNS is working properly and pointing to the right place. A simple 'c:\>ping randomname.lan' resolving to the correct IP is all you need.
Next, set up AAM in SharePoint. You need to either set up what SharePoint calls a Public URL or set up an additional internal URL. Make sure you select the correct AAM collection, ie the web aplication to which you want the traffic to be directed.
After this you can access your site from the new URL. I just followed this exact setup whie writing this post just to make sure it works. Granted I have the DNS set up on the same computer but that does not affect the result.
.b
Blog for my upcoming SharePoint book
"Building the SharePoint User Experience":
- Thread starter
- #3
Hello,
That depends from where you want to access your new address. If you only want it to be available internally there is no need to expose it externally.
.b
Blog for my upcoming SharePoint book
"Building the SharePoint User Experience":
That depends from where you want to access your new address. If you only want it to be available internally there is no need to expose it externally.
.b
Blog for my upcoming SharePoint book
"Building the SharePoint User Experience":
- Status
Similar threads
- Locked
- Question