HP Remote Graphics Software 7.0

RGS error messages
This section lists the error messages reported by the RGS Receiver and describes possible reasons
for them.
Table B-2 RGS Receiver error messages
Error Description
Connection lost! The RGS Sender has closed the connection. Possible
reasons include:
●
The RGS Sender might have explicitly disconnected
your connection. For example a user might have
selected disconnect all connections from the RGS
Sender icon or RGS Sender GUI or the user might have
logged off.
●
Another user has connected to the RGS Sender using
the same username and password.
●
If you connected to a desktop that was not logged in
and another user logged in your connection will be
disconnected.
●
If you were connected to a logged in desktop and the
logged in user disconnects your connection will be
disconnected too.
●
The network may have been disconnected, closed, or
temporarily disrupted.
●
The RGS Sender service/daemon may have been
stopped, restarted, or killed.
●
The RGS Sender system may have been stopped/
shutdown or restarted.
●
If connecting to a Linux computer, the X Server may
have been stopped or restarted.
●
The RGS Sender or X Server may have experienced a
failure.
Unable to connect to Sender! If this error is reported, see
Pre-connection checklist
on page 23 for a list of possible causes.
Authentication failed! The RGS Sender has refused to allow a connection.
Possible reasons include the following:
●
The authentication credentials that you entered, such as
domain name, user name and password, are not valid
or recognized by the remote computer.
●
The RGS Sender's authentication is not configured
appropriately. See the user's manual and README.txt
for the latest directions and issues with respect to
configuring authentication.
Directory not found or not accessible! The directory file is not available. Possible reasons include:
●
The directory file name or location has been mistyped.
●
The file has been moved or is no longer available.
●
The network is down or experiencing a disruption.
●
The user does not have read permission on the file.
102 Appendix B Troubleshooting