Domain Controller (LDAPS) Load Balancing – NetScaler 11.1

Last Modified: Nov 6, 2020 @ 7:26 am



If you plan to use LDAP (Active Directory) for NetScaler Gateway or NetScaler management authentication, load balance the Domain Controllers that are used for authentication.

An alternative to load balancing is to configure NetScaler Gateway and NetScaler management authentication with multiple authentication policies, each pointing to a single Domain Controller. However, NetScaler will try each authentication policy until it finds one that works. If the user enters a wrong password and if you have three authentication policies pointing to different Domain Controllers in the same domain then three different failure attempts will be recorded thus causing premature account lockout. Use Load Balancing to avoid this behavior.

This page details LDAPS, aka Secure LDAP. This protocol requires certificates to be installed on the Domain Controllers. When a user’s password expires, Active Directory does not allow password changes over clear text LDAP so LDAPS must be used instead. Make sure you have certificates installed on your Domain Controllers. The easiest way to accomplish that is to deploy a Microsoft Certificate Authority. Once that’s done the Domain Controllers will request certificates automatically.

An ldaps monitor can be used to verify that the Domain Controller is functional. The ldaps monitor will login as an account, perform an LDAP query, and look for a successful response. The ldaps monitor uses a service account to login. Make sure the service account’s password does not expire. Domain User permissions are sufficient. Since this monitor is a Perl script, it uses NSIP as the source IP. You can use RNAT to override this as described in CTX217712 How to Force scriptable monitor to use SNIP in Netscaler in 10.5.

If you have Domain Controllers in multiple datacenters, you can create multiple load balancing Virtual Servers and cascade them so that the local Domain Controllers are used first, and if they’re not available, then the Virtual Server fails over to Domain Controllers in remote datacenters.

The Load Balancing Virtual Server for LDAPS can be TCP or SSL_TCP:

  • If the protocol is TCP, then SSL-encrypted LDAP traffic is not terminated on the NetScaler, and is simply forwarded to the LDAP servers. If your LDAP client needs to verify the LDAP server certificate, then this Load Balancing configuration will not work, since each back-end LDAP server will have a different certificate.
  • If your Load Balancing Virtual Server is protocol SSL_TCP, then a certificate must be installed on the NetScaler and bound to the Load Balancing Virtual Server. SSL is terminated at the NetScaler and re-encrypted before sending it to the destination Domain Controller. The primary benefit of NetScaler SSL termination is that your LDAP clients can verify the Virtual Server SSL certificate.

When NetScaler uses a local (same appliance) load balanced Virtual Server for LDAPS authentication, the traffic is sourced from the NetScaler SNIP (Subnet IP). When NetScaler uses a direct connection to a Domain Controller without going through a local Load Balancing Virtual Server, or if NetScaler uses a remote (different appliance) Load Balancing VIP, then the traffic is sourced from the NetScaler NSIP (NetScaler IP). Adjust firewall rules accordingly.

LDAPS Monitor

Note: Perl monitor uses NSIP as the source IP. You can use RNAT to override this as described in CTX217712 How to Force scriptable monitor to use SNIP in Netscaler in 10.5.

  1. In the NetScaler Configuration Utility, expand Traffic Management, expand Load Balancing, and click Monitors.
  2. On the right, click Add.
  3. Name the monitor ldaps-Corp or similar. The ldaps monitor logs into Active Directory, performs an LDAP query, and looks for a successful response. The monitor configuration has domain specific information so if you have multiple Active Directory domains, then you will need multiple ldaps monitors. Include the domain name in the monitor name.
  4. Change the Type to LDAP.
  5. Scroll down and check the box next to Secure.
  6. Scroll back up and switch to the Special Parameters tab.
  7. On the Special Parameters tab, use the Script Name drop-down list to select the file.
  8. In the Base DN field, enter your domain name in LDAP format (e.g. dc=company,dc=com)
  9. In the Bind DN field, enter the UPN login (e.g. of a service account in the domain that can browse all objects. Any normal Domain User should be sufficient. Just make sure the password doesn’t expire.
  10. In the Filter field, enter cn=builtin. This limits the search results.
  11. In the Password field, enter the password for the service account. Make sure there is no semicolon in the password or the script will be unable to parse the parameters.
  12. Click Create.

    add lb monitor LDAP-Corp LDAP -scriptName -dispatcherIP -dispatcherPort 3013 -password Passw0rd -secure YES -baseDN "dc=corp,dc=local" -bindDN "corp\\ctxsvc" -filter cn=builtin
  13. If you have multiple domains then create additional monitors: one for each domain.


  1. On the left, expand Traffic Management, expand Load Balancing, and click Servers.
  2. On the right, click Add.
  3. Enter a descriptive server name, usually it matches the actual server name.
  4. Enter the IP address of the server.
  5. Enter comments to describe the server. Click Create.

    add server AD01
    add server AD01
  6. Continue adding Domain Controllers.

Service Groups

  1. On the left, expand Traffic Management, expand Load Balancing, and click Service Groups.
  2. On the right click Add
  3. You will create one Service Group per datacenter. Enter a name reflecting the name of the data center. Also, you will create a set of service groups per Active Directory domain so include the domain name.
  4. Change the Protocol to SSL_TCP. Scroll down and click OK.

  5. On the left, in the Service Group Members section, click where it says No Service Group Member.
  6. If you did not create server objects, then enter the IP address of a Domain Controller in this datacenter. If you previously created a server object, then change the selection to Server Based, and select the server object. In the Port field, enter 636 (LDAPS).
    1. Note: Any Domain Controller you add to this list must have an SSL certificate installed. The easiest way to install SSL certificates on the Domain Controllers is with Active Directory Certificate Services since it installs the certificates automatically.
  7.  Click Create.
  8. Click OK.
  9. On the right, in the Advanced Settings column, click Monitors.
  10. On the left, in the Monitors section, click where it says No Service Group to Monitor Binding.
  11. Click the arrow next to Click to select.
  12. Select your new LDAPS monitor and click Select.
  13. Click Bind.
  14. To verify the member is up, click in the Service Group Members section.
  15. Click the ellipsis next to a member and click Monitor Details.
  16. It should say Success – Probe succeeded. Click Close.
  17. If the monitor doesn’t work, use ldp.exe to verify the Domain Controller certificate.
  18. Click Close and Done to finish creating the Service Group.

    add serviceGroup svcgrp-LDAP-Corp SSL_TCP
    bind serviceGroup svcgrp-LDAP-Corp AD01 636
    bind serviceGroup svcgrp-LDAP-Corp AD02 636
    bind serviceGroup svcgrp-LDAP-Corp -monitorName LDAP-Corp
  19. Add additional service groups for Domain Controllers in each data center.

Virtual Server

  1. Create or import a certificate that matches the FQDN that resolves to the new Load Balancing VIP for LDAPS.
  2. On the left, expand Traffic Management, expand Load Balancing, and click Virtual Servers.

  3. On the right, click Add.
  4. Name it LDAPS-Corp-HQ-LB or similar. You will create one Virtual Server per datacenter so include the datacenter name. Also, each domain has a separate set of Virtual Servers so include the domain name.
  5. Change the Protocol drop-down to SSL_TCP.
  6. Enter a Virtual IP. This VIP cannot conflict with any other IP + Port already being used. You can use an existing VIP that is not already listening on TCP 636.
  7. Enter 636 as the Port. Click OK.
  8. On the left, in the Service Group section, click where it says No Load Balancing Virtual Server ServiceGroup Binding.
  9. Click the arrow next to Click to select.
  10. Select the previously created Service Group and click Select.
  11. Click Bind.
  12. Click Continue.
  13. On the left, in the Certificates section, click where it says No Server Certificate.
  14. Click the arrow next to Click to select.
  15. Select a certificate that matches the FQDN that will resolve to this VIP. Click Select.
  16. Click Bind.
  17. Click Continue.

    add lb vserver lbvip-LDAP-Corp SSL_TCP 636 -persistenceType NONE -cltTimeout 9000
    bind lb vserver lbvip-LDAP-Corp svcgrp-LDAP-Corp
  18. If you haven’t enabled the Default SSL Profile, then perform other normal SSL configuration including: disable SSLv3, and bind a Modern Cipher Group.
    bind ssl vserver MyvServer -certkeyName MyCert
    set ssl vserver MyvServer -ssl3 DISABLED -tls11 ENABLED -tls12 ENABLED
    unbind ssl vserver MyvServer -cipherName ALL
    bind ssl vserver MyvServer -cipherName Modern
    bind ssl vserver MyvServer -eccCurveName ALL
  19. Click Done to finish creating the Virtual Server.
  20. The new Virtual Server should show as Up.
  21. Create additional Virtual Servers for each datacenter. These additional Virtual Servers do not need a VIP so change the IP Address Type to Non Addressable. Only the first Virtual Server will be directly accessible.

    add lb vserver lbvip-LDAP-Corp-Backup SSL_TCP 0
  22. Notice that the additional datacenter Virtual Servers show up with an IP Address of and port of 0.
  23. After you are done creating a Virtual Server for each datacenter, click the ellipsis next to the primary datacenter’s Virtual Server and click Edit.
  24. On the right, in the Advanced Settings column, click Protection.
  25. On the left, in the Protection section, change the Backup Virtual Server to one of the other datacenter Virtual Servers. If all of the services in this datacenter are DOWN, the backup Virtual Server will be used instead. You can cascade multiple Virtual Servers using this method. Click OK and Done.

    set lb vserver lbvip-LDAP-Corp -backupVServer lbvip-LDAP-Corp-Backup

Next Steps

You may now use this Virtual IP in your LDAP authentication policies for NetScaler Gateway or NetScaler management login.

16 thoughts on “Domain Controller (LDAPS) Load Balancing – NetScaler 11.1”

  1. Hey Carl! Really like this write up, and we’ve had an NS VIP for LDAPS authentication in place for years without issue. Recently, we began using the Active Directory “Protected Users” group for certain users, and we find that they can’t authenticate with the NS VIP any longer. I believe this is because the VIP only load balances 636 for LDAPS, and Protected Users require Kerberos. Have you run into this yet? Any thoughts on the best way to deliver both LDAPS (with cert) as well as Kerberos auth? Is it replacing the existing VIP with a new one with >1 port, or just adding new VIPs for TCP/UDP 88?


  2. I am having a lot of issues with setting up the LDAPS monitor and have been forced to resort to just TCP which I would prefer not to use. Version is Citrix ADC NS13.0: Build,

    I have done the following to eliminate environmental causes on the DCs
    Tested the Firewall 636 ports are open on both DCs
    Tested the LDAPS connection using a Powershell script and also ldp.exe and both succeed
    Test-LDAP -ComputerName “DC1”
    Test-LDAP -ComputerName “DC2”
    Computer : DC1
    ComputerFQDN :
    GlobalCatalogLDAP : True
    GlobalCatalogLDAPS : True
    LDAP : True
    LDAPS : True
    AvailablePorts : 389,636,3268,3269

    Chosen SSL_TCP as the service type for LDAP services that are being load balanced but the LDAPS monitor never returns success.

    A basic auth policy action which connects to the same 2 DCs succeeds with SSL and 636 selected and a AAA vServer that uses this LDAP auth action also works. Its the monitoring of LDAPS that seems problematic when TCP is not used. Any tips to debug this further?

  3. Great article Carl, In an environment where few windows servers present which are hosting dns, ldap, ldaps, RPC and Kerberos services. How can all these service be achieved by creating a single vip in netscaler.
    If I create a single vip with any protocol & any port & put the backend servers to windows servers – Then I will be missing out features such as dns security, waf etc.

    So what is your suggestion on loadbalancing dns, ldap, ldaps, RPC and Kerberos services….

  4. Hi Carl, we are utilizing LDAP VIP’s through our our organization for various applications that need LDAP authentication or even DNS and other AD services Global catalog, etc.. We have multiple locations globally. In most of these locations we have a netscaler. So we have local LDAP VIP’s setup on these netscalers. But we would like to use GSLB on the netscaler to Load balance LDAP to 1 VIP and have it globally load balanced across the netscalers. Is there any special considerations to accomplish this?


  5. Hello Carl,
    I created this LDAP Load balancer (without certs) – so just with 389port. Without gateway.
    Is that possible to use this LDAP load balancer for a normal domain authentication requests?
    Same like this – if I want to create a new VM which will be member of a domain, can I use this LDAP LB address (IP of load balancer) for this joining procedure on new VM?
    It is not working for me.
    Is DNS LB required for this? Sorry for my “stupid question”.

  6. Hi Carl! Great page… A few things:

    1.) I thought AD LDAPS didn’t like wildcards configured on the backend servers? So if we have an LDAPS configured on the server shouldn’t it be the CA certficate from the domain controller? In an AD environment WildcardLDAPS certificate won’t work.

    LDAPS (Lightweight Directory Access Protocol) does not support wildcards.

    Active Directory does not support wildcards.

    2.) If we have deployed in an internal certificate on all our domain servers to configure LDAPS. We will need to CA Root certificate on the netscaler, correct?
    3.) don’t we have to use the name and not ip? because it doesn’t have the ip in the SAN?

    1. Domain Controllers will only choose a non-wildcard cert for the LDAPS listener.

      Some LDAP Clients (e.g. NetScaler Gateway) don’t validate the certificate. Some LDAP Clients (e.g. Linux machines) do validate the certificate. If you need valid certificates, then you’ll need to provision a valid certificate. You might be right that LDAPS with certificate validation won’t accept wildcards.

  7. I usually just use TCP instead of SSL_TCP so I don’t have to bind the certificate, or have to update the certificate in the future. Is there any benefit of using SSL_TCP though?

    1. If NetScaler is your LDAP client, then no. But if you have Linux/UNIX machines using the LDAP LB VIP, then yes, so they can verify the certificate.

  8. great article, thanks Carl

    My questions is about step 15: “Select a certificate that matches the FQDN that will resolve to this VIP.”

    In my scenario, our local domain is acme.local, there is a CA installed, I’m using single FQDN for Receiver and our external FQDN will be e.g. (with a split DNS zone internally for this purpose) for which I have a 3rd party purchased cert.

    Which certificate must be used on the LDAPS VIP? Install my root and server certs for the Domain controllers on the netscaler or use the 3rd party one, but have that cert also on the DC’s for SSL_TCP? I’m a bit confused. Thanks for helping !

    1. It’s a different FQDN. And it’s internal only. It’s the same as setting you a new load balancing VIP. It has nothing to do with Gateway other than Gateway will use it to perform LDAP queries.

      Offloading LDAP SSL to NetScaler is optional. Another option is TCP protocol instead of SSL_TCP protocol.

Leave a Reply

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