HP ProLiant xw2x220c Remote Graphics Software 5.2.5 User Guide - Page 120
Network timeout issues, When connecting to a Linux Remote Computer
View all HP ProLiant xw2x220c manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 120 highlights
Network timeout issues Listed below are several timeout-related issues and their potential causes. • Remote Display Window repeatedly dims, and displays a connection warning message-This is likely caused by frequent network disruptions between the Receiver and Sender. The dimming of the display serves as a notification to the user that the Remote Display Window may contain stale information. If frequent notifications are annoying, and the network issues do not improve, see the section "Using Timeouts" and adjust the Receiver's warning timeout value found on the Receiver Control Panel or the property Rgreceiver.Network.Timeout.Warning. • The Remote Display Window dims, the Receiver disconnects, and displays a "Connection closed" error dialog, but the user can often immediately connect again-Most likely the network connectivity between the Receiver and Sender was temporarily lost. Other possible problems include: • The Sender unexpectedly terminated. • The Remote Computer experienced a failure • The Remote Computer CPU utilization prevented the Sender from making progress, • The length of this connectivity loss exceeds the Receiver's error timeout value, controlled by the Receiver Rgreceiver.Network.Timeout.Error property so the Receiver disconnected. If this condition persists, it is possible that network disruptions are exceeding the Receiver error timeout value. If this is a network issue and is not resolvable, 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 Section 6-4, "Network timeouts," for further details. • When connecting to a Linux Remote Computer, 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 the Receiver dialog timeout value being too small. See 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 the Remote Computer, 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 Section 8-6-4, "Sender network timeout properties," 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 Section 3-2-4, "Installing the Sender on Linux," to determine if PAM is correctly configured. See Section 6-4, "Network 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-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 Section 6-4, "Network timeouts," for further details on setting the Receiver timeouts. • Increasing the Receiver error dialog timeout doesn't appear to have an effect and the Receiver still disconnects-This is likely caused by either: • A network failure resulting in detecting lost connectivity by the Receiver (resulting in a disconnected connection) • The Sender timeouts are shorter than the Receiver's timeouts, and the Sender disconnects the 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 Receiver, then the connection will disconnect sooner than the error timeout setting. If the Sender's timeout values are shorter than the Advanced capabilities 120