HP Remote Graphics Software 5.4.8 User Guide
7. Network Interface binding—Beginning with RGS 5.4.0 the Sender defaults to listening to
multiple network interfaces if the computer is so equipped. If the Remote Computer has multiple
network interfaces, the Sender will dynamically add or remove network interfaces without
restarting the Sender. This topic is expanded considerably in
Network Interface binding on the
Sender on page 94 .
8. Linux Sender machine name and IP address—The default on Linux is to bind the machine
name to the following loopback interface in the /etc/hosts file:
127.0.0.1 blade2 localhost.localdomain
The RGS Sender will not accept remote connections with this configuration. Edit the /etc/hosts file
and bind the machine name to its proper IP address as follows:
127.0.0.1 localhost localhost.localdomain
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
9. 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.
10. 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 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 Sender is using private IP addresses
by typing the following in a command window:
netstat -n -a
If the IP address associated with the 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
11. 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.
Remote Computer (Sender) checklist
93