HP Remote Graphics Software Troubleshooting
HP Remote Graphics Software Troubleshooting
Potential RGS issues and troubleshooting suggestions
Issue |
Suggestion |
|---|---|
Can not connect to the RGS Sender. |
Verify that the pre-connection checklist is satisfied as described in Chapter 4 of HP Remote Graphics Software User Guide 5.4.0. |
A connection is established but it appears to time out. |
Check the Network Timeout Section of HP Remote Graphics Software User Guide 5.4.0. |
Graphics performance appears slow. |
Check Optimizing RGS performance section of HP Remote Graphics Software User Guide 5.4.0. |
Remote USB does not work. |
Verify that USB has been correctly configured during Receiver installation on Windows XP. |
RGS error messages
Error |
Description |
|---|---|
Connection lost. |
The RGS Sender has closed the connection. Possible reasons include:
|
Authentication failed. |
The RGS Sender has refused to allow a connection. Possible reasons include the following:
|
Directory not found or not accessible. |
The directory file is not available. Possible reasons include:
|
User not found in directory. |
The username of the current user of the HP Remote Graphics Software Receiver is not found in the directory file. Possible reasons include:
|
Authorization failed. |
The connection was authenticated, but another user is already logged into the desktop of the Sender system. When a connection is attempted to another user’s desktop, a dialog is displayed on the Sender desktop asking the logged in user to allow the connection. A user is not allowed to connect to another user’s desktop unless they are explicitly authorized. Either the connection was not granted access, or the dialog timed-out and the connection was implicitly denied. |
Receiver License Not Found. |
A license was not found for the RGS Receiver. |
Receiver License Invalid. |
The license is invalid for the RGS Receiver. |
No license found for the sender you are trying to connect to. |
A license was not found for the RGS Sender. |
License Expired for the sender you are trying to connect to. |
The license has expired for the RGS Sender. |
License Invalid for the sender you are trying to connect to. |
The license is invalid for the RGS Sender. |
Setup Mode hotkey sequence too short. |
The key sequence specified by the user is too short. |
Setup Mode hotkey sequence too long. |
The key sequence specified by the user is too long. |
Setup Mode hotkey sequence may only consist of Ctrl , Alt , Shift and Space . |
The key sequence specified by the user contains invalid keys. |
A space may only be entered after Ctrl , Alt or Shift is pressed. |
The Setup Mode hotkey sequence cannot start with a space. |
Setup Mode hotkey sequence is invalid. The sequence has been reset to the default. |
The Setup Mode hotkey sequence specified using a property either on the command-line or in the property configuration file is invalid, and has been reset to the default. |
Setup Mode hotkey sequence is invalid. The sequence has been disabled. |
The Setup Mode hotkey sequence specified using a property either on the command-line or in the property configuration file is invalid, and the property Rgreceiver.Hotkeys.IsMutable is disabled. Therefore, hotkeys have been disabled. |
Connection denied. The iLO remote console is enabled. |
The iLO remote console is enabled on the HP Blade Workstation. The Blade must be configured in User Mode before connections are allowed. |
Unable to connect to Sender: The Receiver was unable to resolve the specified hostname or IP Address. Verify that you entered the value correctly. |
This is usually indicative of a DNS error. |
Unable to connect to Sender: The Receiver resolved the specified hostname or IP address, but cannot connect to the Sender. Verify that the system is accessible on your network and that the Remote Graphics Sender service has been started and is listening on a pubic IP address and is not blocked by a firewall. |
The Receiver was able to look up and resolve the specified hostname or IP address. However, the Receiver was unable to establish a connection to the Sender. There are several possibilities such as the Sender is not installed, the Sender is not running, the Sender is listening on the wrong network interface, or a firewall is blocking the Sender. |
cozy coffee shop ambience