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
I can ssh from the desktop to itself.
Yesterday I installed a RaLink RT2800 802.11n PCI on my squeeze system. Now I have a connection to Internet but I can not connect other systems in my home network. An ssh-try to a system in my home network results in: ssh: connect to host xxx.xxx.xxx.xxx port 22: No route to host If I use my eth0, I do not have connection to Internet, but I can connect other systems in my home network.
View 7 Replies View RelatedI 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 wanaa to config tlenet server and did the steps to enable it
but when i try to connect to server this error show :
telnet : connect to address 10.0.0.100 : No route to host
telnet : Unable to connect to remote host : No route to host
[URL]
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.
View 9 Replies View RelatedRight now I have a machine set up running Fedora. I have configured inittab to accept Console Logins, but I am having problems getting my netbook running PuTTY to connect. How would I go about finding the Host Name and Port to connect to?
View 6 Replies View RelatedCode:
Code:
Code:
Code:
Code:
Why can I not reach 192.168.1.1 ?
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...?
View 1 Replies View RelatedNetstat has always confused me. I ype netstat -pl and get this:
Code:
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 localhost:ipp *:* LISTEN 1476/cupsd
tcp 0 0 localhost:postgresql *:* LISTEN 13816/postgres
tcp 0 0 *:44223 *:* LISTEN 1288/sshd
tcp6 0 0 localhost:ipp [::]:* LISTEN 1476/cupsd
tcp6 0 0 localhost:postgresql [::]:* LISTEN 13816/postgres
tcp6 0 0 [::]:44223 [::]:* LISTEN 1288/sshd
udp 0 0 *:bootpc *:* 1267/dhclient
I assume that *:* means that any foreign host can connect from any port, but then what does [::]:* mean? and localhost:ipp... what port is ipp? Shouldn't ports be numeric?
I cannot use GRsync from Ubuntu Desktop to PCLinuxOS laptop.The 2 computers can ping each other. I have disabled both firewalls. My laptop IP address is 192.168.1.11This is the error on Ubuntu Grsync:
ssh: connect to host 192.168.1.11 port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: error in rsync protocol data stream (code 12) at io.c(601) [sender=3.0.7]
Rsync process exit status: 12
On PCLinuxOS it wont say Ethernet is connected when trying a static address setup.However it does connect to the internet via auto Ethernet setup and a LAN cable. It then says connected. In order to use SSH and GRsync what programs are required? I have these installed on both machines: grsync openssh-client openssh-server
I am facing trouble to scp from server to to my local machine where as the vice-vesra is working fine.
The error is like below.
lost connection
I have become convinced that rsync for CentOS 5 is broken. I'm trying to set up automatic backups between 2 servers in 2 different countries using rsync under CentOS 5.I can get manual backups to work between the 2 servers by doing two things I shouldn't need to do, but automatic backups fail and I see no solution.Here are the problems I am encountering: According to the instructions I've read everywhere, I am to set up two configuration files:
/etc/rsyncd.conf
/etc/rsyncd.secrets
When I run rsync from root, it apparently just totally ignores these two files. No custom greeting, no log, no password used.
Even when I specify --password-file=/etc/rsyncd.secrets in the command line, it still ignores it. I am prompted and I must enter the password manually. Let me back up a moment. After first installing rsync, when I ran any command to access the root server, I get this error:
ssh: connect to host 111.222.33.44 port 22: Connection refused
rsync: connection unexpectedly closed (0 bytes received so far) [sender]
rsync error: unexplained error (code 255) at io.c(463) [sender=2.6.8]
I read everywhere that rsync uses port 873, not port 22 which is used for SSH. Why is rsync on CentOS trying to use port 22?I have SSH switched from port 22 to another port (let's call it 5432 here) and block port 22.So, I have added this to the command line:
--rsh='ssh -p5432'
Then I get a connection ...
... but it prompts me for my password. It doesn't matter that I have my username and password, same one, in /etc/rsyncd.secrets on both servers. It still asks.And it rejects my password!The only way I can get it to connect is by creating an SSH user on the remote server for this.Even then, rsync STILL prompts me for a password, even though:
1. the username and password are specified in the /etc/rsyncd.secrets files on both servers
2. I've added the command line parameter --password-file=/etc/rsyncd.secrets Therefore, it is totally impossible to use an any cron job or other automatic synchronization, under CentOS 5.
rsync -av --password-file=/etc/rsyncd.secrets --rsh='ssh -p5432' sourcefiles* rsyncusername@111.222.33.44:httpdocs/rsync
rsync -av --password-file=/etc/rsyncd.secrets --rsh='ssh -p5432' sourcefiles* 111.222.33.44:httpdocs/rsync
rsync -av --verbose --progress --stats --password-file=/etc/rsyncd.secrets --rsh='ssh -p5432' sourcefiles* rsyncusername@111.222.33.44:httpdocs/rsync
Yes, I have made sure that I have the latest rsync. I have run yum update for everything.Yes, I have double checked, triple checked, and quadruple checked my config files.
I've trying to add a route to a host to force traffic out of a clustered IP address...
IE I have a cluster and the IP address moves from host to host on failure of a resource. The IP address is just a simple alias of an interface so for example... bond0:0 192.168.1.1 and bond0 192.168.1.10
What I want to do is force a program that starts up on the cluster hosts which sends packets out to a listening server to only send out of the cluster ip address.
I did a route add -host 172.22.2.2 gw 192.168.1.1. But this doesn't seem to work if i try to send a ping the packets still go out the wrong address, and more and above that for some reason the ping doesn't work at all. If i remove the route the ping will work again.
I have my desktop computer (running F13) configured to accept ssh over port 22 via the firewall configuration tool. If I type ifconfig -a, this computer, which is running on my wireless network, tells me:
Code:
inet addr:192.168.1.100 Bcast:192.168.1.255 Mask:255.255.255.0
However, if I go to my laptop computer (also running F13) and try and ssh into the desktop, i.e. ssh icthy@192.168.1.100, I get this response:
Code:
ssh: connect to host 192.168.1.100 port 22: Connection refused.
I guess I am confused to what is blocking the connection? Is there another means on F13 other than the default Firewall? I haven't really messed with the network at all. For what it's worth, I am hoping to set things up so I can just ssh into the computer name, (ssh icthy@desktop) eventually, but want to start with the IP. So, can anyone offer a hint as to what I can look for that is blocking port 22?
I am getting "ssh:connect to host restart port 22: Connection refused" error when trying to start "ssh" in Ubuntu. I uncommented the port 22 in ssh_config, I dont have iptables setup...Did try to check if the port is listening using the netstat -an | grep "LISTEN" & couldnt find.
View 9 Replies View RelatedI have been playing with this for awhile now and I am ready to go postal.
I just want to move some files around and potentially rsync my net book with my desktop as well as learn the software (my primary reason)
Steps Taken.
Set Static IP address to machines on LAN
Turned on Port Forwarding (22)
Added Rule to UFW allow 22/TCP
I have a Windows machine on which NX Client has been installed. I wanted to test if I could access my Ubuntu box. The Ubuntu Box has NX Server, Node and Client installed. When I try to log in from the Windows machine using NX Client with my Ubuntu username and password I get an error connection refused.
The following service is running: OpenBSD Secure Shell server sshd How can I resolve the issue?
I'm having problems with ssh and don't know what else to do. I keep getting "ssh: connect to host stop port 22: Connection refused" when i try to stop or start ssh:
[Code]....
I am getting "ssh:connect to host restart port 22: Connection refused" error when trying to start "ssh" in Ubuntu. I uncommented the port 22 in ssh_config, I dont have iptables setup...Did try to check if the port is listening using the netstat -an | grep "LISTEN" & couldnt find.
View 14 Replies View RelatedI have installed ubuntu 11.04 and I'm now trying to connect to existing SUSE servers on the LAN. My home directory has a shared NFS mounted home on the SUSE servers while my home on the ubuntu machine is local. I can log in using ssh to all the SUSE servers except one. I get:
ssh: connect to host srv3 port 22: Connection refused
If I use the IP address of srv3 directly it works. Also, before I changed the default machine name ("ubuntu") I could log into srv3.
nslookup srv3 works OK.
ping srv3 works OK.
Even if I completely delete the .ssh directory in both my ubuntu home and in my shared home on the SUSE servers I still cannot log in using the srv3 name, only direct IP address works. I'm thinking that the login I did to srv3 before I changed the machine name for the ububtu machine must have goofed up something
I've been trying to ssh out of my home network to school computers and I keep getting:
ssh: connect to host sage.math.washington.edu port 22: Connection timed out
I've tried this on my machine (running Ubuntu 10.04) and on a windows 7 machine (using putty). I have been successful ssh'ing to this machine using either of the laptops from every other network I've tried, so I'm pretty sure it's something about my home network.
I'm trying to connect with my server via telnet, but when i sent the command (telnet xxx.xxx.xxx.xxx Port) doesn't works and shows then follow error: Unable to connect to remote host: Connection refused, It happens with any port. Is strange but my telnet services works (telnet xxx.xxx.xxx.xxx), In addition, i tried with firewall enabled and disabled and the problem still happens. My centOS run on virtualbox.
View 3 Replies View RelatedI use linux.
I have below error, no route to host.
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 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
[Code]...
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.
View 2 Replies View RelatedI have two servers, one has an empty / and the other has a subdirectory with a large number (4 gig) with many, many files. I need a way to transfer the files en masse from the server with the large number of files to the one that is essentially blank.I don't have space on the used host to simply gzip all the files. I've googled this and see that there may be some combination of tar and/or gzip that will let me do this with some sort of redirection.
I really need and example line of how this can be accomplished. If my explanation seems rather sparse, I can supply more details.
when I am run:
ssh -v "login"@"server"
I get:
OpenSSH_5.3p1 Debian-3ubuntu4, OpenSSL 0.9.8k 25 Mar 2009
debug1: Reading configuration data /etc/ssh/ssh_config
debug1: Applying options for *
debug1: Connecting to server ["address"] port 22.
debug1: connect to address "address" port 22: Connection timed out
ssh: connect to host "server" port 22: Connection timed out
I suppose this is because I am connecting from a public institute where there is a firewall that is blocking an outbound connection on port 22.Is there anyway I can bypass the firewall using the internet ?
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.