How to Install Telnet Client on RHEL 6/7, CentOS 6/7, Oracle Linux 6/7

Install Telnet

Telnet is one of the most frequently used software by the system administrator, program developers and anyone who needs to use the application or data that is located in a particular host computer.

It is a network protocol used on the internet or a local area network to provide text-oriented interactive bidirectional communication facility using a virtual terminal connection.

Telnet client is not installed automatically on all linux distribution with a minimum installation.

Telnet has two different packages which are telnet client and telnet server package. If you do a “yum install telnet” it will only contain client telnet program.

READ  How to Install Iptables on CentOS 5.8

This article explain how to install telnet client program and tested on various linux platform.

How to Install Telnet Client on RHEL 6/7, CentOS 6/7, Oracle Linux 6/7

1. Issue the following commands to confirm that telnet is installed or not :

# telnet localhost 80

If telnet client does not installed, it should return something like :

# telnet localhost 80
-bash: telnet: command not found

2. Verify telnet client using which command :

# which telnet
/usr/bin/which: no telnet in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/root/bin)

3. Issue the following command to install telnet client :

# yum install telnet -y

4. If telnet client installed, it should return something like :

# telnet localhost 80
Trying ::1...
Connected to localhost.
Escape character is '^]'.

or

# which telnet
/usr/bin/telnet

 

4 Replies to “How to Install Telnet Client on RHEL 6/7, CentOS 6/7, Oracle Linux 6/7”

  1. Kindly help. Below is the error :
    [sam@xxxxxx ~]$ yum install telnet -y
    Loaded plugins: fastestmirror, langpacks
    You need to be root to perform this command.
    [sgunjan@inmum0931 ~]$ sudo yum install telnet -y
    Loaded plugins: fastestmirror, langpacks
    Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
    14: HTTP Error 407 – Proxy Authentication Required
    https://archive.cloudera.com/cm5/redhat/7/x86_64/cm/5/repodata/repomd.xml: [Errno 14] curl#22 – “HTTP returned error”
    Trying other mirror.
    Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=extras&infra=stock error was
    14: HTTP Error 407 – Proxy Authentication Required
    localrepo | 3.6 kB 00:00:00
    http://repo.mysql.com/yum/mysql-connectors-community/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 407 – Proxy Authentication Required
    Trying other mirror.
    http://repo.mysql.com/yum/mysql-tools-community/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 407 – Proxy Authentication Required
    Trying other mirror.
    http://repo.mysql.com/yum/mysql-5.7-community/el/7/x86_64/repodata/repomd.xml: [Errno 14] HTTP Error 407 – Proxy Authentication Required
    Trying other mirror.
    Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=updates&infra=stock error was
    14: HTTP Error 407 – Proxy Authentication Required
    Determining fastest mirrors

    One of the configured repositories failed (Unknown),
    and yum doesn’t have enough cached data to continue. At this point the only
    safe thing yum can do is fail. There are a few ways to work “fix” this:

    1. Contact the upstream for the repository and get them to fix the problem.

    2. Reconfigure the baseurl/etc. for the repository, to point to a working
    upstream. This is most often useful if you are using a newer
    distribution release than is supported by the repository (and the
    packages for the previous distribution release still work).

    3. Disable the repository, so yum won’t use it by default. Yum will then
    just ignore the repository until you permanently enable it again or use
    –enablerepo for temporary usage:

    yum-config-manager –disable

    4. Configure the failing repository to be skipped, if it is unavailable.
    Note that yum will try to contact the repo. when it runs most commands,
    so will have to try and fail each time (and thus. yum will be be much
    slower). If it is a very temporary problem though, this is often a nice
    compromise:

    yum-config-manager –save –setopt=.skip_if_unavailable=true

    Cannot find a valid baseurl for repo: base/7/x86_64

Leave a Reply

Your email address will not be published. Required fields are marked *