HP Z620 HP Remote Graphics Software 5.4.7 - Page 31

Networking support, Connection topologies, The Remote Computer frame buffer - memory

Page 31 highlights

On Remote Computers running Linux, OpenGL-based applications can only be remoted if the Remote Computer is using NVIDIA graphics. RGS 5.2.6 and newer Sender and Receiver executables are signed for compatibility with strict antivirus programs. Networking support RGS uses TCP/IP over a standard computer network, and supports Ethernet connection speeds of 10/100/1000BASE-T (Gigabit). The RGS Sender listens on TCP/IP port 42966. The port used by the RGS Receiver is assigned by the Local Computer OS and can vary. HP recommends full-duplex operation between the Sender and Receiver. For information on using RGS through a firewall, see Using RGS through a firewall on page 91. Beginning in RGS 5.4.0, the Sender defaults to "listening" to all available network interfaces. The Sender also has the ability to dynamically add or remove network interfaces and update I.P. address changes of a network interface while there are no active RGS connections. If there are one or more active RGS sessions, the Sender will update the network interface bindings after the connections are disconnected. For instance, if an additional network interface is enabled and configured, the Sender will add that network interface to the binding list and begin listening on that network interface for connect requests. If the I.P. address of a network interface changes due to a DHCP change for instance, the Sender will update the network interface binding. The Sender does not have to be restarted as with previous versions of RGS to update network interface bindings. NOTE: At RGS 5.2.5, the capability was added to specify the port number used by the RGS Sender. The default Sender port number is 42966, as noted above. The Sender port number can be changed using the Rgsender.Network.Port property. If this property is used to change the Sender port number from its default value of 42966, the Sender port number must then be specified in establishing an RGS connection from the Receiver to the Sender. Connection topologies This section describes the connection topologies supported by RGS, such as how a single Local Computer may connect to multiple Remote Computers. The Remote Computer frame buffer After making a connection between a Local Computer and a Remote Computer, the Remote Computer Sender transmits its complete frame buffer to the Local Computer. The frame buffer is the memory on the Remote Computer video adapter that holds the bitmapped image that is typically displayed on a Networking support 15

  • 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

On Remote Computers running Linux, OpenGL-based applications can only be remoted if the Remote
Computer is using NVIDIA graphics.
RGS 5.2.6 and newer Sender and Receiver executables are signed for compatibility with strict anti-
virus programs.
Networking support
RGS uses TCP/IP over a standard computer network, and supports Ethernet connection speeds of
10/100/1000BASE-T (Gigabit). The RGS Sender listens on TCP/IP port 42966. The port used by the
RGS Receiver is assigned by the Local Computer OS and can vary. HP recommends full-duplex
operation between the Sender and Receiver. For information on using RGS through a firewall, see
Using RGS through a firewall
on page
91
.
Beginning in RGS 5.4.0, the Sender defaults to “listening” to all available network interfaces. The
Sender also has the ability to dynamically add or remove network interfaces and update I.P. address
changes of a network interface while there are no active RGS connections. If there are one or more
active RGS sessions, the Sender will update the network interface bindings after the connections are
disconnected. For instance, if an additional network interface is enabled and configured, the Sender
will add that network interface to the binding list and begin listening on that network interface for
connect requests. If the I.P. address of a network interface changes due to a DHCP change for instance,
the Sender will update the network interface binding. The Sender does not have to be restarted as with
previous versions of RGS to update network interface bindings.
NOTE:
At RGS 5.2.5, the capability was added to specify the port number used by the RGS Sender.
The default Sender port number is 42966, as noted above. The Sender port number can be changed
using the Rgsender.Network.Port property. If this property is used to change the Sender port number
from its default value of 42966, the Sender port number must then be specified in establishing an RGS
connection from the Receiver to the Sender.
Connection topologies
This section describes the connection topologies supported by RGS, such as how a single Local
Computer may connect to multiple Remote Computers.
The Remote Computer frame buffer
After making a connection between a Local Computer and a Remote Computer, the Remote Computer
Sender transmits its complete frame buffer to the Local Computer. The frame buffer is the memory on the
Remote Computer video adapter that holds the bitmapped image that is typically displayed on a
Networking support
15