Yes. if you don't have route for 1, it's the same error. However, even I have route but iptable close it, the error message is the same
-----Original Message----- From: Ahmad Emneina [mailto:ahmad.emne...@citrix.com] Sent: Wednesday, April 25, 2012 3:16 PM To: cloudstack-dev@incubator.apache.org; Development discussions for CloudStack (cloudstack-de...@lists.sourceforge.net); CloudStack user/admin discussions (cloudstack-us...@lists.sourceforge.net) Subject: Re: Tips for "No route to host", "Connection refused", "Connection reset" 1. Sounds like a routing issue. Packet flow cant reach the destination. 2. Sounds like a firewall/no service issue -- æ On 4/25/12 3:05 PM, "Frank Zhang" <frank.zh...@citrix.com> wrote: >This is not only for CloudStack, but they are common issues when you are >playing CloudStack regarding network. >I often suffer these errors, there are some tips from my practice: > > >1. "No route to host" >Most likely iptables rule prevents the port from accessing. First check >iptables rule in your VM, then check SecurityGroup rules in CloudStack. >Finally check the rules in host where the VM is running(in this case, >please file a bug for SecurityGroup) > > >2. "Connection refused" > >The destination port is reachable, however, there is no application >listens on that port > > > >3. "Connection reset" > >The established connection has lost. > >Please correct me if you see anything wrong.
