Have you guys started postmaster with the –i option to tell it to listen and accept connections via TCP/IP, instead of just via the *nix sockets??
Cheers,
-p
-----Original Message-----
From: pgsql-novice-owner@postgresql.org [mailto:pgsql-novice-owner@postgresql.org] On Behalf Of Jasbinder Bali
Sent: Friday, 11 August 2006 07:28
To: Walid Haider
Cc: pgsql-novice@postgresql.org
Subject: Re: [NOVICE] Unable to connect to PostgreSQL 8 from PGAdmin III
What does your connection string look like?
I''m also banging my head on the same problem for the past one day.
On 8/10/06, Walid Haider <whaider@odline.com> wrote:
Hi All,
I have been trying to connect to PostgreSQL 8 (which is installed on an FC4 server with a public IP address) from PGAdmin III, and I am getting the following error:
Error connecting to the server: could not connect to server: Connection timed out (0x0000274C/10060)
Is the server running on host "XX.XXX.XXX.XXX" and accepting
TCP/IP connections on port 5432?
From a terminal on the server, on the server I can connect to the 'test' database that I created after installation of PostgreSQL.
I have read on various sites on the internet that this issue could be associated with the "tcpip_socket" flag being set to FALSE, this flag is not available in the postgresql.conf file?
On the postgresql.conf file, I have done the following:
listen_addresses = '*'
port = 5432
On the pg_hba.conf file, I have done the following:
Located the line beginning with "TYPE" and added entries as applicable
TYPE DB USER CIDR-ADDRESS METHOD
host all all XX.XX.XXX.XXX/24 trust # remote access
host all all XX.XX.XX.XX/24 trust # remote access
Any ideas where I am going wrong?
Thanks
Walid
*******************Confidentiality and Privilege Notice*******************
The material contained in this message is privileged and confidential to the addressee. If you are not the addressee indicated in this message or responsible for delivery of the message to such person, you may not copy or deliver this message to anyone, and you should destroy it and kindly notify the sender by reply email.
Information in this message that does not relate to the official business of Weatherbeeta must be treated as neither given nor endorsed by Weatherbeeta. Weatherbeeta, its employees, contractors or associates shall not be liable for direct, indirect or consequential loss arising from transmission of this message or any attachments
