LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Enterprise (https://www.linuxquestions.org/questions/linux-enterprise-47/)
-   -   setting up telnet on redhat enterprise linux 5 (https://www.linuxquestions.org/questions/linux-enterprise-47/setting-up-telnet-on-redhat-enterprise-linux-5-a-605102/)

rockjr 12-06-2007 11:16 PM

setting up telnet on redhat enterprise linux 5
 
i want to practice from work and i have a server at home that i just set up so can anyone tell me how to set up telnet on my red hat????

acid_kewpie 12-07-2007 02:17 AM

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.

rockjr 12-07-2007 06:13 AM

Quote:

Originally Posted by acid_kewpie (Post 2982936)
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

Aaronk 12-07-2007 07:24 AM

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.

rockjr 12-07-2007 05:32 PM

Quote:

Originally Posted by Aaronk (Post 2983155)
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

rockjr 12-07-2007 06:13 PM

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

farslayer 12-07-2007 08:48 PM

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..

rockjr 12-08-2007 05:25 PM

Well i have a dlink gaming router ... forgot model number

right now i am trying from inside the network first

have ip hard coded in box which is 192.168.0.155

ssh is activated but firewall is not

rhl box can get on the internet itself

i am using putty (is this the best ssh/telnet software out there)

it keeps freezing up if i use ssh or when i try to use telnet it trys to connect and then blows away

rockjr 12-08-2007 06:51 PM

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????

Aaronk 12-09-2007 06:58 AM

From a windows environment I use Putty (http://www.chiark.greenend.org.uk/~s.../download.html). From my Linux environments I use open source SSH client that comes with the OS from the command line
.

dmarti 12-10-2007 01:38 PM

Rick Moen's ssh client list
 
Check Rick Moen's list at: http://linuxmafia.com/ssh/ to find an ssh client you can use from your other machines, whatever OS they run.


All times are GMT -5. The time now is 09:43 PM.