Specifications
41
1.1. Enter a name for the desktop. If more than one item is
available to the user, the name will be used on the 2X
desktop so that the user can identify which Terminal Server
he/she will be connecting to.
1.2. Select the protocol type from the drop down list:
Windows (RDP)*
Linux (NX)**
Citrix (ICA)***
1.3. Enter the server addresses and “Port Number” The
“Primary Address” may be a hostname or an IP address.
The default port number is automatically set when the
protocol type is selected – this value may be customized if
necessary. The “Secondary Address” can be added to
provide redundancy to a secondary NIC card or Terminal
Server. This address will be used if the user selects
“Reconnect” after the session has been disconnected.
1.4. Enable SSL to encrypt the data that is being passed for
communication. Specify the speed of you bandwidth that
you will use to connect to your remote desktops. Enable
“Auto Reconnect” if you would like to automatically
reconnect to you remote desktop if a connection is lost.
1.5. Specify the “Redirection Settings”
You may specify which redirection facilities (sound, disk,
printing, serial ports and smart card) will be available to this
protocol.
Please note that for a Windows (RDP) Full Desktop
Session
to run successfully, it will be necessary to
ensure that TCP connections on port 3389 to the
Windows Terminal Server can be established.
Please note that for a Citrix (ICA) Full Desktop Session
to run successfully, it will be necessary to ensure that
TCP connections on port 1494 to the Citrix Presenta
tion
Server can be established.
The “Citrix (ICA)” and “Citrix Published Applications”
protocols are only available in the Enterprise Edition.
This connection will bypass the Citrix load balancing and
provide direct connectivity to the server. If you wish
to
use Citrix load balancing configure a new published app.
If you use Citrix (ICA) you can enable a River Cipher
encryption for added security.
Please note that for a Linux (NX) Session to run
successfully, it will be necessary to ensure that TCP
connections on port 22 to the 2X TerminalServer can be
established.