In my scenario, I have
The desired as follows
If I navigate to this URL “http://epm”, It should be pointed directly to web application URL.
In this article, I will demonstrate How to map an internal URL to be associated with a web application public URL by performing the following:
- Configure alternate access mapping via Central Administration.
- Configure SharePoint Site Bindings.
- Configure Hosts file
- Disable loop Back Check
- Add “A” record on DNS server for your URL
Finally, I’m gonna show some alternate access mapping considerations.
1. Configure alternate access mapping
- Open Central Administration as administrator > System Settings > Configure Alternative Access Mappings.
- The Alternate Access Mappings page should be shown.
- Click on Edit Public URL.
- Be aware that, by default, There must always be a public URL for the default zone, and you can’t delete the last internal URL for the default zone.
- Set Intranet Zone to (http://URL.domain.local).
- In this case, It’s “http://epm.domain.local”.
- Set Internet Zone to (http://URL).
- In this case, It’s “http://epm”
- Finally, Alternate Access Mappings should be like this. (Click on image to view it in original size)
2. Configure SharePoint Site Bindings
- Open IIS Manager > From left side select SharePoint site > From right side, below Actions > Click on bindings.
- Click on add to add a new URL (http://URL.domain.local)
3. Configure Hosts file
- Navigate to this path.
- Open hosts file via appropriate editor > add the current server IP > click Tab from keyboard >add the URL.
4. Disable loop Back Check
- Run Regedit.msc.
- Navigate to HKEY_LOCAL_MACHINE > System.
- System > Control.
- Control > Lsa.
- Right Click on Lsa to add a new key.
- Rename key with DisableLoopbackCheck > Right-click on it > select Edit.
- Change value data from 0 to 1 > click OK.
- Close Registry Editor and restart the server
4. Add “A” record on DNS server for your URL
- Tell your system administrator to create “A” record on the DNS server for http://epm.domain.local to Point to SharePoint server with IP: xxx.xxx.xxx.xxx
To get SharePoint IP you should run this command “ipconfig /all”
You should now be able to connect to the web application URL via http://epm inside your network.
**Alternate access mapping considerations.
- Alternate access mappings must be configured for load balancing, even though it generally does not apply to host header site collections. The default zone public URL should be set to a domain URL that is appropriate for all users to see. Unless you do this, the names of web servers or their IP addresses might be displayed in parameters that were passed between pages within SharePoint 2013.
- Host-named site collections can’t use alternate access mappings. Host-named site collections are automatically considered in the Default zone, and the URL of the request must not be changed between the user and the server.
- Alternate access mappings allow you to expose a web application in as many as five different zones, with a different IIS website backing each zone, some people mistakenly refer to this as having up to five different web applications sharing the same content databases. In reality, there is just one web application.
- There must always be a public URL for the default zone.
- You can’t delete the last internal URL for the default zone.