cancel
Showing results for 
Search instead for 
Did you mean: 

Not able to Telnet

 
Atul Gautam
Valued Contributor

Not able to Telnet

Hi Xperts,

I'm not able to telnet my server.
I've got the following information for you people --


/etc/xinetd.d/telnet
---------------------

service telnet
{
disable = no
flags = REUSE
socket_type = stream
wait = no
user = sysadm
server = /usr/sbin/in.telnetd
log_on_failure += USERID
}

----------------------------

Logs say --

MLXILSFTP xinetd[14757]: libwrap refused connection to telnet (libwrap=in.telnetd) from
--------------------------------------------
[root@MLXILSFTP log]# service xinetd status
xinetd (pid 14354) is running...
[root@MLXILSFTP log]#
--------------------------------------------


What may be the possible cause of this....

Thanx in advance...


--
Atul
8 REPLIES 8
g33k
Valued Contributor

Re: Not able to Telnet

libwrap(TCP wraper) is used to restict access to server....
check and edit /etc/hosts.allow or /etc/hosts.deny
Vipulinux
Respected Contributor

Re: Not able to Telnet

Hi Atul

Check your /etc/hosts.allow and /etc/hosts.deny

Edit these to allow telnet.

Cheers
Vipul
Jaime Bolanos Rojas.
Honored Contributor

Re: Not able to Telnet

Atul,

Both responses given to you above are right, it's a secure shell feature, according to this HP doc, KBRC00011104

Regards,

Jaime.
Work hard when the need comes out.
Atul Gautam
Valued Contributor

Re: Not able to Telnet

But I checked one thing, if at all I replace the line in "telnet" file--

user = sysadm

with

user = root

then only I'm able to get the login prompt, else it never prompts me or it gives me an error "Connection to host lost".

So, why do I need to specify user=root in it.


Thanks,

Atul
g33k
Valued Contributor

Re: Not able to Telnet

well man sais

user = root

it defines user ID which is running process with....

so it means, if your telnet server have some buffer overfolw vulnarability, than a pontetial hacker will get root rights... god with you...

so check your /etc/passwd if there is sysadm user, if not it, was maybe the problem...

try to create new user, or maybe on some distribution there is user called telnet... so try to run telnet server as this user...

user = telnet

anyway I would never use telnet... only device where I use telnet are old cisco which do not have ssh suport
Atul Gautam
Valued Contributor

Re: Not able to Telnet

Found the solution

Thanks to all....


ATUL
Highlighted
Mike Brown_3
Frequent Advisor

Re: Not able to Telnet

Yes, but what was it?

Thanks.
There's no substitute for experience
prasadb
Super Advisor

Re: Not able to Telnet

hi atul,

you should share the solution,and kindly assign the points for those who had taken the efforts in order to resolve your problem.