HP Remote Graphics Software 7.0

88.1.89.122 blade2 blade2.datacenter.com
For Linux systems with multiple network interfaces, each IP address must be listed in the /etc/
hosts file, for example:
192.168.89.122 blade2 blade2.datacenter.com
192.168.90.111 blade2b blade2b.datacenter.com
10. User-started X environments do not reliably support outside connections—Users who manually
start X desktops (such as with startx) from the console command line will find that outside
access attempts may not properly connect or be authenticated. This stems primarily from
incomplete PAM session management and permissions to the console. Users should avoid this
condition, and achieve login management through the display manager launched in init-level 5 of
the system.
11. Windows APIPA (Automatic Private IP Addressing)—APIPA can cause the RGS Sender to open
sockets on private IP addresses. This can occur, for example, if the RGS Sender computer is
unable to connect to a DHCP server. Because the private IP addresses are not visible to the
RGS Receiver, RGS connections will not work. You can verify if the RGS Sender is using private
IP addresses by typing the following in a command window:
netstat -n -a
If the IP address associated with the RGS Sender port (listening port 42966) is private, APIPA is
the likely cause. For more information on this topic, go to:
http://support.microsoft.com/kb/
220874.
12. Log out—If you do log into the remote computer to verify any of the above items, ensure that you
log out when you’re done.
RGS Sender network interface binding
The RGS Sender is set by default to listen to all network interfaces present on the remote computer.
If this is undesirable, the network interface binding can be manually reconfigured.
There are three methods to reconfigure RGS Sender network interface binding:
●
Disable the network interfaces that you do not want the RGS Sender to listen to, and then restart
the remote computer. The RGS Sender will then bind to the remaining enabled network
interface. The disadvantage of this method is that the other network interfaces will no longer be
usable.
●
Disable the RGS Sender property that causes it to listen to all network interfaces, and then
manually configure the desired network interface to be the one listened to by the RGS Sender.
See
Reconfiguring network interface binding manually on page 26 for more information.
●
Disable the RGS Sender property that causes it to listen to all network interfaces, and then use
the RGS Sender network interface binding property to specify which network interface to listen
to. See
Reconfiguring network interface binding using RGS Sender properties on page 26 for
more information.
If you enter a hostname instead of an IP address when establishing an RGS connection, it is possible
that the hostname will resolve to the IP address of an incorrect network interface. This could be
caused by a number of factors, including how your DHCP and DNS servers are configured.
RGS Sender network interface binding 25