HP Remote Graphics Software 5.4.0 User Guide

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, see

Using RGS through a firewall on page 84.

Beginning in RGS 5.4.0, the Sender defaults to “listening” to all available network interfaces. The

Sender also has the ability to dynamically add or remove network interfaces and update I.P. address

changes of a network interface while there are no active RGS connections. If there are one or more

active RGS sessions, the Sender will update the network interface bindings after the connections are

disconnected. For instance, if an additional network interface is enabled and configured, the Sender

will add that network interface to the binding list and begin listening on that network interface for

connect requests. If the I.P. address of a network interface changes due to a DHCP change for instance,

the Sender will update the network interface binding. The Sender does not have to be restarted as with

previous versions of RGS to update network interface bindings.

NOTE: At RGS 5.2.5, the capability was added to specify the port number used by the RGS Sender.

The default Sender port number is 42966, as noted above. The Sender port number can be changed

using the Rgsender.Network.Port property. If this property is used to change the Sender port number

from its default value of 42966, the Sender port number must then be specified in establishing an RGS

connection from the Receiver to the Sender.

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-3 The

Remote Computer frame buffer containing the Windows desktop on page 15).

Figure 2-3 The Remote Computer frame buffer containing the Windows desktop

ENWW

Networking support