Re: Networking - still could not telnet in
Well thanks Sean , for asking that question.
I tried telnet 127.0.0.1 (because the output of ifconfig -a
assured me that the loopback was up and running)
and
the answer (to telnet 127.0.0.1)
was in the negative : "Could not telnet host".
And then I did a whereis telnet
whereis: /usr/bin/telnet
and a whereis in.telnetd
whereis: something/inetd , if I remember rightly.
I am actually confused on how to read the situation.
Thanks and Regards,
Shyam.
As on Sat, May 04, 2002 at 10:57:53AM -0700 , Sean 'Shaleh' Perry said :
>
> On 04-May-2002 shyamk wrote:
> > I am trying to establish networking on a LAN consisting of
> > 2 machines on Linux 2 on Windoze.
> > My second Linux box never used to respond to the network.
> > So I did :
> > ifconfig -a
> > ifconfig eth0 192.147.165.4 netmask 255.255.255.0
> > ifconfig -a
> >
> > Now from the one Windows box (192.147. 165.1) ,
> > connected to the same HUB, I tried to telnet 192.147.165.4
> > I got the message "Could not connect".
> > Then I gave ping 192.147.165.4
> > which vae out 4 packets sent 4 received 0%packet loss.
> >
>
> this may be a stupid question, but is the linux box actually running the telnet
> daemon? If you are on the linux machine and type 'telnet localhost' do you get
> a login prompt?
--
----------------------------(*)-X-(*)----------------------------
Knowledge is Power
-----------------------------------------------------------------
__________________
| __ |
| |_|_ |
| __| | |
|__________________|
--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: