HP Remote Graphics Software (RGS) Instrukcja Użytkownika Strona 114

  • Pobierz
  • Dodaj do moich podręczników
  • Drukuj
Przeglądanie stron 113
When connecting to the remote computer, the authorization dialog is not displayed long enough for
the user to respond to it—This is likely caused by the RGS Sender’s dialog timeout value being too
small. See
RGS Sender properties on page 91 for further details on the property
Rgsender.Network.Timeout.Dialog. The default value for this property is 15 seconds.
When connecting to a Linux remote computer, the PAM authentication often fails—There are several
reasons why this might occur:
PAM may be configured incorrectly.
The user could be entering incorrect credentials.
The timeouts are too short.
See
Installing the RGS Sender on Linux on page 20 to determine if PAM is correctly configured. See
Network settings on page 36 for further details on setting timeouts. The user could try increasing the
RGS Receiver’s network dialog timeout as well as the RGS Sender’s error and dialog timeouts to see if
this helps. If this does not help and the user is convinced that the timeouts are not being exceeded, then
it is likely a PAM authentication configuration problem.
The Remote Display Window is not updating and appears to be hung—This is most likely caused by a
network disruption. You can adjust the warning timeout to get notification when this occurs. You can
also adjust the error timeout to disconnect and dismiss the Remote Display Window sooner. The default
warning timeout is two seconds. The default error timeout is 30 seconds. See
Network settings
on page 36 for further details on setting the RGS Receiver timeouts.
Increasing the RGS Receiver error dialog timeout doesn’t appear to have an effect and the RGS
Receiver still disconnects—This is likely caused by either:
A network failure resulting in detecting lost connectivity by the RGS Receiver (resulting in a
disconnected connection)
The RGS Sender timeouts are shorter than the RGS Receiver’s timeouts, and the RGS Sender
disconnects the RGS Receiver.
It is not always the case that network error timeouts are honored. A network error timeout only
establishes an upper bound on the duration of retries before returning with an error. If the computer
determines that network connectivity is lost and an error returns by the network stack to the RGS
Receiver, then the connection will disconnect sooner than the error timeout setting. If the RGS Sender’s
timeout values are shorter than the RGS Receiver’s, the RGS Sender may close the connection sooner
than the RGS Receiver, disconnecting the RGS Receiver. If the issue continues, consider increasing the
RGS Sender's error timeout value. See
Network settings on page 36 for further details on setting
timeouts.
Troubleshooting graphics performance
The dominant factor impacting performance on the remote computer is the frame buffer read performance
of the graphics adapter. Frame buffer read performance of at least ten frames per second is recommended
for optimum RGS performance.
RGS uses the remote computer’s graphics adapter to accelerate rendering of the image. After the image on
the remote computer is modified, the RGS Sender reads the rendered image from the frame buffer,
compresses it, and transmits it to the RGS Receiver.
On Windows, use the BltTest tool to test the frame buffer read performance of the remote computer. This
tool is available at:
http://www.stereopsis.com/blttest/.
Troubleshooting Remote Audio
Several potential audio issues are described below along with their potential causes.
102 Appendix B Troubleshooting
Przeglądanie stron 113

Komentarze do niniejszej Instrukcji

Brak uwag