Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

From: Jacques Lamothe <JLamothe(at)allconnect(dot)com>
To: Adrian Klaver <adrian(dot)klaver(at)gmail(dot)com>
Cc: "rod(at)iol(dot)ie" <rod(at)iol(dot)ie>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org>
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Date: 2011-12-27 19:44:08
Message-ID: A464248CE14E60408AC030D3CD1790BA0271E7@ACMAILNODE01.allconnect.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Yes I'm running on amazon.aws and yes I requested my admin to open the port, do you know how I can check its status

iptables -L -vn
Chain INPUT (policy ACCEPT 44554 packets, 6381K bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 tcp dpt:5436

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination

Chain OUTPUT (policy ACCEPT 43998 packets, 6200K bytes)
pkts bytes target prot opt in out source destination

-----Original Message-----
From: Adrian Klaver [mailto:adrian(dot)klaver(at)gmail(dot)com]
Sent: Tuesday, December 27, 2011 2:42 PM
To: Jacques Lamothe
Cc: rod(at)iol(dot)ie; pgsql-general(at)postgresql(dot)org
Subject: Re: [GENERAL] UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL

On 12/27/2011 11:39 AM, Jacques Lamothe wrote:
> Yes I did

More guesses.
Looks like you may be running on Amazon AWS?
If so, did you change the AWS firewall to allow port 5436?

>
>

--
Adrian Klaver
adrian(dot)klaver(at)gmail(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message John R Pierce 2011-12-27 19:46:14 Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Previous Message Adrian Klaver 2011-12-27 19:41:34 Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL