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

Pre-connection checklist, 4-1 Local Computer (Receiver) checklist

Page 74 highlights

4 Pre-connection checklist Establishing an RGS connection from a Receiver to a Sender requires that the Local and Remote Computers be in the correct state. This chapter provides a checklist of items that should be verified before attempting an RGS connection. IMPORTANT: This chapter can also be used as a troubleshooting aid. If a connection attempt fails, the checklists below can be used to help diagnose the problem. NOTE: The port used by the RGS Receiver is assigned by the Local Computer OS and can vary. The RGS Sender listens on TCP/IP port 42966. 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. 4-1 Local Computer (Receiver) checklist Verify the following items on the Receiver computer before attempting to establish a connection. 1. Verify the hostname or IP address of the Remote Computer-Verify that you have the correct hostname or IP address of the Remote Computer. If the Remote Computer hostname fails to resolve to the correct IP address, address this problem before continuing. 2. Verify that, from the Local Computer, you can ping the Remote Computer-If you're unable to ping the Remote Computer, you won't be able to establish an RGS connection. Ping the Remote Computer using the same computer designator you'll be using to establish an RGS connection, either the hostname or the IP address of the Remote Computer. Open a Command window and execute either: ping hostname or ping If no ping reply is received, the Sender computer is unreachable or is not running-resolve this problem before continuing. If a ping reply is received, the Sender computer is reachable by RGS. NOTE: Ensure that firewall settings are not preventing the ping command from working. 4-2 Remote Computer (Sender) checklist Modification and verification of the Sender state can be performed either by connecting a keyboard, mouse, and monitor directly to the Remote Computer, or by using Remote Desktop Protocol to log in remotely to the Remote Computer. In either case, verify each of the following items: • OPTIONAL: Ensure RGS Sender licensing is set up-Beginning at RGS 5.2.0, HP implemented licensing for the RGS Sender. For an overview of RGS licensing, see Section 2-3, "RGS licensing." For detailed information on RGS licensing, see the HP Remote Graphics Software Licensing Guide, available at www.hp.com/support/rgs_manuals. NOTE: The Sender licensing check is optional because you can establish a connection from the Receiver to the Sender without a Sender license. However, as shown in Figure 2-3, an error dialog will be displayed in the Remote Display Window if the Sender license file is missing or invalid. If you don't set up RGS licensing now, you can do it after you've verified you can establish an RGS connection. • Ensure you have a login account on the Remote Computer-When establishing an RGS connection, the Remote Computer will prompt you for a user name and password. Ensure that you have a login account on the Remote Computer. • Verify the Remote Computer login account does not have a blank password-The Remote Computer will not allow a connection for any account with a blank or undefined password. Any accounts on the Remote Computer used for connection by the Local Computer must have password protection. • OPTIONAL: Disable Guest login access-By default, Windows allows any user who can access a computer over the network to login with Guest access. Because this is a potential security issue, HP recommends that Pre-connection checklist 74

  • 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

Pre-connection checklist 74
4
Pre-connection checklist
Establishing an RGS connection from a Receiver to a Sender requires that the Local and Remote Computers be in
the correct state. This chapter provides a checklist of items that should be verified before attempting an RGS
connection.
IMPORTANT:
This chapter can also be used as a troubleshooting aid. If a connection attempt fails, the
checklists below can be used to help diagnose the problem.
NOTE:
The port used by the RGS Receiver is assigned by the Local Computer OS and can vary. The RGS
Sender listens on TCP/IP port 42966. 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.
4-1 Local Computer (Receiver) checklist
Verify the following items on the Receiver computer before attempting to establish a connection.
1.
Verify the hostname or IP address of the Remote Computer
—Verify that you have the correct hostname or IP
address of the Remote Computer. If the Remote Computer hostname fails to resolve to the correct IP address,
address this problem before continuing.
2.
Verify that, from the Local Computer, you can ping the Remote Computer
—If you’re unable to ping the
Remote Computer, you won’t be able to establish an RGS connection. Ping the Remote Computer using the
same computer designator you’ll be using to establish an RGS connection, either the hostname or the IP
address of the Remote Computer. Open a Command window and execute either:
ping
hostname
or
ping <
IP address>
If no ping reply is received, the Sender computer is unreachable or is not running—resolve this problem
before continuing. If a ping reply is received, the Sender computer is reachable by RGS.
NOTE:
Ensure that firewall settings are not preventing the ping command from working.
4-2 Remote Computer (Sender) checklist
Modification and verification of the Sender state can be performed either by connecting a keyboard, mouse, and
monitor directly to the Remote Computer, or by using Remote Desktop Protocol to log in remotely to the Remote
Computer. In either case, verify each of the following items:
OPTIONAL: Ensure RGS Sender licensing is set up
—Beginning at RGS 5.2.0, HP implemented licensing for the
RGS Sender. For an overview of RGS licensing, see Section 2-3, “
RGS licensing
.” For detailed information on
RGS licensing, see the
HP Remote Graphics Software Licensing Guide
, available at
www.hp.com/support/rgs_manuals
.
NOTE:
The Sender licensing check is optional because you can establish a connection from the Receiver to the
Sender without a Sender license. However, as shown in Figure 2-3, an error dialog will be displayed in the
Remote Display Window if the Sender license file is missing or invalid. If you don’t set up RGS licensing now,
you can do it after you’ve verified you can establish an RGS connection.
Ensure you have a login account on the Remote Computer—
When establishing an RGS connection, the
Remote Computer will prompt you for a user name and password. Ensure that you have a login account on
the Remote Computer.
Verify the Remote Computer login account does not have a blank password—The Remote Computer will not
allow a connection for any account with a blank or undefined password. Any accounts on the Remote
Computer used for connection by the Local Computer must have password protection.
OPTIONAL: Disable Guest login access—
By default, Windows allows any user who can access a computer
over the network to login with Guest access. Because this is a potential security issue, HP recommends that