Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL - Mailing list pgsql-general

From Jacques Lamothe
Subject Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Date
Msg-id A464248CE14E60408AC030D3CD1790BA0271E7@ACMAILNODE01.allconnect.com
Whole thread Raw
In response to Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL  (Adrian Klaver <adrian.klaver@gmail.com>)
Responses Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
List 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.klaver@gmail.com]
Sent: Tuesday, December 27, 2011 2:42 PM
To: Jacques Lamothe
Cc: rod@iol.ie; pgsql-general@postgresql.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.klaver@gmail.com

pgsql-general by date:

Previous
From: Adrian Klaver
Date:
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL
Next
From: John R Pierce
Date:
Subject: Re: UNABLE TO CONNECT REMOTELY TO port 5436 - CRITICAL