Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: cloudstack-dev@incubator.apache.org
Received-SPF: pass (nike.apache.org: domain of Frank.Zhang@citrix.com
 designates 66.165.176.89 as permitted sender)
From: Frank Zhang <Frank.Zhang@citrix.com>
To: "cloudstack-dev@incubator.apache.org"
	<cloudstack-dev@incubator.apache.org>, "Development discussions for
 CloudStack (cloudstack-devel@lists.sourceforge.net)"
	<cloudstack-devel@lists.sourceforge.net>, "CloudStack user/admin discussions
 (cloudstack-users@lists.sourceforge.net)"
	<cloudstack-users@lists.sourceforge.net>
Date: Wed, 25 Apr 2012 15:39:41 -0700
Subject: RE: Tips for "No route to host", "Connection refused", "Connection
 reset"
Thread-Topic: Tips for "No route to host", "Connection refused", "Connection
 reset"
Thread-Index: Ac0jMP2ce2SGlJcfSWeHzGfKwiCNUQAAz2yA
Message-ID: 
 <93099572B72EB341B81A644E134F240B011CF644726D@SJCPMAILBOX01.citrite.net>
References: 
 <93099572B72EB341B81A644E134F240B011CF6447269@SJCPMAILBOX01.citrite.net>
 <CBBDC585.170FF%Ahmad.Emneina@citrix.com>
In-Reply-To: <CBBDC585.170FF%Ahmad.Emneina@citrix.com>
Accept-Language: en-US
Content-Language: en-US
acceptlanguage: en-US
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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 s=
ame

-----Original Message-----
From: Ahmad Emneina [mailto:Ahmad.Emneina@citrix.com]=20
Sent: Wednesday, April 25, 2012 3:16 PM
To: cloudstack-dev@incubator.apache.org; Development discussions for CloudS=
tack (cloudstack-devel@lists.sourceforge.net); CloudStack user/admin discus=
sions (cloudstack-users@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

--=20
=E6


On 4/25/12 3:05 PM, "Frank Zhang" <Frank.Zhang@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.