HP Z620 HP Remote Graphics Software 5.4.7 - Page 160

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

Page 160 highlights

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's 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 Adjusting Network timeout settings on page 139 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 Dialog timeouts on page 145 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 Sender network timeout properties on page 192 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 Sender on Linux on page 79 to determine if PAM is correctly configured. See Adjusting Network timeout settings on page 139 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 144 Chapter 6 Advanced capabilities

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226
  • 227
  • 228
  • 229
  • 230
  • 231
  • 232
  • 233
  • 234
  • 235
  • 236
  • 237
  • 238
  • 239
  • 240
  • 241
  • 242
  • 243
  • 244
  • 245
  • 246
  • 247

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’s 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
Adjusting Network timeout settings
on page
139
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
Dialog timeouts
on page
145
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
Sender network timeout properties
on page
192
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 Sender on Linux
on page
79
to determine if PAM is correctly configured. See
Adjusting Network timeout settings
on page
139
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
144
Chapter 6
Advanced capabilities