Configure SharePoint Network Load Balance using Citrix NetScaler

To make your SharePoint farm builds resilience, network load balancing plays an important role. In this article I will cover load balancing Web Front End servers using Citrix NetScaler.

This article is a continuation to SharePoint 2013 Enterprise farm Build.

To begin with the configuration.

1. Logon to Citrix NetScaler. Under traffic management, expand Load Balancing and click on servers and add SharePoint servers you would like to load balance.  In this example, I will use WFE 01 and WFE02. Add server name and IP addresses.

Load balancing service groupsCapture3

Repeat the same step for another Web Front End server.

2. Now click on Service groups under the same tab and give the service group a name and click on the members and add SharePoint servers you have created in step one.


Next, click on Monitors tab and choose http and click on add.

Create a group

3. We will be binding a service group to the virtual server and assign our virtual IP. Under load balancing, click on Virtual Servers, give it a name and add virtual IP and then click on Service Groups and choose SharePoint service group you have created in step 2

Capture7 - CopyCapture8


Within the same screen, choose Method and Persistence tab and Select Least Connection in Method and None as Persistence drop downs.


Thats it your NLB for SharePoint should be up and running, to check if your configuration is done properly, go to Virtual server and see that state is UP.

4 thoughts on “Configure SharePoint Network Load Balance using Citrix NetScaler

  1. Thanks for your post..hard finding easy info on SP2013 and Netscaler. I do have one issue however…when enabling “http” monitor on my service group, I am noticing that my effective state is “DOWN”. When looking at the monitor details I see that the monitor is receiving “401 Unauthorized”. I am able to reach each front end individually without any authentication issues but I suspect this issue is in fact due to some authorization problem when using the VIP. As soon as I change the DNS A record to use the VIP, I am getting a 401 and unable to login. Any ideas as to why this is occurring?

  2. Hi Garion, did you configure your Alternate access mappings? it looks like you have not yet used your IPs on your SharePoint IIS and AAM.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.