·   Wiki Home
 ·   Wiki Help
 ·   Categories
 ·   Title List
 ·   Uncategorized Pages
 ·   Random Page
 ·   Recent Changes
 ·   RSS
 ·   Atom
 ·   What Links Here

Active Members:



Create or Find Page:


View Migration to Load Balancing

Category:Hosted Accounts

About Server Load Balancing

Hudson maintains a large number of Terminal Servers, which hosted clients connect to when trying to access and run their Hudson applications. Most clients are connecting to a shared server, meaning that they are connecting to a remote computer that is also being accessed by users from other companies as well.  Hudson has generally monitored and managed how many individual users can access any single Terminal Server at one time. In this way, Hudson is able to ensure that the server is not overloaded or “bogged” down by an excessive number of users.  Hudson has essentially manually balanced the “load” on each of these machines.

We are pleased to announce that we have implemented an automated process for balancing this load.  By implementing this change, it affords both our clients, and our own support staff, greater flexibility in managing the server network and ensuring that applications run at optimum speeds.

From here forward, when you connect to a Hudson server, using Remote Desktop Protocol (RDP), you should enter the server address to be connected to as TSL01.HUDSONLTD.NET  (not case sensitive).  When the network senses a user trying to connect, it evaluates all of the machines in the network and then routes you to that machine which is currently running the fastest (typically the fewest users).  Your login name and password remain unchanged.  When your connection is complete, you will see the same program icons and shortcuts that you have become accustomed to.

Should you ever experience a situation during your work day when the machine you are connected to seems “sluggish” or not as responsive as expected, you should close down your Hudson applications and then “Log Off” of the Hudson Terminal Server, using the standard Windows LogOff procedure:  Click the START button in lower left corner, select the LogOff option.  You can immediately log back in again by launching the RDP icon on your computer workstation, ensuring you are logging in to TSL01.HUDSONLTD.NET.  You will then be connected (most likely) to a different Terminal Server and should see improved performance.  If your connection still appears to be slow, please contact Hudson Tech Support for additional troubleshooting assistance.

By having this new Load Balancing technology in place, Hudson will also be able to schedule and perform server hardware maintenance and updates.  If you ever receive a notice on your screen while you are working, indicating that the server will be taken off-line for service, please complete your current task (reservation, report, etc.) and then Log Off of the server.  As mentioned in the paragraph above, you may then immediately log back in, and you will be routed to a new machine.  In this manner, no hosted client should ever be forced to be “offline” and without access to their Hudson applications.

Where to make the change

Most users probably have an icon or shortcut on their Windows Desktop. It may be labeled “Hudson” or it may be labeled “Remote Desktop”.  Others might have to browse for the icon by going to Start > All Programs > Accessories > Communications > Remote Desktop.  In either scenario, when you click the shortcut, before connecting, you should be able to see or select the “Computer” that you are connecting to.  This is the place where you will enter: TSL01.HUDSONLTD.NET (that is a zero in the string TSL01). (NOTE: Depending on your version of Windows (e.g. Vista), when you are connecting to the Terminal Server you may need to enter your user name as HUDSONTS\UserName01).

If you click the icon and are connected immediately, without the ability to see or change the computer name, then right click on the icon and select the “Properties” option from the menu.  If neither of these solutions applies to your situation, please give Hudson Tech Support a call and we will be glad to assist.


A very few clients have reported that after the change to the load balancing process their Remote Desktop Protocol session (RDP) has been spontaneously disconnected.  These incidents have been very few and isolated. Working with the Technicians at the Server Hosting facility, Hudson is confident that this is not related to the implementation of the load balancing program but may be due to problems with a customer router, or the version of Microsoft RDP that is running on the individual client workstations.  If you have experienced a problem involving spontaneous disconnection, please visit the Microsoft support site ( )  to ensure you are running the latest version of the RDP application.  If the problem persists, please contact Hudson Tech Support and be prepared to explain in as much detail as possible what conditions exist at the time of a disconnect and how many workstations are effected.