Tripp Lite B0930042E4UV Owners Manual for B093- B097- and B098-Series Console - Page 125

SSH Tunneling Using Other SSH Clients e.g. PuTTY

Page 125 highlights

6. SSH Tunnels and SDT Connector 6.10.2 Set Up SDT Serial Ports on Console Server To set up RDP (and VNC) forwarding on the console server serial port that is connected to the Windows computer's COM port: • Select the Serial & Network: Serial Port menu option and click Edit (for the particular Serial Port that is connected to the Windows computer COM port). • On the SDT Settings menu, select SDT Mode (which will enable port forwarding and SSH tunneling) and enter a Username and User Password. Notes: • Enabling SDT will override all other configuration protocols on that port. • If you leave the Username and Password fields blank, they default to portXX and portXX, where XX is the serial port number. For example, the default username and password for Secure RDP over Port 2 is port02. • Ensure the console server Common Settings (Baud Rate, Flow Control) are the same as were set up on the Windows computer COM port and click Apply. • RDP and VNC forwarding over serial ports is enabled by port. You can add users with access to these ports (or reconfigure User profiles) by selecting Serial & Network: User & Groups menu tag. Refer to 4.1 Configure Serial Ports for more information. 6.10.3 Set Up SDT Connector to SSH Port Forward over Console Server Serial Port In the SDT Connector software running on your remote computer, specify the gateway IP address of your console server and a username/password for a user you have set up on the console server that has access to the desired port. Next, you need to add a new SDT Host. In the host address, put portxx where xx = the port you are connecting to. For example, for port 3, you would have a Host Address of: port03, then select the RDP Service check box. 6.11 SSH Tunneling Using Other SSH Clients (e.g. PuTTY) It is recommend you use the SDT Connector client software supplied with the console server. However, there is also a wide selection of commercial and free SSH client programs that can provide the secure SSH connections to the console servers and secure tunnels to connected devices: • PuTTY is a complete (though not the most user-friendly) freeware implementation of SSH for Win32 and UNIX platforms. • SSHTerm is a useful open source SSH communications package. • SSH Tectia is the leading end-to-end commercial communications security solution for enterprise. • Reflection for Secure IT (formerly F-Secure SSH) is another good commercial SSH-based security solution. 125

  • 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
  • 248
  • 249
  • 250
  • 251
  • 252
  • 253
  • 254
  • 255
  • 256
  • 257
  • 258
  • 259
  • 260
  • 261
  • 262
  • 263
  • 264
  • 265
  • 266
  • 267
  • 268
  • 269
  • 270
  • 271
  • 272
  • 273
  • 274
  • 275
  • 276
  • 277
  • 278
  • 279
  • 280
  • 281
  • 282
  • 283
  • 284
  • 285
  • 286
  • 287
  • 288

125
6. SSH Tunnels and SDT Connector
6.10.2 Set Up SDT Serial Ports on Console Server
To set up RDP (and VNC) forwarding on the console server serial port that is connected to the Windows computer’s COM port:
• Select the
Serial & Network: Serial Port
menu option and click
Edit
(for the particular Serial Port that is connected to the
Windows computer COM port).
• On the SDT Settings menu, select
SDT Mode
(which will enable port forwarding and SSH tunneling) and enter a
Username
and
User Password
.
Notes:
• Enabling SDT will override all other configuration protocols on that port.
• If you leave the Username and Password fields blank, they default to portXX and portXX, where XX is the serial port number. For
example, the default username and password for Secure RDP over Port 2 is port02.
• Ensure the console server
Common Settings
(Baud Rate, Flow Control) are the same as were set up on the Windows
computer COM port and click
Apply
.
• RDP and VNC forwarding over serial ports is enabled by port. You can add users with access to these ports (or reconfigure
User profiles) by selecting
Serial & Network: User & Groups
menu tag. Refer to
4.1 Configure Serial Ports
for more
information.
6.10.3 Set Up SDT Connector to SSH Port Forward over Console Server Serial Port
In the SDT Connector software running on your remote computer, specify the gateway IP address of your console server and a
username/password for a user you have set up on the console server that has access to the desired port.
Next, you need to add a new SDT Host. In the host address, put portxx where xx = the port you are connecting to. For
example, for port 3, you would have a Host Address of: port03, then select the RDP Service check box.
6.11 SSH Tunneling Using Other SSH Clients (e.g. PuTTY)
It is recommend you use the SDT Connector client software supplied with the console server. However, there is also a wide
selection of commercial and free SSH client programs that can provide the secure SSH connections to the console servers
and secure tunnels to connected devices:
PuTTY
is a complete (though not the most user-friendly) freeware implementation of SSH for Win32 and UNIX platforms.
SSHTerm
is a useful open source SSH communications package.
SSH Tectia
is the leading end-to-end commercial communications security solution for enterprise.
Reflection for Secure IT
(formerly F-Secure SSH) is another good commercial SSH-based security solution.