Received: from localhost (unknown [200.46.204.183]) by mail.postgresql.org (Postfix) with ESMTP id A7B26650109 for ; Fri, 5 Dec 2008 06:24:19 -0400 (AST) Received: from mail.postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 74248-06 for ; Fri, 5 Dec 2008 06:24:16 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from easy2.in-chemnitz.de (easy2.in-chemnitz.de [88.198.17.232]) by mail.postgresql.org (Postfix) with ESMTP id 7E62E6500FF for ; Fri, 5 Dec 2008 06:24:16 -0400 (AST) Received: from localhost (localhost [127.0.0.1]) by easy2.in-chemnitz.de (Postfix) with ESMTP id B851B47000E for ; Fri, 5 Dec 2008 11:24:14 +0100 (CET) Received: from easy2.in-chemnitz.de ([127.0.0.1]) by localhost (easy.in-chemnitz.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id MRXXOb00v+mw for ; Fri, 5 Dec 2008 11:24:14 +0100 (CET) Received: by easy2.in-chemnitz.de (Postfix, from userid 1013) id A8176470009; Fri, 5 Dec 2008 11:24:14 +0100 (CET) Date: Fri, 5 Dec 2008 11:24:14 +0100 From: Tino Schwarze To: pgsql-admin@postgresql.org Subject: Re: Remote access Message-ID: <20081205102414.GH8219@easy2.in-chemnitz.de> References: <20081205085352.GF8219@easy2.in-chemnitz.de> <813882.29714.qm@web95109.mail.in2.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <813882.29714.qm@web95109.mail.in2.yahoo.com> User-Agent: Mutt/1.5.13 (2006-08-11) X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200812/32 X-Sequence-Number: 30865 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 wrote: > > From: Tino Schwarze > > 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