telnet won't start
-
- Posts: 10
- Joined: 2014/07/23 12:47:01
telnet won't start
I am getting the following:
Jul 23 08:22:03 testlinux.nacscom.com xinetd[1352]: bind failed (Address already
in use (errno = 98)). service = telnet
Jul 23 08:22:03 testlinux.nacscom.com xinetd[1352]: Service telnet failed to sta
rt and is deactivated.
When I run the following lsof I see:
lsof -i tcp:23
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 24u IPv6 14991 0t0 TCP *:telnet (LISTEN)
I have no clue what to do to get telnet running. Please help.
Jul 23 08:22:03 testlinux.nacscom.com xinetd[1352]: bind failed (Address already
in use (errno = 98)). service = telnet
Jul 23 08:22:03 testlinux.nacscom.com xinetd[1352]: Service telnet failed to sta
rt and is deactivated.
When I run the following lsof I see:
lsof -i tcp:23
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
systemd 1 root 24u IPv6 14991 0t0 TCP *:telnet (LISTEN)
I have no clue what to do to get telnet running. Please help.
Last edited by luvdemheels on 2014/07/24 18:51:41, edited 1 time in total.
Re: telnet won't start
Silly question but why on earth are you trying to get telnet running? Hello! The '80s called and want their daemon back...
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke
Re: telnet won't start
Systemd also replaces xinetd, I guess. Forget everything you thought you knew. Learn systemd.
-
- Posts: 10
- Joined: 2014/07/23 12:47:01
Re: telnet won't start
Really embarrassing but where i work i am stuck in the stone age and am tasked with getting this to work. Would appreciate any help!!
-
- Posts: 10642
- Joined: 2005/08/05 15:19:54
- Location: Northern Illinois, USA
Re: telnet won't start
yum install telnet-server
systemctl enable telnet.socket
systemctl start telnet.socket
firewall-cmd --add-service=telnet --permanent
systemctl enable telnet.socket
systemctl start telnet.socket
firewall-cmd --add-service=telnet --permanent
-
- Posts: 10
- Joined: 2014/07/23 12:47:01
Re: telnet won't start
Thanks for the replay. Tried that and still getting the same xinetd message as above and cannot telnet. Any other ideas?
-
- Posts: 10642
- Joined: 2005/08/05 15:19:54
- Location: Northern Illinois, USA
Re: telnet won't start
C7 does not use xinetd to manage telnet.
Did you create an entry in /etc/xinetd.d for telnet?
If so, remove it and restart xinetd.d
I verified the instructions I posted work both with and without xinetd being installed.
Did you create an entry in /etc/xinetd.d for telnet?
If so, remove it and restart xinetd.d
I verified the instructions I posted work both with and without xinetd being installed.
-
- Posts: 10
- Joined: 2014/07/23 12:47:01
Re: telnet won't start
Gerald, Thank you so much!!!!!
Good grief you just saved me. I can't believe I am stuck in the stone age but Thanks!!
Good grief you just saved me. I can't believe I am stuck in the stone age but Thanks!!
Re: telnet won't start
Hi guys,
I have the same problem :/
Would you please help me?
[root@addie ~]# systemctl start telnet.socket
[root@addie ~]# systemctl enable telnet.socket
[root@addie ~]# telnet 192.168.0.110
Trying 192.168.0.110...
telnet: connect to address 192.168.0.110: No route to host
I have the same problem :/
Would you please help me?
[root@addie ~]# systemctl start telnet.socket
[root@addie ~]# systemctl enable telnet.socket
[root@addie ~]# telnet 192.168.0.110
Trying 192.168.0.110...
telnet: connect to address 192.168.0.110: No route to host
Re: telnet won't start
Do not use telnet. It is a very unsafe protocol (it sends the login name and password without encryption across the network). Use ssh for your terminal connections.
That said, the message "No route to host" is likely caused by the firewall blocking the connection.
Also, don't login as root. Login as a non-root user and use the "sudo" command to execute those commands that really require root-privileges.
That said, the message "No route to host" is likely caused by the firewall blocking the connection.
Also, don't login as root. Login as a non-root user and use the "sudo" command to execute those commands that really require root-privileges.