pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tino Schwarze <postgresql@tisc.de>
To: pgsql-admin@postgresql.org
Subject: Re: Remote access
Date: Fri, 5 Dec 2008 11:24:14 +0100
Message-ID: <20081205102414.GH8219@easy2.in-chemnitz.de> (raw)
In-Reply-To: <813882.29714.qm@web95109.mail.in2.yahoo.com>
References: <20081205085352.GF8219@easy2.in-chemnitz.de>
	<813882.29714.qm@web95109.mail.in2.yahoo.com>

On Fri, Dec 05, 2008 at 03:23:26PM +0530, Abubaker wrote:
> I restarted my service and the netstat now shows the correct details.
> 
>   TCP    0.0.0.0:5432           0.0.0.0:0              LISTENING

Looks good.
 
> But its still showing the same error.  I am trying to connect with the
> "Add Server" method in pgAdmin III. I am using postgresql in windows.

Sounds like some firewall inbetween. Open a command line and try the
following to check basic network connectivity:

1. ping your_server
and if that works
2. telnet your_server 5432

Are you sure you don't have a firewall on the client or inbetween?

HTH,

Tino.

> On Fri, Dec 05, 2008 at 02:51:59PM +0530, Abubaker wrote:
> 
> > Thanks for the information. But how do I change the listening ip
> > address to 0.0.0.0
> 
> Simply restart postgres.
> 
> Your
> listen_addresses = '*'
> in postgresql.conf should do it. I suppose, you forgot to restart
> postgresql (reload might not be enough).
> 
> HTH,
> 
> Tino.
> 
> > --- On Fri, 5/12/08, Tino Schwarze <postgresql(at)tisc(dot)de> wrote:
> > From: Tino Schwarze <postgresql(at)tisc(dot)de>
> > Subject: Re: [ADMIN] Remote access
> > To: pgsql-admin(at)postgresql(dot)org
> > Date: Friday, 5 December, 2008, 12:53 AM
> > 
> > Hi,
> > 
> > > I am getting this error when I try to access the database in another
> > computer within the same network.
> > > 
> > > could not connect to server: Connection timed out (0x0000274C/10060). Is
> > the server running on host "XX.XX.XX.XX" and accepting TCP/IP
> > connections on port 5432?
> > > 
> > [...]
> > 
> > > My postgresql.conf file line:
> > > 
> > > listen_addresses = '*'
> > 
> > correct.
> > 
> > > Netstat details:
> > > TCP    127.0.0.1:5432        
> > 0.0.0.0:0              LISTENING
> > 
> > Not correct. It should display 0.0.0.0:5432. Did you restart postgres
> > after you changed postgresql.conf?
> > 
> > > I have disabled all the firewall. Can someone help me with this error?
> > 
> > Connection timed out sounds like a firewall dropping packets, though. It
> > should be "Connection refused". But try to make it listen on 0.0.0.0
> > first.
> > 
> > HTH,
> > 
> > Tino.
-- 
"What we nourish flourishes." - "Was wir nähren erblüht."

www.lichtkreis-chemnitz.de
www.craniosacralzentrum.de



view thread (14+ messages)

Message-ID: <20081205102414.GH8219@easy2.in-chemnitz.de>
Permalink:  ../20081205102414.GH8219@easy2.in-chemnitz.de/
Also on:    postgresql.org/message-id/20081205102414.GH8219@easy2.in-chemnitz.de

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-admin@postgresql.org
  Cc: postgresql@tisc.de
  Subject: Re: Remote access
  In-Reply-To: <20081205102414.GH8219@easy2.in-chemnitz.de>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox