telnet & ssh & ping

telnet & ssh & ping

Post by Zimmen Gnau » Sat, 21 Dec 2002 12:30:39



    For the first time, I installed redhat 8.0 workstation in my pc.
Unable to get network working. To test basic networking capability, I
tried to ping and ssh itself, both working fine. However, to telnet
itsself:

telnet 192.168.51.20
response:  connection refused.

There is no firewall in my computer. Does anyone have any idea of what
happens? Do I need to run any server program to make telnet working? (I
saw sshd running).

 
 
 

telnet & ssh & ping

Post by Zimmen Gnau » Sat, 21 Dec 2002 12:35:55



>     For the first time, I installed redhat 8.0 workstation in my pc.
> Unable to get network working. To test basic networking capability, I
> tried to ping and ssh itself, both working fine. However, to telnet
> itsself:

> telnet 192.168.51.20
> response:  connection refused.

> There is no firewall in my computer. Does anyone have any idea of what
> happens? Do I need to run any server program to make telnet working? (I
> saw sshd running).

          BTW, I can telnet to my router: telnet 192.168.51.17
successfully.

 
 
 

telnet & ssh & ping

Post by Lenar » Sat, 21 Dec 2002 12:58:27




>>     For the first time, I installed redhat 8.0 workstation in my pc.
>> Unable to get network working. To test basic networking capability, I
>> tried to ping and ssh itself, both working fine. However, to telnet
>> itsself:

>> telnet 192.168.51.20
>> response:  connection refused.

>> There is no firewall in my computer. Does anyone have any idea of what
>> happens? Do I need to run any server program to make telnet working? (I
>> saw sshd running).

>           BTW, I can telnet to my router: telnet 192.168.51.17
> successfully.

OK you have the telnet client installed. What about the telnet-server?

Hint: rpm -q telnet-server

 
 
 

telnet & ssh & ping

Post by Allen McInto » Sat, 21 Dec 2002 13:18:34




>OK you have the telnet client installed. What about the telnet-server?
>Hint: rpm -q telnet-server

And when you get that fixed, you may need to turn it on in xinetd's
configuration.  See the disable= entry in /etc/xinetd.d/telnet