|
|
Fig.5 - The General tab.
|
Server Host
Specify the hostname or IP address of the machine where NX Server has to be contacted for
starting the session.
Server - Port
Specify the port where the SSH daemon is listening on the NX Server host machine. By default
the port is 22.
Server - Remember my password
Store your password in the session file. Next time you need to run that session, NX Client will
not ask you to insert the username and password in the login dialog. This allows you to automate
login by simply clicking on the session configuration icon saved on your local desktop. NX Client
stores the password in a scrambled format. More information about the password scrambling
algorithm in NX Client is available at:
http://www.nomachine.com/ar/view.php?ar_id=AR01C00125
Server - Key
Use customized SSH keys to access NX Server. More information about replacing the default SSH keys
used by NX with keys generated for your server is available at:
http://www.nomachine.com/ar/view.php?ar_id=AR01C00126
Desktop
Select the session type to be run on the server. You may choose among:
Unix run either a X11 desktop as KDE, GNOME, CDE and XDM or a single application by
choosing the Custom option.
Windows run a RDP session on a Windows Terminal Server.
VNC run a VNC session on a VNC server.
Shadow attach to an already running X11 session or to the native display (session shadowing
and desktop sharing).
Some session types may require additional settings. For example the 'Windows settings' panel is
for specifying hostname for the RDP server, while the 'VNC settings' panel is for specifying hostname
and port for the VNC server. You may refer to the following article to get more information on
support for RDP and VNC sessions with NX 3.0.0 or higher:
http://www.nomachine.com/ar/view.php?ar_id=AR06E00469
|
Fig.6 - Sample settings for an RDP session on NoMachine Testdrive.
|
In the "Custom Settings" panel you may instead specify the remote application to be run in seamless
mode. When the "Floating window" option is selected, nxagent operates in rootless mode, i.e. it
impersonates the application's display and can rewrite the X traffic down to the real X server to hide
the details of the network and be extremely bandwidth efficient. When the "Disable X agent encoding"
option is selected, the NX proxy tunnels the raw X protocol traffic. NX can't do much in this case,
other than compress the X traffic better than any known generic compressor. The application, in fact,
is connected to the real display and so it will still suffer from all the limitations of the X system.
Running the single application as "New virtual desktop" still reaps the
benefits of the nxagent capabilities, but, in this case the agent is not running in rootless mode, i.e. the the application window may not match
the local desktop size and may be displayed inside a black parent window.
|
Fig.7 - Sample settings for running the console
in rootless mode on NoMachine Testdrive.
|
Desktop - Link type
Set the type of network connection that is going to be used to connect to the remote proxy. Some
session parameters, such as the compression level, depend on this setting. For example, the link
MODEM uses high compression levels for both protocol and images, while the link LAN disables the
protocol compression and uses a low compression level for the image encoding, to make the best use
of the available bandwidth.
The image encoding can be customized regardless of the link type. The different encoding types are
explained in the Display - Use custom settings - Unix display settings section in this document.
Lazy encoding policies, i.e. the ability to defer image updates, are activated by default for all
link types other than for LAN. However, you have the possibility to disable deferred screen
updates in the NX Client GUI -> Advanced tab.
Display
Set the size for the X server window. In the case of 'Shadow' desktop type, when a different size other than
'As on the server' is selected, the X11 agent applies its own screen scaling capabilities.
Display - Use custom settings - Unix display settings
|
Fig.8 - The General tab and the
Unix - Display settings dialog for X11 sessions.
|
Unix - Display settings Images
You can force the selected image encoding to be used, overriding the default encoding set according
to the link type.
-
Use both JPEG and RGB compression
The adaptive compression dynamically selects a lossy or a lossless encoding depending on how
compressible the image data is.
-
Only use JPEG compression
Use only the lossy encoding. This kind of compression is advisable on slow links, because a
low image quality is covered by a minor amount of image data to transfer.
-
Only use RGB compression
Use only the lossless encoding. This compression is advisable on fast links, since the high
image quality increases the data to be sent.
-
Use plain X bitmaps
The compression is disabled and images are sent in raw format. This setting is advised only
on fast and wide links, because of the large amount of image data to transfer.
-
Quality - Use custom JPEG quality
Specify the JPEG compression level. A lower level value means poorer image quality but higher
data compression.
Unix - Display settings Performance
-
Disable the render extension
Disable the use of render protocol extension between the X server and the X11 agent. This
can become necessary when you need to migrate your session to a display of a X server missing
the render extension.
-
Disable the backing-store
Disabling the use of backing-store may degrade NX performances, but can be useful in case you
need to lower memory usage on either server and client side.
-
Disable the composite extension
Disable use of X server's composite extension in X11 agent.
-
Disable the shared memory extension and Disable emulation of shared pixmap
Disabling shared pixmap emulation between X11 agent and X server may increase NX performance,
since the pixmap created on the X server can't be shared, but has to be kept updated.
Note that, since a number of applications using shared pixmap don't check if shared pixmap is
available, these applications won't work if shared memory is enabled and shared pixmap is
disabled.
Display - Use custom settings - Windows display settings
-
Colors
Define the number of colors to be set for the RDP session. This setting applies to the RDP
client run for establishing the RDP session with the Windows Terminal Server.
-
Images
Force the selected image encoding to be used, overriding the default encoding set according
to the link type. This setting applies to the X11 session inside which the RDP session is running.
For more details, refer to Unix display settings.
-
Cache
Enable the RDP image cache. This setting applies to the RDP client run for establishing the RDP
session with the Windows Terminal Server.
Display - Use custom settings - VNC display settings
-
Images
Force the selected image encoding to be used, overriding the default encoding set according
to the link type. This setting applies to the X11 session inside which the VNC session is running.
For more details, refer to Unix display settings.
|
