Alternate Access mapping Problem
Hi all,
I've a problem while i'm trying to add alternate access mapping to my sharepoint web application it show an error that i don't understand Ex:
my sharepoint web app is (http://sharepoint2010:4000) and the alternate access mapping is a registered domain name for example it's
(http://kkk.edu.us/en/pages).
what shall i do so as to make the users from every where to access that web application via this domain name (http://kkk.edu.us/en/pages).??
thanks in advance
January 22nd, 2011 3:07pm
Usually if both publishers have to publish content and viewers have to view content, it's a two step process. Once you create your very first site collection under your web app, you need to extend that web app. While extending this web app, you will provide
http://kkk.edu.us/en/pages as the host header. However, usually port 80 (http) and 443 (https) are the standard ports opened to the outer world.
Here is what I would do if you have no reason to create a https site at all for publishing content:
Test by going to one of the WFEs whether I can ping or nslookup kkk.edu.us Create a SharePoint web app using Central Admin at port 80, while creating supply kkk.edu.us/en/pages as host header
Create your site collection under this web app just created
The above should take care of the plumbing. However, once everything is done, you can go to IISManager and double check whether the host header got assigned to the IIS website created by SharePoint.
Network admins usually don't recommend the usage of non standard ports to be exposed outside company network.
AAM will be needed if the same site needs to accesses by more than one url. There are plenty of explanations in the internet like this one:
http://mossmash.blogspot.com/2010/03/how-to-configure-alternate-access.html
Hope this helpsThanks, Soumya
Free Windows Admin Tool Kit Click here and download it now
January 22nd, 2011 4:53pm
Usually if both publishers have to publish content and viewers have to view content, it's a two step process. Once you create your very first site collection under your web app, you need to extend that web app. While extending this web app, you will provide
http://kkk.edu.us/en/pages as the host header. However, usually port 80 (http) and 443 (https) are the standard ports opened to the outer world.
Here is what I would do if you have no reason to create a https site at all for publishing content:
Test by going to one of the WFEs whether I can ping or nslookup kkk.edu.us Create a SharePoint web app using Central Admin at port 80, while creating supply kkk.edu.us/en/pages as host header
Create your site collection under this web app just created
The above should take care of the plumbing. However, once everything is done, you can go to IISManager and double check whether the host header got assigned to the IIS website created by SharePoint.
Network admins usually don't recommend the usage of non standard ports to be exposed outside company network.
AAM will be needed if the same site needs to accesses by more than one url. There are plenty of explanations in the internet like this one:
http://mossmash.blogspot.com/2010/03/how-to-configure-alternate-access.html
Hope this helpsThanks, Soumya
January 22nd, 2011 4:53pm
Thanks a lot Soumya but it didn't work :(
, i've checked some web sites for answer and here was the nearst one :
http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=48
any new answers welcomed :)
Free Windows Admin Tool Kit Click here and download it now
January 24th, 2011 2:25am