HP Xw460c Remote Graphics Software 5.3.0 User Guide - Page 123
Dialog timeouts, See
View all HP Xw460c manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 123 highlights
Receiver's, the Sender may close the connection sooner than the Receiver, disconnecting the Receiver. If the issue continues, consider increasing the Sender's error timeout value. See Section 6-4, "Network timeouts," for further details on setting timeouts. 6-4-2 Dialog timeouts RGS supports dialog timeouts, which specify how long user interactions between the Local Computer and Remote Computer are allowed to take. The two dialog timeout properties are: • Receiver dialog timeout property-This property specifies the maximum time that the Receiver (Local Computer) will wait for a dialog response from the Remote Computer in response to a message sent to the Remote Computer. It also specifies how long dialogs initiated by the Remote Computer will be displayed to the user on the Local Computer. • Sender dialog timeout property-This property specifies the maximum time that a message, originating from the Receiver, will be displayed on the Remote Computer. It also specifies how long the Remote Computer Sender will wait for a dialog response from the Receiver. For example, assume that a local user is attempting to connect to a Remote Computer. Assume, furthermore, that another user is already logged into the Remote Computer (this person is therefore the primary user). The Sender will prompt the primary user for authorization to connect the local user to the Remote Computer. The duration of this prompt is set by the Rgsender.Network.Timeout.Dialog property. The Receiver property Rgreceiver.Network.Timeout.Dialog limits how long the Receiver will wait for a response from the Remote Computer before returning failure. If the Rgsender.Network.Timeout.Dialog timeout expires without action by the primary user, the Sender dialog exits, and connection is denied by default. If the Sender times out, the Receiver will also time out (based on its Rgreceiver.Network.Timeout.Dialog property) because no authorization reply will be returned by the Sender. In the previous example, the dialog was displayed on the Remote Computer. An example of a dialog being displayed on the Local Computer follows. When a Receiver connects to a Sender running Linux, the Pluggable Authentication Module (PAM) on the Sender attempts to authenticate the connection. In this case, the PAM subsystem invokes a PAM conversation/callback function to the Receiver, causing the Local Computer to prompt the user with a PAM message dialog. The dialog typically requests a username and password. The timeout for the dialog on the Receiver is controlled by the Rgreceiver.Network.Timeout.Dialog property. If this timeout expires without the local user entering a username and password, the Receiver will remove the dialog. NOTE: The property Rgreceiver.Network.Timeout.Dialog does not control the duration of all dialogs displayed by the Receiver. For example, the authentication dialog for a Windows Sender connection displayed by the Receiver for username and password does not have an associated timeout since it is not an incoming message from the Sender to the Receiver. This dialog will be displayed indefinitely until the user responds "OK" or "Cancel" to its requests The Receiver dialog timeout property, Rgreceiver.Network.Timeout.Dialog, can be set using the Receiver Control Panel as shown in Figure 6-21, and has a default value of 15 seconds (15,000 milliseconds). This property can also be set using the rgreceiverconfig file and from a command line. The Sender dialog timeout property, Rgsender.Network.Timeout.Dialog, can only be set using the rgsenderconfig file and from a command line-there is no dialog on the Sender for setting this property. The default value of this property is also 15 seconds. The 15 second Receiver and Sender dialog timeouts should support most authorization and authentication scenarios. For more complex scenarios requiring additional time, the user should adjust both the Receiver and Sender dialog timeouts appropriately. Advanced capabilities 123