telnet connection problem

I have telnet server running on linux
the ip address of the linux box is 192.168.0.2
chkconfig confirms the server is running
When I try to connect by telnet to 192.168.0.2 from 192.168.0.4 on the same
lan i get the message:

C:\>telnet 192.168.0.2
Connecting To 192.168.0.2...Could not open connection to the host, on port
23: Connect failed

What would be blocking the connection?
--

Thank you
James T. Studebaker

On Sun, 07 Dec 2003 04:38:05 GMT, James T. Studebaker wrote:
> I have telnet server running on linux
> the ip address of the linux box is 192.168.0.2
> chkconfig confirms the server is running
> When I try to connect by telnet to 192.168.0.2 from 192.168.0.4 on the same
> lan i get the message:
>
> C:\>telnet 192.168.0.2
> Connecting To 192.168.0.2...Could not open connection to the host, on port
> 23: Connect failed
>
> What would be blocking the connection?


Please read http://www.catb.org/~esr/faqs/smart-questions.html

Always post Vendor distribution and release level so we can give better answers.
Different distros have different commands, files, and links to files.
Even happens between release levels of the same distribution.

man xinetd
man hosts.allow
man tcpd
man 5 hosts_access
Check the firewall

and if all else fails, there is a very
large Frequently Asked Question (FAQ) search engine found at
http://groups.google.com/advanced_group_search
Connect failed telnet in the first box
*linux* in the Newsgroup, pick English

If you would like to see some comments on telnet
http://groups.google.com/advanced_group_search
Xns93FD6FED9472jbuserspc9org@130.179.16.24 in the message id box

and view complete thread

"James T. Studebaker" <(E-Mail Removed)> wrote in message
news:N8yAb.447620$Tr4.1250847@attbi_s03

> I have telnet server running on linux
> the ip address of the linux box is 192.168.0.2
> chkconfig confirms the server is running
> When I try to connect by telnet to 192.168.0.2 from 192.168.0.4 on
> the same lan i get the message:
>
> C:\>telnet 192.168.0.2
> Connecting To 192.168.0.2...Could not open connection to the host, on
> port 23: Connect failed
>
> What would be blocking the connection?

--
use hotmail for any email replies


-----= Posted via Newsfeeds.Com, Uncensored Usenet News =-----
http://www.newsfeeds.com - The #1 Newsgroup Service in the World!
-----== Over 100,000 Newsgroups - 19 Different Servers! =-----

"James T. Studebaker" <(E-Mail Removed)> wrote:

>I have telnet server running on linux
>the ip address of the linux box is 192.168.0.2
>chkconfig confirms the server is running
>When I try to connect by telnet to 192.168.0.2 from 192.168.0.4 on the same
>lan i get the message:
>
>C:\>telnet 192.168.0.2
>Connecting To 192.168.0.2...Could not open connection to the host, on port
>23: Connect failed
>
>What would be blocking the connection?

You may have a firewall running on the Linux machine ... as root try
`iptables -L`
to see if there are any rules blocking telnet!
--
------------------------------------------------
http://www3.sympatico.ca/dmitton
SPAM Reduction: Remove "x." from my domain.
------------------------------------------------

James T. Studebaker <(E-Mail Removed)> randomly warbled in
comp.os.linux.networking:

> I have telnet server running on linux
> the ip address of the linux box is 192.168.0.2
> chkconfig confirms the server is running

Useless.
Run 'netstat -ltp' to PROVE that telnetd (or inetd) is listening on port
23.

> When I try to connect by telnet to 192.168.0.2 from 192.168.0.4 on the
> same lan i get the message:
>
> C:\>telnet 192.168.0.2
> Connecting To 192.168.0.2...Could not open connection to the host, on
> port 23: Connect failed
>
> What would be blocking the connection?

Many, many things...

- Linux iptables firewall - run 'iptables -L' to see whether there are
any rules active
- man hosts.allow, hosts.deny - these apply to ALL (x)inetd services!

And, of course, the old favourite: is there actually a connection
between these systems ?

Prove this by studying the output of route -n and ifconfig, optionally
ipconfig on Windoze as well.

If you don't know how to troubleshoot the network itself, do a google
for any TCP/IP tutorial, and check back later...

--
Jeroen Geilman

All your bits are belong to us.

Also is telnetd listening on the IP 192.168.0.2 and not just localhost
127.0.0.1..??

Nmap is a life saver here; nmap -sT 192.168.0.2


--
..¤¤°MaX°¤¤.
Cold and silent soiled face I will wash it all away...

"Jeroen Geilman" <(E-Mail Removed)> wrote in message
news:3fd38d11$0$211$(E-Mail Removed)...
> James T. Studebaker <(E-Mail Removed)> randomly warbled in
> comp.os.linux.networking:
>
> > I have telnet server running on linux
> > the ip address of the linux box is 192.168.0.2
> > chkconfig confirms the server is running
>
> Useless.
> Run 'netstat -ltp' to PROVE that telnetd (or inetd) is listening on port
> 23.
>
> > When I try to connect by telnet to 192.168.0.2 from 192.168.0.4 on the
> > same lan i get the message:
> >
> > C:\>telnet 192.168.0.2
> > Connecting To 192.168.0.2...Could not open connection to the host, on
> > port 23: Connect failed
> >
> > What would be blocking the connection?
>
> Many, many things...
>
> - Linux iptables firewall - run 'iptables -L' to see whether there are
> any rules active
> - man hosts.allow, hosts.deny - these apply to ALL (x)inetd services!
>
> And, of course, the old favourite: is there actually a connection
> between these systems ?
>
> Prove this by studying the output of route -n and ifconfig, optionally
> ipconfig on Windoze as well.
>
> If you don't know how to troubleshoot the network itself, do a google
> for any TCP/IP tutorial, and check back later...
>
> --
> Jeroen Geilman
>
> All your bits are belong to us.
>

If your various servers only show up on 127.0.0.1 and not on 192.x.x.x what
remedy is necessary?

I've added an alias to /etc/hosts
I've added all my home networked IP's to hosts.allow

No matter what I do, the 192.x.x.x does not have my ssh/ftp/... services.
This address only has things link microsoft_ns, UPnP and such.


"MaX" <(E-Mail Removed)> wrote in message news:gsuga1-(E-Mail Removed)...
> Also is telnetd listening on the IP 192.168.0.2 and not just localhost
> 127.0.0.1..??
>
> Nmap is a life saver here; nmap -sT 192.168.0.2
>
>
> --
> .¤¤°MaX°¤¤.
> Cold and silent soiled face I will wash it all away...
>
> "Jeroen Geilman" <(E-Mail Removed)> wrote in message
> news:3fd38d11$0$211$(E-Mail Removed)...
> > James T. Studebaker <(E-Mail Removed)> randomly warbled in
> > comp.os.linux.networking:
> >
> > > I have telnet server running on linux
> > > the ip address of the linux box is 192.168.0.2
> > > chkconfig confirms the server is running
> >
> > Useless.
> > Run 'netstat -ltp' to PROVE that telnetd (or inetd) is listening on port
> > 23.
> >
> > > When I try to connect by telnet to 192.168.0.2 from 192.168.0.4 on the
> > > same lan i get the message:
> > >
> > > C:\>telnet 192.168.0.2
> > > Connecting To 192.168.0.2...Could not open connection to the host, on
> > > port 23: Connect failed
> > >
> > > What would be blocking the connection?
> >
> > Many, many things...
> >
> > - Linux iptables firewall - run 'iptables -L' to see whether there are
> > any rules active
> > - man hosts.allow, hosts.deny - these apply to ALL (x)inetd services!
> >
> > And, of course, the old favourite: is there actually a connection
> > between these systems ?
> >
> > Prove this by studying the output of route -n and ifconfig, optionally
> > ipconfig on Windoze as well.
> >
> > If you don't know how to troubleshoot the network itself, do a google
> > for any TCP/IP tutorial, and check back later...
> >
> > --
> > Jeroen Geilman
> >
> > All your bits are belong to us.
> >
>
>