testing services/open ports with telnet?

Question

I often see that folks test ports this way:

//shell
telnet ip-address 80
telnet ip-address 25

AFAIK telnet was the old way of getting onto some remote box - right? or so I thought...

Why exactly can you connect via telnet to smtp port for example?

Answer 1

It's for convenience, but it's also a lower-than-user-level diagnostic. You can isolate the problem you're having with a service that way, for example: Joe has a database server and client. They are not communicating. Is the problem on the network? The server? The client?

Joe goes to the client machine and opens a shell. He uses telnet, just as you described:

telnet server.ip.com 3333

and types a command as if he were the client program

WHO;

The server replies with

'11','JOE.CORP.COM'

(It's a very dumb server)

So then Joe knows that the network link to the server works, and that his client is likely not configured correctly.

Answer 2

Telnet is a very simple protocol, where everything that you type in your client (with few exceptions) go to the wire, and everything that comes from the wire is shown in your terminal. The exception is the 0xFF byte, that setups some special communication states. As long as your communication doesn't contain this byte, you can use telnet as sort of a raw communication client over any TCP port.

IOW: It is purely for convenience.

Answer 3

Why exactly can you connect via telnet to smtp port for example?

Because both smtp and telnet protocols are implemented as plain-text. So with a telnet client, you can basically go connect to any port with a specific protocol that implements plain-text and you know how to communicate using the protocol.

Answer 4

Telnet was designed as a remote terminal application utilizing a socket, plain text and a few control characters. Its use in this way has been mostly replaced by ssh. Any telnet client can be used to interface with any protocol that is implemented in plain text and that's how it's most commonly used today.

Although telnet wasn't designed for this purpose it works perfectly using it this way. Netcat actually was designed for this exact use (opening a socket and spitting raw data over it for any purpose). I generally prefer netcat, but telnet is pretty much universally available.

Answer 5

Why not use netcat nc instead of telnet?

We use netcat in our testtool dda-serverspec - precise command

nc [host] [port] -z -w [timeout]

(see https://github.com/DomainDrivenArchitecture/dda-serverspec-crate/blob/61f44990b07779328ffca0ce7081a7eb1ef9d46b/main/src/dda/pallet/dda_serverspec_crate/infra/fact/netcat.clj#L59)