How do I Make the 2X LoadBalancer Fully Redundant?
Posted by - NA - on 02 October 2007 01:25 PM

As of Version 5, primary publishing and backup agents are hosted, and can be set up in the 2X Console. In the event of a primary failure, the backup agent will take over management of the 2X Client Gateways and 2X Terminal Server agents.

This setup is not enough to provide complete redundancy; if using a single 2X Secure Client Gateway, no users can connect in the case of machine failure.

Within the 2X ApplicationServer client, primary and secondary servers are allowed (input as the IP of the 2X Secure Client Gateways); however, some RDP clients only allow a single name or IP to be referenced. To prevent users from needing to know multiple addresses, users can simply use the DNS Round Robin or Network LoadBalancing (NLB) methods.


In the figure above, we have a 2X Secure Client Gateway hosting our primary Publishing Agent, and a second 2X Secure Client Gateway hosting our backup Publishing agent.

The backup Publishing Agent doesn't operate when the primary Publishing Agent is functioning; however, both 2X Client Gateways are in use, providing redundancy in case of primary Publishing Agent failure and balancing network traffic for clients when both 2X Secure Client Gateways are active.

To Setup DNS Round Robin

1. Add two A (host records); Ex: "clientgateway", "clientgateway"

2. Set "clientgateway.x.x x.x =" as your dns domain in the client.

DNS Round Robin is explainedin greater detail here: Round Robin DNS.


To Setup Network Load Balancing (NLB)

For setup, NLB protocol must be enabled on network interfaces and assigned a virtual IP address, depending on the version of Windows you are running. Alternatively, hardware loadbalancing (with a Layer 4 switch, for example) can achieve similar results.


  • Please make sure that you are running the latest build. To find out what the latest version/build is, kindly visit the following link:
  • Please note that in order to upgrade, you must have purchased the upgrade insurance, as licenses need to be upgraded in order to work on a later build.
  • To find out what is the version you currently have installed on your ThinClientServer, please open the console and check the currently installed version from the top right of your screen.
  • To find out what is the currently installed version of your 2X Application, please open the console and navigate to help>about.
  • Please kindly note that the issues and resolution presented on this article may be obsolete or no longer helpful with the latest version of your 2X Application. Should you require further assistance, please submit a ticket with Technical Support from the following link:
  • Please be aware that links related to 3rd parties like Microsoft, may sometimes be replaced or moved by the 3rd party itself.


(1336 vote(s))
Not helpful

Comments (0)
Post a new comment
Full Name: