HP Xw460c Administrator's Guide for Microsoft Windows on HP ProLiant Blade Wor - Page 95

Troubleshooting RGS problems, Unable to connect using RGS Receiver, RGS performance problem

Get HP Xw460c - ProLiant - Blade Workstation PDF manuals and user guides View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 95 highlights

13-3 Troubleshooting RGS problems Also see the Chapter "Troubleshooting" in the HP Remote Graphics User's Guide for additional information on possible RGS problems and suggested solutions. Table 13-3 Troubleshooting RGS problems Problem Cause Unable to connect using RGS Receiver A connection cannot be established The proper DNS suffixes for your using the Remote Graphics network have not been entered. Receiver if the host name is used instead of the IP address. RGS performance problem Client performance might appear to A background with a large be impacted when using a photo or gradient of patterns or colors patterned bitmap for your blade causes the RGS application to use workstation desktop background. additional bandwidth which reduces the bandwidth available for other network traffic. Suggestions 1 On the client, ensure that the correct DNS suffixes for your blade workstation network have been entered. 2 Use the IP address instead of the hostname to connect to the blade. Use a plain colored bitmap for your system desktop background. RGS connection failure If multiple user accounts exist in To connect to the workstation from Ensure that the user name used at Windows on the blade workstation, the client, the user starts the RGS the RGS authentication prompt the Remote Graphics connection application. The authentication matches the Windows user account can fail if the RGS application login prompt prompts the user to input a and when logging out of the one does not match the user names valid network domain and user Windows user session to log into between the active Windows name. This user name must match another. session and the RGS. the Windows user account name when logging onto the workstation. If you input a different Windows user account name, an "Authorization failed!" error results. Another example, after a successful RGS connection to the workstation is made as Windows user X, this connection only remains viable as long as the user X account remains active. If the user logs out of the Windows user X session, and then logs back into Windows as user Y, a "Connection Lost!" error appears. Troubleshooting the blade workstation solution 95

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
Troubleshooting the blade workstation solution
95
13-3 Troubleshooting RGS problems
Also see the Chapter “Troubleshooting” in the
HP Remote Graphics User’s Guide
for additional information on
possible RGS problems and suggested solutions.
Table 13-3
Troubleshooting RGS problems
Problem
Cause
Suggestions
Unable to connect using RGS Receiver
A connection cannot be established
using the Remote Graphics
Receiver if the host name is used
instead of the IP address.
The proper DNS suffixes for your
network have not been entered.
1
On the client, ensure that the
correct DNS suffixes for your
blade workstation network
have been entered.
2
Use the IP address instead of
the hostname to connect to the
blade.
RGS performance problem
Client performance might appear to
be impacted when using a photo or
patterned bitmap for your blade
workstation desktop background.
A background with a large
gradient of patterns or colors
causes the RGS application to use
additional bandwidth which
reduces the bandwidth available
for other network traffic.
Use a plain colored bitmap for your
system desktop background.
RGS connection failure
If multiple user accounts exist in
Windows on the blade workstation,
the Remote Graphics connection
can fail if the RGS application login
does not match the user names
between the active Windows
session and the RGS.
To connect to the workstation from
the client, the user starts the RGS
application. The authentication
prompt prompts the user to input a
valid network domain and user
name. This user name must match
the Windows user account name
when logging onto the workstation.
If you input a different Windows
user account name, an
“Authorization failed!” error results.
Another example, after a successful
RGS connection to the workstation
is made as Windows user
X
, this
connection only remains viable as
long as the user
X
account remains
active. If the user logs out of the
Windows user
X
session, and then
logs back into Windows as user
Y
,
a “Connection Lost!” error appears.
Ensure that the user name used at
the RGS authentication prompt
matches the Windows user account
and when logging out of the one
Windows user session to log into
another.