OK, I've found what worked for me.
By default, the pg_hba file installs like so:
# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD
local all all trust
# IPv4-style local connections:
host all all 127.0.0.1 255.255.255.255 trust
# IPv6-style local connections:
host all all ::1 :::ff
I've been watching this thread because I am experience exactly the same
thing. I can also repeat all the diagnostic results of Conni. Postmaster
resides on a Win 2K box. I can telnet to the server no problem. My pg_hba
file line entries will allow access from all hosts, all users, all databases
Tom Lane <[EMAIL PROTECTED]> writes:
> "Cornelia Boenigk" <[EMAIL PROTECTED]> writes:
>> C:\>psql -h 192.168.1.8 -U postgres -d minitest
>> psql: could not connect to server: Connection refused
>> Is the server running on host "192.168.1.8" and accepting
>> TCP/IP connections on po
"Cornelia Boenigk" <[EMAIL PROTECTED]> writes:
> C:\>psql -h 192.168.1.8 -U postgres -d minitest
> psql: could not connect to server: Connection refused
> Is the server running on host "192.168.1.8" and accepting
> TCP/IP connections on port 5432?
"Connection refused" suggests that
Hi Magnus
Thanks.
> If you meant to match the entire subnet (192.168.*.*), instead put
> host minitest postgres 192.168.0.0 255.255.0.0 password
Ok. I changed the line in pg_hba.conf to
host all all 192.168.0.0 255.255.0.0 password
then rebooted the computer and tried again:
C:\>psql -h 192.
