Back in the old days before SSH was “the standard way” to log into a remote computer, there “were” a protocol (and a utility) called “telnet” in order to achieve that.
But the “telnet” utility traditionally also served for testing deliberate TCP/IP ports somewhere in the Internet resp. on your “Intranet”, e.g.
Can I connect to that Oracle DB server on that specific port?
That’s particularly useful, because the applications themselves (whether GUIs or CLI utilities) usually have poor ways of dealing with facts like:
- some firewall prevents you from accessing that Oracle DB server
- there is simply no route to that Oracle DB server
The “telnet” utility does not really have nicer error messages, but “everybody knows”, what it means, if you tell them, you tried to “telnet HOST PORT“, and it failed or timed out. And you know, it’s not the application, but it’s the network or the server.
In recent versions of Microsoft Windows the “telnet” utility got made sort of invisible, but there is an easy way to make it visible and available. See the links below!
But if you already have the PuTTY suite of utilities available on your PC, maybe you prefer the “plink” utility:
% …plink -telnet -P port host
- http://www.chiark.greenend.org.uk/~sgtatham/putty/latest.html – where to find the PuTTY suite of utilities
The Windows “defect” and its fix:
If you wish to turn on and enable the “telnet” utility, here is what to do:
- Click Start.
- Click Control Panel.
- Now, go to Programs or Programs and Features.
- Click Turn Windows features on or off. (only “administrators” can proceed here.)
- In the Windows Features dialog box, tick Telnet Client check box.
- Click OK.