White Papers

19 Accessing Remote Desktop using VNC on Dell PowerEdge Servers and MX7000 Modular Infrastructure
4. Load the modified stunnel configuration. Right-click the stunnel taskbar icon, and then click Reload
Configuration. The updated configuration will take effect.
5. Connections to the local stunnel port will now be encrypted and forwarded to the iDRAC.
4.3.2 Using RealVNC Client with a local TLS/SSL tunnel
To use RealVNC with a local TLS/SSL tunnel:
1. Start the RealVNC Viewer Client application.
2. Connect the client to the local tunnel port by entering the local address as the server address. For
example, '127.0.0.1:5900'. Because the VNC client is unaware of the encryption, leave the encryption
level (within preferences) set to a value that does not require encryption such as 'let VNC Server
choose'.
Use ReaVNC Client with a local TLS/SSL tunnel
3. Press Enter or select the list item to connect.
4. Because the client is unaware of the encryption, it may show an inaccurate warning indicating that the
connection is unencrypted. Click continue to complete the connection.
5. When prompted, type the VNC password.
6. The VNC session to Server Host OS will be started over an encrypted channel.
4.4 Connecting using RealVNC over SSH
SSH tunneling provides protection against information disclosure on the 14G PowerEdge servers. The SSH
connection is established by using iDRAC credentials, and need not require a separate VNC password.
Similar to many VNC clients, RealVNC does not have built-in SSH support. However, a secure connection
can be achieved by using RealVNC with an external SSH application's tunneling capabilities. One such