RDP, VNC or SSH: which remote access should you use for your equipment?

RDP: remote control of a Windows PC

RDP is particularly suitable for industrial PCs and Windows workstations. It transmits a graphical session efficiently and generally works well over a remote connection. However, the Windows version, user rights and workstation session policy must be checked.

For programming software installed on an on-site PC, RDP can be a very convenient solution.

VNC: viewing and controlling the existing screen

VNC generally shares the same screen that is displayed locally on the machine. This is useful for some HMIs, embedded systems or workstations where the technician needs to see exactly what an operator sees.

There are many VNC implementations, and security and performance depend heavily on the server used. VNC should be used through a secure remote-access connection rather than exposed directly on the Internet.

SSH: lightweight and efficient administration

SSH is ideal for Linux equipment, gateways, PLCs or embedded systems that provide a command line. It uses little bandwidth and is well suited to diagnostics, logs, configuration and secure file transfers.

Key-based authentication should be preferred when the equipment supports it.

Choosing the simplest protocol

There is no need to use a graphical remote-control solution when an SSH command is sufficient, or to impose SSH when Windows software must be operated. The best protocol is the one that provides only the functions needed for the task.

RescueLAN provides the communication path to the equipment; the technician can then use the protocol best suited to the task, including SSH, RDP, VNC or specific TCP access, for the duration of the session.