A typical SharePoint farm may contain more than one web front-end server – load balanced. When you hit the SharePoint site URL, say: https://portal.crescent.com, it hits the load balancer first. Load balancer decides to which web front end server this request needs to be transferred based on server load and other load balancing algorithms. Here is a nifty trick to hit specific WFE, bypassing load balancer in SharePoint farm.
Option 1: Connect to a Specific WFE Server in SharePoint with HOST file Edit:
- Go to “C:\WINDOWS\system32\drivers\etc” in your local machine
- Open the “HOST” file in notepad.
- Add an entry at the end of the file with: WFE IP and SharePoint site’s Host header.
- E.g. 10.129.150.25 extranet.crescent.com
- Save and close the file.
- Clear your browser cache and reopen the site.
Now you should get responses from the specified web front end server. BTW, Web Front End Server (WFE) is the one with IIS Web sites running.
Option 2: Add a Binding to SharePoint Web Application in IIS:
Alternatively, you can add an additional binding to your SharePoint web application and hit that URL from your local machine. Say, You have a SharePoint web application: Intranet.Crescent.com which has port 80 and Port 443 bindings on a web server: Abz-SPS2013-V1. Now,
- Go to IIS >> Expand Sites >> Pick your web app >> Click on Bindings >> Add a binding. E.g. Type: HTTP, IP: All Unassigned, Port: 8888.
- Add an alternate access mapping with the new URL to complete.
Now you can hit: https://Abz-SPS2013-V1:8888/ from your local machine!