Remote Login with Telnet

Now everyone can work anywhere — Part1/3


My work shift starts at 8.30am, and I wake up 7.30am daily; so you can guess that I have one hour to get ready. Yet somehow I am always, still late to work. — Don’t get me wrong, I have a cosy office that make me feel less blue on each Mondays. Here’s a sneak peek of my work office.

An office I can call home

Intuition of remote login

So you get a message from your boss: ‘do not come into the office, but make sure the report is ready by next week’. Suppose that the data you need to compile this report is stored on a server in the office. We can use remote login services like Telnet, SSH, Windows remote desktop or VNC to connect into this server remotely to get what we need. For this to work, the target server must be remote login enabled, meaning that it is running either Telnet, SSH, VNC server and Firewall is not blocking any of these ports.

Avocado is working from home in Penang. He is connecting to the server located in the office using remote login during MCO.
Putty.exe is a popular choice for remote login using TELNET and SSH
Telnet server asking for the login credentials during the authorisation. Telnet service is password protected. Each user is given unique username and password. However, the is no end to end encryption for Telnet connection. Telnet is vulnerable to MITM attacks.

How Telnet works?

Telnet is a basic remote login protocol without all the bell and whistle. Telnet allows the client to establish a remote connection to the Telnet server. This connection happened in plain text, including the authentication message.

Setting up a remote connection from Telnet client →Telnet Server
Behind The Scenes — How Telnet Works

Problems with Telnet

Telnet works well for basic remote login requirements, only when it works. However there are some cases where telnet client is not able to connect to the server. Here’s a troubleshooting checklist for Telnet connection issues: