If telnet is enables on the Linux computer, but most distributions do not enable telnet servers by default (some do not even install it.)
(The instructions below are for RedHat and may need to be modified for other distros)
To see if telnet (server) is installed, type
rpm -qa|grep telnet-server
at the command prompt, if you see it returned it will be available... to see if it is running, type
netstat -pl|grep telnet
If nothing is retuned then you need to edit the /etc/xinetd.d/telnet file and change the
disabled = yes
to
disabled = no
then restart xinetd
/etc/init.d/xinetd restart
Another option, which is more secure and supported, is SSH.
You can download a windows SSH client for free (for trial, academic, or non-commercial use) at
Yes - as long as you have the telnet server package installed and configured. You don't say what linux that is but, for redhat, you'd first check if the telnet-server rpm was installed (rpm -q telnet-server). If not, install it of course. Then you'd need to make sure it wasn't disabled under xinetd by doing as root :
# /sbin/chkconfig telnet on
then restart xinetd :
# /etc/rc.d/init.d/xinetd restart
At this stage xinetd should be listening on port 23 for telnet connections. You can confirm this with the command :
# /usr/sbin/lsof -i TCP:23
After that, all that's left is to configure the firewall to allow inbound port 23 :
# /usr/sbin/lokkit (follow screens)
After all that you should have no trouble telnetting to the linux box (assuming you have network connectivity in the first place.) However, you will not be able to login as 'root' - use a normal account and then 'su' to root from within telnet.
Even better, use ssh. You need to install the various rpms beginning with 'openssh' and use something like puTTY on the windows side. In fact, I'd recommend to use puTTY anyway as it can do telnet better that the regular windows telnet client.
On caldera, the telnet server rpm seems to be called 'netkit-telnet' . You'd need to install that rpm to start with. I believe caldera still uses inetd rather than xinetd so you'd need to make sure you /etc/inetd.conf has a line like :
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.