HP Z620 HP Remote Graphics Software 5.4.7 - Page 156

Network timeouts, Receiver network timeouts

Page 156 highlights

Network timeouts RGS uses TCP/IP over a standard computer network to transmit data. Although TCP/IP is a reliable transport mechanism, it does not guarantee network packet delivery. The TCP/IP network stack performs well on a relatively stable network. However, network issues beyond RGS can affect the probability and timing of network packet delivery. Possible network issues include: ● Network over-subscription, resulting in congestion and packet loss ● CPU utilization by other processes and tasks, starving the TCP/IP network stack ● Incorrectly configured or malfunctioning network switches, routers, and network interfaces ● A disconnected network cable To deal with such network issues, the Receiver and Sender support network timeout mechanisms to provide notification to the user of network issues. Receiver network timeouts RGS provides two user-settable Receiver timeout properties to allow you to optimize RGS for your particular network conditions (such as low-bandwidth or high-latency conditions). These properties allow you to specify timeout values that, if exceeded, will cause the RGS Receiver to take specific actions, such as displaying a warning dialog or closing the RGS connection. The two Receiver timeout properties are: ● Receiver warning timeout property-If this value is exceeded, the Receiver displays a network connection warning. ● Receiver error timeout property-If this value is exceeded, the Receiver closes the connection. The Receiver error and warning timeout properties can be set in the Receiver Control Panel (see Figure 6-23 Receiver Control Panel on page 141) and are specified in seconds. The Receiver timeout properties can also be set in the rgreceiverconfig file or on a command line-in both of these cases, the 140 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

Network timeouts
RGS uses TCP/IP over a standard computer network to transmit data. Although TCP/IP is a reliable
transport mechanism, it does not guarantee network packet delivery. The TCP/IP network stack
performs well on a relatively stable network. However, network issues beyond RGS can affect the
probability and timing of network packet delivery. Possible network issues include:
Network over-subscription, resulting in congestion and packet loss
CPU utilization by other processes and tasks, starving the TCP/IP network stack
Incorrectly configured or malfunctioning network switches, routers, and network interfaces
A disconnected network cable
To deal with such network issues, the Receiver and Sender support network timeout mechanisms to
provide notification to the user of network issues.
Receiver network timeouts
RGS provides two user-settable Receiver timeout properties to allow you to optimize RGS for your
particular network conditions (such as low-bandwidth or high-latency conditions). These properties
allow you to specify timeout values that, if exceeded, will cause the RGS Receiver to take specific
actions, such as displaying a warning dialog or closing the RGS connection. The two Receiver timeout
properties are:
Receiver warning timeout property
—If this value is exceeded, the Receiver displays a
network connection warning.
Receiver error timeout property
—If this value is exceeded, the Receiver closes the
connection.
The Receiver error and warning timeout properties can be set in the Receiver Control Panel (see
Figure
6
-
23
Receiver Control Panel
on page
141
) and are specified in seconds. The Receiver timeout
properties can also be set in the rgreceiverconfig file or on a command line—in both of these cases, the
140
Chapter 6
Advanced capabilities