From: | mcravitz(at)att(dot)net |
---|---|
To: | pgsql-admin(at)postgresql(dot)org |
Subject: | Can't connect remotely |
Date: | 2008-05-07 16:12:00 |
Message-ID: | 050720081612.26557.4821D4D00006D5CD000067BD22230703729B0A02D29B9B0EBF969B07900E9D0C03@att.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
We've recently installed Postgresql 8.3 on a Windows Server 2003, Standard Edition, Service Pack 2 machine. I am able to connect locally via pgAdmin but not remotely.
The error message we are receiving in the Application event log is...
XX000: could not bind IPv4 socket: No error
The above occurs twice and then we get
WARNING 01000: could not create list socket for "loaner-mikec"
Our postgresql.conf contains...
#------------------------------------------------------------------------------
# CONNECTIONS AND AUTHENTICATION
#------------------------------------------------------------------------------
# - Connection Settings -
listen_addresses = 'localhost,marlon,loaner-mikec'
# what IP address(es) to listen on;
# comma-separated list of addresses;
# defaults to 'localhost', '*' = all
# (change requires restart)
port = 5432 # (change requires restart)
max_connections = 100 # (change requires restart)
host all all marlon/32 trust
host all all loaner-mikec/32 trust
host all all marlon trust
marlon, and loaner-mikec are two machine names from which we're trying to connect. We previously tried using ip address instead of machine names, but got the same negative symptoms.
Any help greatly appreciated.
From | Date | Subject | |
---|---|---|---|
Next Message | Barbara Stephenson | 2008-05-07 19:38:42 | Converting from 7.4.19 To 8.3.1 & want to use autovacuum |
Previous Message | Tom Lane | 2008-05-07 15:27:54 | Re: column: on update update? |