trouble to connect via ssh

[tuxalka]

Hi, I have notebook and desktop in small home network. Fedora 16 rans on both of them, I followed the documentation guidelines of F16 to establish ssh connection between them. And when I try to connect from notebook to PC it reports: no route to host. I can ping both of them. I saw ssh is enabled in firewall -just in graphical user enviroment. Both notebook and PC have ip address from my router dhcp. Any advice? I changed permission on .ssh directory 775 and th authorized_keys file on 644. Please help.

[glennzo]

tuxalka, I've closed your other thread as a duplicate of this one.

http://forums.fedoraforum.org/showthread.php?t=276461

Please read the Posting Rules before posting again.

[coffee412]

A great tool for investigating connection problems is probably nmap. This will show what ports are open on a computer on your network.

yum -y install nmap

Then do a "nmap <ipaddress of computer your trying to connect too>"

Also, See if you can ping the other computer.

Thats all a start to fixing your problem. If you cannot ping or discover the open ports with nmap then it very well could be a firewall problem.

[tuxalka]

Hi,
I tried the nmap and ping.
The nmap reported:
Starting Nmap 5.51 ( http://nmap.org ) at 2012-02-16 18:19 CET
Note: Host seems down. If it is really up, but blocking our ping probes, try -Pn
Nmap done: 1 IP address (0 hosts up) scanned in 0.39 seconds

The ping is succesful. I do not understand how is possible that nmap reports blocking ping probes and I can ping the adress without problem. I have the ssh service checked (ticked off) on firewall.

nmap -Pn reported this:
Starting Nmap 5.51 ( http://nmap.org ) at 2012-02-16 18:25 CET
Nmap scan report for 192.168.1.101
Host is up (0.95s latency).
All 1000 scanned ports on 192.168.1.101 are filtered

Nmap done: 1 IP address (1 host up) scanned in 54.66 seconds

[PabloTwo]

The Fedora firewall also blocks "interfaces". In your "system-config-firewall" GUI application, by default, all interfaces are marked as "untrusted". For ssh to work, on the machine you are ssh'ing into, you must go to the "Trusted Interfaces" tab and check off which ever of the interfaces you want to allow. Probably checking off "eth+" and "wlan+" will do for most circumstances. Save and exit.

[coffee412]

Note: Host seems down. If it is really up, but blocking our ping probes

Yep. Your blocked from access.

If you dont see your ports as visible from nmap then they are most likely blocked. You need to open up the port for your local network as PabloTwo stated.

Personally, My home network is secured by my server acting also as a firewall. Therefore I just tell the server to trust my nic running the local network and leave all ports open. Now it only has to worry about the nic heading out/in from internet.

Port 22 must be available for your local network in order to connect.

take care,

[PabloTwo]

@coffee412- My post wasn't referring to ports, it was referring to blocked "interfaces". Port 22 for ssh is enabled and open by default in F16.

[jswmcw]

Originally Posted by PabloTwo

Port 22 for ssh is enabled and open by default in F16.

Are you sure about this? I specifically remember having to enable ssh in the firewall settings. Of course, I cannot confirm this without a fresh install.



---------

Actually, I think I just had to start the service. Nevermind.

[coffee412]

Originally Posted by PabloTwo

@coffee412- My post wasn't referring to ports, it was referring to blocked "interfaces". Port 22 for ssh is enabled and open by default in F16.

Note: Host seems down. If it is really up, but blocking our ping probes....

Really?