Sharepoint 2010 Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint 2010       RSS Feeds

Alternate Access Mapping

  Date: Oct 13    Category: Sharepoint 2010    Views: 1350

Alright, I clearly do not understand the underlying mechanism for how AAM works.
I'm hoping that by pinging the list here, I either get a response, or distill
the information I do know into the answer. :)

I have a SharePoint Foundation server running on SPFDNSVR. I have a web
application on that server running on port 10000. The default name of the web
application and the default public URL for that same application are

Now, I had our networking group reserve an IP for a VIP, DNS reserve a name, and
the VIP configured (address pointing to server name port 10000, SSL offloading,

The new FQDN for the server *should* be https://foundation.mycompany.com.

I went into the AAM for that web application and added
http://foundation.mycompany.com Intranet
https://foundation.mycompany.com Internet

That didn't work. I even tried adding
<ip address of spfdnsvr> foundation.mycompany.com
...to my HOSTS file and that also did not work.

So I poked around and after some reading thought that perhaps what I wanted to
do wasn't add an AAM, but extend the application. So I extended the application
to http://foundation.mycompany.com (port 80) (I couldn't extend it to https
because I didn't have a certificate on the sharepoint server.)

That still didn't work with the VIP, but it DID work with the HOSTS file.

After reviewing all of this, I thought that maybe the problem was the port
number. Would the following solution be correct and/or at least moving in the
right direction?

1. Extend web application to http://foundation.mycompany.com (port 10001)

2. Change the load balancer to point
https://foundation.mycompany.com<http://foundation.mycompany.com> at port 10001
instead of 10000

Is there a good reference for all of this? I've got the MS Press Admin's
Companion and WROX's SP 2010 Administration books and both have about 2 pages
(total) talking about AAM.



4 Answers Found

Answer #1    Answered On: Oct 13    

AAMs don't include the port number. So when you added
http://foundation.mycompany.com its acutually

Answer #2    Answered On: Oct 13    

Alright, that makes sense based on the results of what I tried. So the question
then becomes, can I set up a web application, not on port 80, that will respond
to http requests sans port number? Was I on the right track at the end there?
(Extend or create a new web app, with the correct name to respond to, on a
different port and point the load balancer at the new port?)

Answer #3    Answered On: Oct 13    

In your case the answer would be to extend the existing web application to a
new zone with the port number you want to use. HTTP always uses a port
number. If you don't supply one for HTTP then it uses port 80 and HTTPS
uses port 443.

Answer #4    Answered On: Oct 13    

You can also add/check for a host header in IIS to route that FQDN to that web

Didn't find what you were looking for? Find more on Alternate Access Mapping Or get search suggestion and latest updates.