HP Xw460c - ProLiant - Blade Workstation User Manual page 75

you disable Guest logins on the Remote Computer. To disable this policy, open the "Control Panel", selecting
"Administrative Tools", selecting "Local Security Policy", expanding the "Local Policies", expanding "Security
Options", and setting "Network access: Sharing and security model for local accounts" to "Classic – local
users authenticate as themselves". For more information on this topic, go to:
support.microsoft.com/kb/103674
Ensure that the RGS Sender is running on the Remote Computer—This can be done on Windows as follows:
•
a. Click on Start
b. Right click on My Computer
c. Select manage from the menu.
d. In the Computer Management console, click the + sign to expand Services and Applications and select
Services. The service Remote Graphics Sender should be listed as "Started".
Verify that the rgdiag.exe diagnostics tool passes all tests on the RGS Sender on Windows—This tool is
•
automatically executed after completion of a normal Sender installation on Windows. It can also be run any
time after Sender installation. Refer to the section
information on running this tool.
Ensure that the Sender knows its current IP address— If the Sender computer has changed networks and has
•
been assigned a new IP address after the Sender was started, you'll need to restart the Sender
service/daemon.
NIC binding—If the Remote Computer has multiple NICs, ensure that you attempt to connect to the same NIC
•
that the RGS Sender is "listening" to. This topic is expanded considerably in Section 4-3 below.
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
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
88.1.89.122
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.
Microsoft 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:
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:
support.microsoft.com/kb/220874
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.
"Using the RGS Diagnostics Tool on
blade2 localhost.localdomain
localhost localhost.localdomain
blade2 blade2.datacenter.com
netstat -n -a
Windows" for
Pre-connection checklist 75