Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Chris Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Telnet problems

Status
Not open for further replies.

stevenriz

IS-IT--Management
May 21, 2001
1,069
I have read all the postings in regard to telnet and am still a little confused. I can telnet to my RH 7.2 box from the console only. Can't from anywhere else on the network. I assume it is because of the hosts.allow hosts.deny files. I don't know the syntax. Are these the files that are holding me up here?
Steve
 
Hi,

On redhat 7.x, its much more likely to be because of the firewall they provide which seems to turn itself on by default. Its called lokkit and generates ipchains rules that are read by the ipchains service. Unless you know it isn't that, the first thing to do is administer that firewall to allow the telnet service through, i.e. permit inbound TCP port 23 . You do that as root with :

# /usr/sbin/lokkit

or

# /usr/sbin/gnome-lokkit (Alan Cox gnome gui version !)

If you are on a lan and want to run various services on the linux box it is maybe easiest to take the option to treat your lan interface (eth0 ?) as 'trusted' - then most stuff will be allowed through. Otherwise, just allow inbound port 23.

Restart the network :

# /etc/rc.d/init.d/network restart

... and try again. Out of the box, you should be able to login via telnet with any 'regular' linux account - but not root. Thats restricted for security purposes.

You probably read it before, but its really much more secure to use ssh instead of telnet. You need to install all the rpms on the redhat CD beginning with 'openssh' :

# mount /dev/cdrom
# rpm -Uvh /mnt/cdrom/Redhat/RPMS/openssh*.rpm

Again, you'd need to allow it through lokkit (port 22) this time. If you need a client for ssh (or even a better windows telnet client) then try PuTTY -->
Hope this helps
 
Perhaps the xinted is not running !

Try to run xinted and telnet that machine!

Make sure your /etc/xinet.d/*.conf script disable = no

Sivakumar Kandaraj
web system programmer
Melbourne
 
Gday,

I'd assume that xinetd was OK in this particular case if it's possible to do a 'telnet localhost', as seems to be the case.

Otherwise, on redhat / mandrake, its easiest to use chkconfig rather than directly editing the /etc/xinetd.d/telnet file (as root) :

# /sbin/chkconfig telnet on

(does the same thing as an edit to change disable=yes to disable=no)


Regards
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top