no route to host

Issues related to configuring your network
Post Reply
knzzz
Posts: 157
Joined: 2017/02/25 12:41:42

no route to host

Post by knzzz » 2017/08/02 10:20:28

Hi Team,

i have create the passwordless authentication from server A to Server B but when i try to login using the fqdn set for server b am getting error message as no rout to host

ssh: connect to host FQDN port 22: No route to host

kindly provide solution to fix this problem

Regards
Kanna

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: no route to host

Post by TrevorH » 2017/08/02 10:49:55

Does iptables on the target host allow connections on port 22 from your client?
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

knzzz
Posts: 157
Joined: 2017/02/25 12:41:42

Re: no route to host

Post by knzzz » 2017/08/02 11:54:27

since its centos 7 i have just flushed it using iptables -F in sever A

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: no route to host

Post by TrevorH » 2017/08/02 12:08:44

Which will make zero difference if the server is running firewalld as that will detect the missing rules and immediately add them back.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

knzzz
Posts: 157
Joined: 2017/02/25 12:41:42

Re: no route to host

Post by knzzz » 2017/08/02 12:14:50

Could you please tell how to add it back

Regards
Kannappan

knzzz
Posts: 157
Joined: 2017/02/25 12:41:42

Re: no route to host

Post by knzzz » 2017/08/02 12:15:43

Could you please tell how to add in back
what all the steps i need to do in server A and server B

Regards
Kannappan M

knzzz
Posts: 157
Joined: 2017/02/25 12:41:42

Re: no route to host

Post by knzzz » 2017/08/03 08:52:35

Hi Team,

i have added the port 22 in both server A and Server B please find the attachement

still facing the same problem

Regards
Kannappan M
Attachments
server b
server b
server b.png (11.3 KiB) Viewed 8603 times
server a
server a
server a.jpg (45 KiB) Viewed 8603 times

hunter86_bg
Posts: 2019
Joined: 2015/02/17 15:14:33
Location: Bulgaria
Contact:

Re: no route to host

Post by hunter86_bg » 2017/08/05 20:31:22

You have to :
1. run a 'nmap' scan against the other server . Something like this should do the trick:

Code: Select all

nmap -sS -p 22 serverB.somedomain.com
2.Check that the ssh service is actually running on destination host and on what port:

Code: Select all

systemctl status sshd.service; netstat -tulpen | grep :22
3.Disable firewalld on destination host to confirm if the firewall is your actual issue:

Code: Select all

systemctl stop firewalld.service
Once your firewall is down - try to connect again.To enable the firewalld:

Code: Select all

systemctl start firewalld.service
Edit: What is the output of:

Code: Select all

ssh -vvv someuser@ServerB.somedomain.com

Post Reply