no route to host
no route to host
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
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
Re: no route to host
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
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
Re: no route to host
since its centos 7 i have just flushed it using iptables -F in sever A
Re: no route to host
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
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
Re: no route to host
Could you please tell how to add it back
Regards
Kannappan
Regards
Kannappan
Re: no route to host
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
what all the steps i need to do in server A and server B
Regards
Kannappan M
Re: no route to host
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
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.png (11.3 KiB) Viewed 8603 times
-
- server a
- server a.jpg (45 KiB) Viewed 8603 times
-
- Posts: 2019
- Joined: 2015/02/17 15:14:33
- Location: Bulgaria
- Contact:
Re: no route to host
You have to :
1. run a 'nmap' scan against the other server . Something like this should do the trick:
2.Check that the ssh service is actually running on destination host and on what port:
3.Disable firewalld on destination host to confirm if the firewall is your actual issue:Once your firewall is down - try to connect again.To enable the firewalld:
Edit: What is the output of:
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
Code: Select all
systemctl status sshd.service; netstat -tulpen | grep :22
Code: Select all
systemctl stop firewalld.service
Code: Select all
systemctl start firewalld.service
Code: Select all
ssh -vvv someuser@ServerB.somedomain.com