HP ProLiant xw2x220c Remote Graphics Software 5.3.0 User Guide - Page 118

Adjusting Network timeout settings, 4-1 Network timeouts

Page 118 highlights

6-4 Adjusting Network timeout settings The options available under the Network tab in the Receiver Control Panel are shown in Figure 6-20. Figure 6-20 Options available under the Network tab RGS supports three classes of user-settable timeouts: 1. Receiver network timeout properties-After the Receiver has established a connection to the Sender, the Sender transmits sync pulses (consisting of network messages) to the Receiver every second to permit the Receiver to determine connection integrity. If the Receiver fails to detect the sync pulses, the Receiver compares the time since the last sync pulse was received to two user-settable Receiver network timeout properties: • Receiver warning timeout property • Receiver error timeout property 2. Sender network timeout property-After the Receiver has established a connection to the Sender, the Receiver likewise transmits sync pulses to the Sender every second to permit the Sender to also determine connection integrity. If the Sender fails to detect the sync pulses, the Sender compares the time since the last sync pulse was received to the user-settable Sender network timeout property. 3. Dialog timeouts-Dialog timeouts control how long user interactions between the Sender and Receiver are allowed to take. The Receiver and Sender network timeout properties are discussed in the next section. Dialog timeouts are discussed in Section 6-4-2, "Dialog timeouts." 6-4-1 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 NICs • 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. Advanced capabilities 118

  • 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

Advanced capabilities 118
6-4 Adjusting Network timeout settings
The options available under the
Network
tab in the Receiver Control Panel are shown in Figure 6-20.
Figure 6-20
Options available under the Network tab
RGS supports three classes of user-settable timeouts:
1.
Receiver network timeout properties
—After the Receiver has established a connection to the Sender, the
Sender transmits
sync pulses
(consisting of network messages) to the Receiver every second to permit the
Receiver to determine connection integrity. If the Receiver fails to detect the sync pulses, the Receiver
compares the time since the last sync pulse was received to two user-settable Receiver network timeout
properties:
Receiver warning timeout property
Receiver error timeout property
2.
Sender network timeout property
—After the Receiver has established a connection to the Sender, the
Receiver likewise transmits sync pulses to the Sender every second to permit the Sender to also determine
connection integrity. If the Sender fails to detect the sync pulses, the Sender compares the time since the last
sync pulse was received to the user-settable Sender network timeout property.
3.
Dialog timeouts
—Dialog timeouts control how long user interactions between the Sender and Receiver are
allowed to take.
The Receiver and Sender network timeout properties are discussed in the next section. Dialog timeouts are
discussed in Section 6-4-2, “
Dialog timeouts
.”
6-4-1 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 NICs
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.