LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Linux - Networking (https://www.linuxquestions.org/questions/linux-networking-3/)
-   -   Other machine CANNOT SSH into it but the machine CAN ssh into other machines. (https://www.linuxquestions.org/questions/linux-networking-3/other-machine-cannot-ssh-into-it-but-the-machine-can-ssh-into-other-machines-4175462898/)

monag 05-21-2013 12:48 PM

Other machine CANNOT SSH into it but the machine CAN ssh into other machines.
 
Hello,
I installed the fedora liveCD after booting it of a USB drive.
However I had some issues with ssh. I could ssh to any other machine in network from that machine but could not SSH into it from other machines.
I noticed the services option was absent from the admin menu. I installed it via the system-config-services rpm. But yet was unable to SSH into it.
I ensured that the sshd daemon was running via the chkconfig sshd on command.

There is something funny in this installation. I noticed that the ifcfg-eth0 file was mising from the /etc/sysconfig/network-script folder. So I copied over this file from another machine , made appropriate changes to the file w.r.t mac address and IP address. BUt yet am not able to ssh into it.
I just get a message "no route to host".
I can ping into this machine from any other machine but cannot ssh into it.
I am wondering why the ifcfg-eth0 did not get generated duing the installation process.

I have been struggling on this for the past 3 days. Would apprecaite if someone can let me know what I should do to resolve this issue.

Regards

lleb 05-21-2013 02:08 PM

if you are running Fedora 16 or newer, as you should be if you are running Fedora, then you need to do a few things.

1. set SELinux to passive.

2. Verify that iptables is properly configured to allow port 22 access via your LAN, or as this is a laptop you can open port 22 to all IP ranges.

Those two features are PROTECTING your system as designed. This is a good thing.

monag 05-22-2013 12:03 AM

Thanks very much. Your suggestions helped me. I made a change in iptables to accept 22 and it worked. Thanks for your time and valuable suggestion. Have a great day.

RootMason 05-22-2013 01:20 AM

Awesome, good to hear you got it fixed! I was also going to reply that it could be a problem with iptables blocking port 22, but I wouldn't have thought about setting SELinux to passive. Was this also something you applied in the fix?

lleb 05-22-2013 07:26 AM

Quote:

Originally Posted by monag (Post 4956252)
Thanks very much. Your suggestions helped me. I made a change in iptables to accept 22 and it worked. Thanks for your time and valuable suggestion. Have a great day.

very welcome. good to hear it.


All times are GMT -5. The time now is 04:29 AM.