User guide

RGS overview 21
2-5 Sender and Receiver interoperability
RGS provides interoperability between versions of RGS Senders and Receivers that have the same major version
number. For example, Sender version 5.0 and Receiver version 5.1 will interoperate together. However, Sender
version 4.2 is not guaranteed to interoperate with Receiver version 5.0. Connection between a Receiver and a
Sender should only be attempted when their major version numbers are the same.
2-6 Application support
Except as noted in the next paragraph, RGS provides application transparency, meaning that the Local Computer
user, in executing applications on the Remote Computer, is typically unaware that the application is executing
remotely.
RGS supports all applications, except gaming applications and those applications that use full screen exclusive
mode. If a full-screen MS-DOS command prompt window is created on the Sender (using, for example,
command.com), the window will be reset to its default size by RGS. Likewise, if a full-screen Windows XP
command prompt window is created (using cmd.exe or the command prompt icon), the window will also be
reset to its default size by RGS. Full-screen DirectDraw applications are not supported (however, DirectDraw
applications in a Window may work, and should be qualified individually).
2-7 Networking support
RGS uses TCP/IP over a standard computer network, and supports Ethernet connection speeds of
10/100/1000BASE-T (Gigabit). The RGS Sender listens on TCP/IP port 42966. The port used by the RGS
Receiver is assigned by the Local Computer OS and can vary. HP recommends full-duplex operation between the
Sender and Receiver.
For information on using RGS through a firewall, refer to Section 4-4, “Using RGS through a firewall.”
2-8 Connection topologies
This section describes the connection topologies supported by RGS, such as how a single Local Computer may
connect to multiple Remote Computers.
2-8-1 The Remote Computer frame buffer
After making a connection between a Local Computer and a Remote Computer, the Remote Computer Sender
transmits its complete frame buffer to the Local Computer. The frame buffer is the memory on the Remote
Computer video adapter that holds the bitmapped image that is typically displayed on a monitor—for Windows
XP, the frame buffer contains the familiar Windows desktop (see Figure 2-5).
Figure 2-5 The Remote Computer frame buffer containing the Windows desktop
The monitor itself is optional on the Remote Computer. For example, if the Remote Computer is a Personal
Workstation, a monitor (plus a keyboard and mouse) would typically be attached. If the Remote Computer is an
HP ProLiant xw460c Blade Workstation, it is not possible to attach a monitor to view the primary (NVIDIA) frame
buffer because the video signal from the NVIDIA graphics adapter is not available on a connector—the contents
of the frame buffer can only be viewed remotely using RGS.
Remote
Computer
(optional)
frame
buffer
to Local Computer
TCP/IP