Remote Access protocols

Remote Access protocols

1. Telnet: Allows a command line terminal interface with a remote system.

   • Uses TCP port 23. Its features are very basic and it isn't very secure, so it's not nearly as popular as it once was.

2. SSH: Secure Shell allows stronger authentication and encrypted transmission than Telnet.

   • It also allows other features, such as file transfers. SSH uses TCP port 22.

3. RDP: Remote Desktop Protocol is Microsoft's proprietary remote access protocol.

   • Not only does it provide security features, but it allows you to log into a complete Windows desktop over the network.
   • RDP uses TCP port 3389.

4. VNC: Virtual Network Computing is an open set of standards based on the Remote Frame Buffer (RFB) protocol. Like RDP, VNC allows you to access a complete graphical desktop, but unlike RDP it directly shares input and output rather than creating a remote user session.

   • By default, VNC uses TCP port 5900+N, where N is the display number.

5. HTTP: Web-based interfaces aren't that suitable for remote access to a graphic or command-line shell interface, though it's possible with the assistance of a web-based application.

   • More commonly, HTTP is used for web management interfaces for network devices and services. Just like any other website, HTTP itself provides no real security, so HTTPS is much better for use on untrusted networks.

6. SNMP: Simple Network Management Protocol is used to remotely manage and monitor network devices like routers and switches.

   • SNMP doesn't provide a direct login to the device, but rather standardizes communication between managed devices and a central management application.
   • SNMP uses UDP ports 161 and 162.