Troubleshooting

Rgreceiver.Network.Timeout.Error property so the Receiver disconnected.

If this condition persists, then it is likely that network disruptions are exceeding the Receiver’s error timeout value. If this is a network issue and is not resolvable, then the user might consider adjusting the error timeout of the Receiver to reduce Receiver disconnection. Additionally, the Sender timeout might need to be increased too. Please refer to the section Using Timeouts for further details.

When connecting to a Linux or HP-UX system, the PAM authentication dialog displayed by the Receiver does not appear long enough to enter the user’s credentials such as username and password:

This is likely caused by too small of a Receiver’s dialog timeout value. Please refer to the section “Using Timeouts” for further details on setting timeouts. The user should first check the Receiver Control Panel to determine the Network dialog timeout setting and adjust as appropriate.

When connecting to a Sender, the authorization dialog is not displayed long enough for the user to respond to it:

This is likely caused by too small of a Sender’s dialog timeout value. Please refer to the section Using Timeouts for further details on the property Rgsender.Network.Timeout.Dialog. The default value for this property is 15 seconds.

When connecting to a Linux or HP-UX system 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, or

∙the timeouts are too short.

Please refer to the section Installing the Sender to understand if PAM is correctly configured. Please refer to the section Using Timeouts for further details on setting timeouts. The user could try increasing the Receiver’s network dialog timeout as well as the 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:

Most likely a network disruption. The user can adjust the warning timeout to get notification when this occurs. The user 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. Please refer to the section Using Timeouts for further details on setting the Receiver timeouts.

131