HP Remote Graphics Software 7.0

independent of the RGS Receiver timeout properties. The RGS Sender begins by using the maximum
of the Rgsender.Network.Timeout.Error property and the Rgsender.Network.Timeout.Dialog property.
When the RGS Receiver negotiates its connection to the RGS Sender, it notifies the RGS Sender of
its error timeout property. For sync pulse timeout purposes, the RGS Sender adopts the minimum of:
Rgreceiver.Network.Timeout.Error
and the maximum of
{ Rgsender.Network.Timeout.Error AND Rgsender.Network.Timeout.Dialog }
For example, if the RGS Sender error timeout property is 30 seconds and the RGS Receiver error
timeout property is 20 seconds, the RGS Sender will use 20 seconds for its sync pulse timeout
because 20 seconds is the minimum of both. If the user adjusts the RGS Receiver error timeout
property to 60 seconds, the RGS Sender will use a value of 30 seconds for sync pulse timeout
because, again, 30 seconds is the minimum of both error timeouts.
If a RGS Sender sync pulse timeout occurs, the RGS Sender will terminate its connection to the RGS
Receiver. Unlike the local computer, which displays warning and error messages, the remote
computer does not display a message prior to terminating the connection. The user must initiate a
reconnection from the RGS Receiver to the RGS Sender to restore connectivity.
A relatively small RGS Sender error timeout property is recommended. If the RGS Receiver and
Sender connectivity is impacted by a network disruption, the RGS Sender can take as long as its
error timeout property to determine the connectivity loss, and fully terminate the connection. During
the time from the actual network disruption until the RGS Sender error timeout expires, the remote
computer will not send image updates to any other local computers (if the RGS Server is serving
multiple RGS Receiver connections). This will impact the interactivity of other users for no apparent
reason. After the RGS Sender error timeout expires, the RGS Sender will terminate the faulty
connection, and continue updating the other RGS Receivers.
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 RGS 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
Network settings on page 36 and adjust the RGS Receiver’s warning
timeout value found on the RGS Receiver Control Panel or the property
Rgreceiver.Network.Timeout.Warning.
●
The Remote Display Window dims, and the local computer disconnects, and displays a
“Connection closed” error dialog, but the user can often immediately connect again—Most likely
the network connectivity between the RGS Receiver and Sender was temporarily lost. Other
possible problems include:
◦
The RGS Sender unexpectedly terminated.
◦
The remote computer experienced a failure.
◦
The remote computer CPU utilization prevented the RGS Sender from making progress.
◦
The length of this connectivity loss exceeded the RGS Receiver’s error timeout value,
controlled by the RGS Receiver’s Rgreceiver.Network.Timeout.Error property, so the RGS
Receiver disconnected.
If this condition persists, it is possible that network disruptions are exceeding the RGS Receiver
error timeout value. If this is a network issue and is not resolvable, consider adjusting the error
Potential issues and suggestions 97