Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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.
don't use telnet, use ssh instead, it'll already be fully working in terms of the machine itself, but you'll presumably be needing to do some port forwarding on a home router and such to reach it... http://portforward.com.
don't use telnet, use ssh instead, it'll already be fully working in terms of the machine itself, but you'll presumably be needing to do some port forwarding on a home router and such to reach it... http://portforward.com.
i already did port forwarding using my virture server selection in my router.... i looked into service config on the linux r.h.e box and it said sshd is running but when i try to log in using putty it still doesnt work. Can anyone tell me step by step how to config the r.h.e 5 server box
first test it from within your home network, (google "putty" first thing that pops up is one of the more popular of hundreds of ssh clients available - download it to a windows or other box on the same LAN as your home server) open putty or another SSH client, and simply put in the LOCAL (non-routeable) IP of the home server. I have yet to see an RH / Fedora build that doesn't have an SSH daemon running post (typical) install. For this excesize we'll assume you went with a somewhat normal install. If that doesn't work go back and check your firewall and SELinux settings on the RH box. Firewall settings can easily be accessed by typing "setup" from a root prompt. You're going to need to make sure its either turned off or have TCP port 22 allowed. Do a google search for SELinux, but I would recommend just disabling it until you have SSH functioning, then go back and update it appropriately. After changing SELinux you'll have to reboot. Next, retest - you should definately be able to SSH to your home server from within your LAN at this point. Next you'll have to mess with your main router / firewall. It will be easiest to activate remote administration temporarily for your router. Check and make sure you have TCP 22 forwarded to whatever the local ip is for your RH server. Go to work, test. if it still fails log into your router and double check your work. If it all seems correct but youre' still failing, go to a friends house and check from there. Its entirely possible your corporate IT dept is blocking outgoing SSH requests.
first test it from within your home network, (google "putty" first thing that pops up is one of the more popular of hundreds of ssh clients available - download it to a windows or other box on the same LAN as your home server) open putty or another SSH client, and simply put in the LOCAL (non-routeable) IP of the home server. I have yet to see an RH / Fedora build that doesn't have an SSH daemon running post (typical) install. For this excesize we'll assume you went with a somewhat normal install. If that doesn't work go back and check your firewall and SELinux settings on the RH box. Firewall settings can easily be accessed by typing "setup" from a root prompt. You're going to need to make sure its either turned off or have TCP port 22 allowed. Do a google search for SELinux, but I would recommend just disabling it until you have SSH functioning, then go back and update it appropriately. After changing SELinux you'll have to reboot. Next, retest - you should definately be able to SSH to your home server from within your LAN at this point. Next you'll have to mess with your main router / firewall. It will be easiest to activate remote administration temporarily for your router. Check and make sure you have TCP 22 forwarded to whatever the local ip is for your RH server. Go to work, test. if it still fails log into your router and double check your work. If it all seems correct but youre' still failing, go to a friends house and check from there. Its entirely possible your corporate IT dept is blocking outgoing SSH requests.
ok my router is set to port 23.... do i need to use 22 or does it not matter
ok, in putty i switched it to ssh (whats the dif between that and telnet) and cant log into it outside the router or inside the network either... i did make sure that ssh was cut on... and i switch the router from port 23 to 22 but its still not working
Telnet's default port is 23
Telnet sends EVERYTHING including your username and password in PLAIN TEXT so anyone can read it..
You should only use telnet if the box you are connecting to cannot do SSH and you have absolutely no other possible secure options available. Never is a good time to use telnet..
SSH default port is 22
SSH Encrypts your connection including your username and password.
When using putty select SSH
Your Router should be set to forward Port 22 to your RHEL box..
Provided your sshd is configured to accept connections on port 22 (netstat -alnp | grep ::22) and there is no firewall on your RHEL box (iptables -L) that is blocking port 22, or the firewall is configured to accept connections on port 22.. then you should be able to connect..
ok... got that part figured out.... it was supposed to be imputted as so .... whatevertheacctnameis@84.34.44.4 .....
so i got it now... i am able to log in from internally and externally.... thanks for all the help guys.... i am a rookie on this trying to get my linux+ sometime early next year so wish me luck
ps. whats the best ssh software out there that i can use on my computer and one for my pocketpc device????
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.