Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
There are any number of problems that you may be experiencing, but here are the 2 most likely -
1) If the redhat box is behind a firewall or router, and you go to whatismyipaddress.com, you are not going to get the redhat box's "true" IP address, you are getting the IP of the router or firewall.
2) Telnet is junk. Telnet sends unencrypted passwords accross the net, meaning anyone running a packet sniffer will get your username and password in 1 attempt. Red Hat 9 is ancient by linux standards, but even from when it came out, I believe ssh (similiar to telnet, but it encrypts the data) was the default way to access through the net.
It worked with the irix box probably because that box was running a real world IP, so it can be reached from anywhere. If your redhat box is on your lan, you need to know its LOCAL Ip (192.168.x.x, 172.Y.x.x (Y<=16), 169.254.x.x, or 10.x.x.x), and you can telnet to it that way. Use SSH though, it is infinitely more safe.
You can find the IP address on the redhat box much more effectively by doing ifconfig eth0 as full root (su -), and you will be able to connect to that.
Also, seriously consider upgrading that redhat box if you have control of it, that is so old it has missed 3 major versions. It is like finding somebody still using Windows 95 nowadays.
Originally posted by JimBass There are any number of problems that you may be experiencing, but here are the 2 most likely -
1) If the redhat box is behind a firewall or router, and you go to whatismyipaddress.com, you are not going to get the redhat box's "true" IP address, you are getting the IP of the router or firewall.
2) Telnet is junk. Telnet sends unencrypted passwords accross the net, meaning anyone running a packet sniffer will get your username and password in 1 attempt. Red Hat 9 is ancient by linux standards, but even from when it came out, I believe ssh (similiar to telnet, but it encrypts the data) was the default way to access through the net.
It worked with the irix box probably because that box was running a real world IP, so it can be reached from anywhere. If your redhat box is on your lan, you need to know its LOCAL Ip (192.168.x.x, 172.Y.x.x (Y<=16), 169.254.x.x, or 10.x.x.x), and you can telnet to it that way. Use SSH though, it is infinitely more safe.
You can find the IP address on the redhat box much more effectively by doing ifconfig eth0 as full root (su -), and you will be able to connect to that.
Also, seriously consider upgrading that redhat box if you have control of it, that is so old it has missed 3 major versions. It is like finding somebody still using Windows 95 nowadays.
Connnect to the IP of the redhat box from your windows box on the same subnet, but NOT telnet, use SSH. Chances are fairly good that the telnet server on the redhat box isn't on, because it is a security risk. Putty is a free app for window$ that can use ssh.
That should fire up the ssh deamon. If you still can't get in, then you should post the full IP info about the boxes involved, so we can look at problems in that area. If you are on the same LAN as the server, a firewall shouldn't be a problem, but it may be.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.