Alternate Access Mappings Problem - Please Help

I have been trying to solve a problem (for several days) with a portal that I think is AAM related.

Here is the scenario:

I have a portal that is to be accessed internally by employees, and externally by outside partners.

For this I have a web application that uses windows authentication and that can be accessed, internally, through http://extranet:20707/sites/somePortal

I extended the web application to allow outside partners to be able to access the site using forms authentication. This extended site is to be accessed from outside through: http://extranet.mydomain.com/sites/somePortal

This extended web app can also be accessed internally (although the user/password prompt comes up) through: http://extranet/sites/somePortal

From inside, everything is working fine. I can access both sites (http://extranet:20707/sites/somePortal & http://extranet/sites/somePortal) with no problems.

However, when I try to hit the site from outside (http://extranet.mydomain.com/sites/somePortal) I get the user/password prompt but I get redirected to the http://extranet:20707/sites/somePortal site (however the URL does not change in the browser) but of course external users don＊t have access to it.

As far as I am concerned, this most likely is an AAM related problem, but I have read many blogs and forums, and I have tried everything I could possibly imagine, but I still cannot get it to work.

This is the configuration that I have on the AAM config page:

Internal URL Zone Public URL for Zone

http://extranet:20707 Default http://extranet:20707

http://extranet Extranet http://extranet

This is the configuration I have in IIS:

Description IP Address Port Host Header Value

aPortal - default 10.201.16.204 20707

aPortal 每 extranet 10.201.16.204 80 extranet

Your help will be very much appreciated.

Thanks in advance.

LAM.

Please recreate the Externet web application zone with the host header of extranet.mydomain.com (FQDN) instead of just extranet.

This is the DNS configuration that we have:

External DNS (Network Solutions) Internal DNS Internal IP Host Header

http://extranet.mydomail.com ==> external ip ==> INTERNET ==> extranet ==> 10.201.16.204 ==> extranet

Do you still recomend to create extranet.mydomain.com host header

Do I have to create it on the internal DSN pointing to 10.201.16.204

Thanks,

LAM.

What I was doing was right. For some reason SharePoint did not like it. I removed all AAM configuration, I created a new web app and a new site, I configured it like I show below and worked fine. Then, I re-configured my original web app and this time it worked!

This is the configuration that I have on the AAM config page:

I am assuming you want to have internal access through the default zone and external access through the extranet zone. Then, if you want both zones on port 80, you will need to specify different IP addresses.

In the event that you want to use ※http://extranet§ for the default zone (used internally), and ※http://extranet.mydomain.com§ for the extranet zone I would do the following:

AAM Configuration:

Internal URL Zone Public URL for Zone

http://extranet Default http://extranet

http://extranet.mydomain.com Extranet http://extranet.mydomain.com

IIS Configuration:

Description IP Address Port Host Header Value

aPortal - default 10.201.16.204 80 extranet

aPortal 每 extranet 10.201.16.205 80 extranet.mydomain.com

※extranet.mydomain.com§ has to be added to the internal DNS as a FQDN. I cannot tell you exactly how because I had the IT people handle that.

Please try this and let me know what happens.

LAM.