Ubuntu :: SSH Server Only Wants To Work On The Very First Boot Of A Clean Install - No Route To Host Error
Apr 22, 2011
Ok so I just installed Ubuntu 10.10 Server Edition. On the very first boot, everything seems to run perfectly. I can SSH into it from any remote computer with no problems. However, the installation of certain things calls for a system reboot, which 2 days ago never would have been a problem. But now for some reason, the SSH server only wants to work on the very first boot of a clean install. After I reboot it, I get the ssh: connect to host 192.168.0.180 port 22: No route to host error. The absurd part is sshd is running! I've even tried restarting sshd, restarting the server, and using both 64 and 32 bit installs. The only way I can get anything to connect to it is by using ssh localhost. It won't even let me connect using the IP on the local machine!
I installed ntop on our server, after installing it, i ran ntop as a daemon. shortly after we lost the ability to ssh into the server.tried restarting ssh, but it didn't work, so had to restart the entire server.Where should we look to find why ssh suddenly stopped?
the error ssh gave when we try to connect was like: ssh: no route to host what log files should i look at and what should i look for to find the cause of the error?
My domain [URL]... has recently been moved to a new server. Since then, I have not been able to download email. Email sent to the domain can be seen in /var/spool/mail/akwebsoft, just as on the previous server. However when I go to download the email, I get the following error message (in part) in my fetchmail logfile:
I have 2 clients (one IP 200.x.y.52 and another 200.x.y.47) in ADSL conection and a same gateway (200.x.y.1).
When the server send an email, the error "No route to host" appear. I used TELNET 200.x.y.52 25 (110 soo) and the error occurr in both servers and both directions. The Firewall was disabled .
using redhat on server machine and open suse on client machine.i have installed nfs server and and it is running properly but when i want to mount shares from my client machine it gives the following.
error. "mount.nfs: mount to NFS server '10.3.31.146:/share' failed: System Error: No route to host" both systems ping each other and firewall is also disabled. another problem is when i remotely access from my server machine to client machine it gives the following error ssh:connect to host 10.3.31.147 port 22:connection refused what can be the problem?
I am using fedora 14..i wanna create webservice in fedora 14...i am able to create sevice in server machine...but the client not able to get service from the server.it shows an error an i/o error has occured.no route to host.....we checked the ip address and port...i am able to ping the server...its connecting ...but it shows this error...?
I have recently set up two machines with F14 and on both, I am completely unable to make remote login via SSH work. openssh-server is installed and seems to work well:
I have already worked for hours on the problem now, using Google and trying numerous things, and still could not find any solution. On my other machine, which still uses F13, remote login works just fine. Is there any change in the default behaviour of the sshd I am not aware of? I would really appreciate your assistance!
I am using Fedora-10 on 64-bit quad-core xeon processors. I ran ssh-keygen and established passwordless connection between host-client and created a host file named lamhosts as follows:
172.16.122.11 cpu=4 172.16.122.21 cpu=4
where 11 is the host server and 21 is one of the nodes. When I executed 'lamboot -v lamhosts', it failed to boot nodes ssi:boot:base:linear: Failed to boot n1 (172.16.122.21). By googling, I found the error but couldn't yet find a solution.
I am trying to share directories between two F12 machines on a local network with a router box doing DHCP because not all machines on all the time. Web access is fine and local ping and ssh works but telnet doesn't. I have never succeeded doing mounts. So I have been searching for things to fix the above and have just tried rpcinfo. If I do this :
rpcinfo -p 192.168.2.2 it gives rpcinfo: can't contact portmapper: RPC: Remote system error - No route to host. Does that suggest that actually there is an installation problem? So I tried "yum provides portmapper" and that gives "No Matches found".
I did a fresh install of SuSE 11.4 (WIN7 TOO) and changed my Larger HD1 to the first HD. I was installing and got this error first: the boot loader is installed on a partition that does not lie entirely below 128GB The system might not boot if BIOS supports only lba24 (result is error during install grub mbr) status loc dev/sdb6
I continued with the install and then got:
Yast2 error occured while installing GRUB ver 0.97 (640k lower/3072k upper memory) [minimal bash-like lineediting is supported? for the first word, TAB lists possible command completition anywhere else TAB lists possible completion of a device/filename] grub setup --stage2=/boot/grub/stage2 --force4-lba (hd0,5) (hd0,5) Error 25 disk read error grub> quit
I'm setting up apache on centOS 5.5 and administering it from another host on my LAN(this web server has no Xorg). I can ping from the config host to the web server but not the other way. My network is quite a way from being set up so i'm just configuring the web server at the moment, the simplest way i can. It's just trying to get two LAN hosts both with 192.168.1.0/24 I.Ps to talk to each other using a router to connect them.
Here are the outputs of ifconfig and netstat -rn for the web server, the config host and the router:
The ifconfig -a and netstat -rn of the config host are: lo0: flags=8049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x1
All I want is to be able to access files on one Ubuntu computer from another Ubuntu computer via a home wireless network. I have been at this for a week now. Scouring the web for answers and so far I have come up with this: Port 22 is open. I have both computers IP addr's via right clicking on the network icon-> Connection Information. ssh is installed and running. Both computers are listening on port22. But when I try Places->Connect to server, I get "no route to host". I'm not a networking guru and I'm at a complete loss on this.
It has been years since I had to mess with sendmail (I prefer using postfix) - but I inherited a server that someone else configured. This machine is a webserver - but is running sendmail for the various webforms, etc. I want to configure sendmail on this machine to route ALL outgoing messages to the main email server. This means local users too. I have read through sendmail configurations for the past 3 hours, but it's mostly greek. Here is my current sendmail.mc file - could some kind soul tell me what I need to change (and WHERE)?
I am trying to access a DVD mounted on a machine running Fedora12 (192.168.0.105). I thought this should be possible with NFS, but the above error message is what I keep getting, no matter what I try.
Here is my mount command: Code: mount 192.168.0.105:/mnt/dvd -t nfs /tmp/scaleo The Fedora 12 machine has the NFS server running, and the corresponding entry in /etc/exports is Code: /mnt/dvd *(ro)
I thought this might be a firewall problem, but it persists even if I turn firewalls off on both machines (client as well as server.) Also, doing Code: ssh 192.168.0.105 is OK, so what is wrong with the route?
I am trying to access a DVD mounted on a machine running Fedora12 (192.168.0.105). I thought this should be possible with NFS, but the above error message is what I keep getting, no matter what I try. Here is my mount command: Code: mount 192.168.0.105:/mnt/dvd -t nfs /tmp/scaleo
I now tried Code: mount 192.168.0.105:/mnt/dvd -t nfs4 /tmp/scaleo and it seems the mount succeeded. So, instead of nfs, one must write nfs4?
I'm trying to ssh from my laptop to my desktop (both fedora 14) over a local network. I can ping my desktop and get responses, but if I ssh to it, I receive
ssh: connect to host 192.168.100.xxx port 22: No route to host
Many of mails sent from my mail server that are in Queue;The main reason is deffered by domains like yahoo,aol,etc.but there is one more error that i keep getting and that is Host Unknown,Below is an example from mail log,The catch is,test mail sent on the same email id sent from my personal mail from the same server i.e. url was deliveredHowever,another mail containing client information sent from customercare@mycompanysdomain ended up in queue.
There are more examples of the same,around 20 domain have the same problem.
I install and configure the vncserver following and reading 1000papers, but all of this present the same problem; when i try to connect to my vncserver,recive this mesage: unable connect to socket: No route to host (113) The OS version is Fedora Core 14 and tigervnc-server i try different solutions including:Allow TCP connection modifing files /etc/gdm/custom.conf and /usr/share/gdm/gdm.chemas Disable SELinux removing iptables Here follow the vncserver configuration:
[code].....
The ip address of the vncserver is correct because i can do ssh on it. Where or what can i do?
I have two machines: A.domain.com: (Old mail server): Red Hat 9 (Linux 2.4.20-30.9) B.domain.com: (New mail server): RHEL Client 5 (2.6.18-164.2.1.el5) (Both machines are in the same subnet and on the same switch). I wanted to test the new mail server by sending an E-mail message to it from the old one, but the maillog says
[code]...
I can ping from A.domain.com to B.domain.com and from B.domain.com to A.domain.com . I can traceroute -p 25 from A.domain.com to B.domain.com and from B.domain.com to A.domain.com. I can *telnet* on port 25 from B.domain.com to A.domain.com. BUT when I telnet on port 25 from A.domain.com to B.domain.com. I get "telnet: connect to address x.x.x.x: No route to host". The resolved IP x.x.x.x is correct by the way. So I see no reason why. it should fail to telnet on port 25 to A.domain.com.
I have 3 computers on a local home network. Computer 1 is not receiving incoming anything from other computers on the network, and I don't know why. The regular internet works fine. Computer 1 can ping and ssh into either 2 or 3. 2 can ping and ssh into 3 and vice versa. But nothing can ping OR ssh into 1. Trying to do so says "no route to host". All computers are running Ubuntu Karmic. I don't even know where to start figuring out what's causing this, but it's probably something simple. I'm using the IPs I found listed in my wireless router's web-based control panel.
so on the host i'm trying to connect to, i have installed ssh server and it was working fine until i changed the /etc/network/interfaces file to set a static IP and then ran Code: sudo /etc/init.d/networking restart but now when i try to connect with SSH using the new static IP i get Code: ssh: connect to host 192.168.2.10 port 22: No route to host
Having trouble getting my Netgear WNA1000 working thru wireless router. Have tried lots of suggestions from other threads to no avail. Someone suggested that th routing table isn't set correctly, so have been trying to use the follwing to make the proper entry in the routing table: sudo route add -net 192.168.0.1 netmask 255.255.255.0 dev wlan0
Result: error message stating with: "route: netmask does not match route address"
followed by "Usage" instructions which tell me to do what I just did. Any ideas on how I can populate my routing table with correct entry for my wireless card? Not to complicate matters, but I temporarily turned off encryption on my router to eliminate that as a possibility until I get connected. So maybe it'still trying to connect via encrypted mode - do I need to turn off encryption on my (client) end?
I have 3 computers on a local home network. Computer 1 is not receiving incoming anything from other computers on the network, and I don't know why. The regular internet works fine.
Computer 1 can ping and ssh into either 2 or 3. 2 can ping and ssh into 3 and vice versa. But nothing can ping OR ssh into 1. Trying to do so says "no route to host".
I have a server that I can ping, and I can connect remotely with ssh to it. But when I try to connect to apache (port 80) I get "no route to host". But I can connect to localhost It's not just my client system that is having this problem but also systems that are on the same subnet There is no firewall running on the server route on the server
We have a Red Hat Linux server that sends email out daily. It points to and Exchange server for smtp. It works fine, however, at least once a day, an email will fail and in the maillog I see "No route to host". After a few minutes, everything is working fine. The Linux server and Exchange are on the same VLAN and IP subnet.
I have two system, an Intel Core2 Duo system running the 32-bit version of Fedora 12, and a MacBook Pro running the 64-bit version of Fedora 12. I'm using the Gnome desktop on each system. I have enabled all the services I believe are necessary to support NFS including nfs, rpcbind, rpcgssd, rpcidmapd, and rpcsvcgssd on each system. I have added an entry to my /etc/exports file to export my home on each system, and if I type this command:
$ showmount -e localhost
I get a result like this:
Export list for localhost:
/home/tron 192.168.200.101,192.168.200.100
However when I issue this type of command:
$ showmount -e <remote host name>
I get this kind of result: rpc mount export: RPC: Unable to receive; errno = No route to host Research on the Internet indicates this is usually due to a firewall problem. However, I use the Firewall Configuration application to the disable the firewall on both systems, and I continue to get the same result. What is needed so I can get this two machines to display their exported file shares remotely? It turns out I did not disable the firewall when I thought I had. Now that I'm certain the firewall is disabled on both systems, I'm able to get the showmount command to succeed.
