To telnet from a Windows computer to a Unix computer you need to ensure that
- Windows has telnet client installed (it is not installed in latest Windows)
- Windows firewall is not blocking outgoing Telnet (very unlikely)
- Windows can resolve server's name (e.g. through DNS or local
hosts
file)
- Unix server has Telnet service enabled (increasingly being disable to encourage SSH use)
- No intermdiate firewalls are blocking Telnet (unlikely if both computers are in same subnet)
- You have valid Unix login credentials (user name and password)
Since you didn't post an actual error message but just said you "can't do telnet" - we can only guess at the problem.
To check if the Telnet service is runnning, log on at the Unix server console and use this command:
netstat -a | grep "telnet.*LISTEN"
The output should be this
tcp 0 0 *.telnet *.* LISTEN
Note: If you have problems, update your question with the actual command and error messages by using cut & paste (then edit only if needed to change confidential details)
Update:
Redhat / Fedora
Use these commands
chkconfig telnet on
chkconfig --list | grep telnet
The output from the second command should be
telnet: on
Ubuntu
sudo apt-get install telnetd
sudo /etc/init.d/inetd restart
Once installed, from the GUI, select Administration, Services and enable Telnet
Distros using Xinetd
You need a file named /etc/xinetd.d/telnet with contents something like this
# default: on
# description: The telnet server serves telnet sessions; it uses \
# unencrypted username/password pairs for authentication.
service telnet
{
flags = REUSE
socket_type = stream
wait = no
user = root
server = /usr/sbin/in.telnetd
log_on_failure += USERID
disable = no
}
Warning!
You shouldn't be doing this unless you are familiar with Linux, with Linux commands, with editors such as vi and have good backups and are prepared to reinstall if it all goes horribly wrong. If other people rely on this server, you should employ a systems administrator who is familiar with the particular Linux distribution you are using.
Just a comment.... To telnet works, you will need to have a TCP port on LISTENING state on server's side. You can check it on the server using netstat -a – Diogo – 2011-11-04T13:48:04.673
SERV1 has 2 IP-adresses 172.26.1.40 and 172.26.1.42? UNI1 172.28.150.10 is in another network? And then FUN-SERV1 and DRIVER-SERV1 are again in a third network? Can you show the ifconfig (or ipconfig) for each interface and the routing table on each host? Now from where to where do you want to telnet? – ott-- – 2011-11-04T14:05:35.807
1
This is barely comprehensible, but appears to be an exact duplicate of the question that this questioner asked last week. Xe is still trying to telnet from that Windows machine to the Unix machine.
– JdeBP – 2011-11-04T14:12:37.203i believe telnet is required from DRIVER-SERV1 to 172.26.1.40 The switch is unmanaged and it is in DR lan – steveaston – 2011-11-04T14:44:01.140
Can you please just post one question to one problem you're having? Your question here contains even less information than the one before? It would be much better if you could just have one question with all the details. – slhck – 2011-11-05T10:24:53.907