Skip site navigation (1) Skip section navigation (2)

Re: Configure foreign host for PostgreSQL 8.0.3 on WindowsXP

From: "Dario" <dario_d_s(at)unitech(dot)com(dot)ar>
To: <pgsql-admin(at)postgresql(dot)org>
Subject: Re: Configure foreign host for PostgreSQL 8.0.3 on WindowsXP
Date: 2005-09-28 12:57:27
Message-ID: MHEDJHCKDNOEHJKHIOCJOEMLCHAA.dario_d_s@unitech.com.ar (view raw or flat)
Thread:
Lists: pgsql-admin
this line
 host    all         all            192.168.2.120/24       md5
                                    ----------------

makes no sense to me, and probably neither to postgresql, it should be:
192.168.2.120/32       # if 192.168.2.120 is your client, this should be
enough
or
192.168.2.0/24         # if you wanted to allow all host in subnet to
validate thru md5, use this


long life, little spam and prosper.

-----Mensaje original-----
De: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org]En nombre de Magnus Hagander
Enviado el: miercoles, 28 de septiembre de 2005 5:14
Para: Todd Rockhold; pgsql-admin(at)postgresql(dot)org
Asunto: Re: [ADMIN] Configure foreign host for PostgreSQL 8.0.3 on
WindowsXP


> Installed PostgreSQL 8.0.3 on WindowsXP.  Have not been able
> to configure so that a client program running on a different
> WindowsXP box can connect to the PostgreSQL database.
>
> As I understand the documentation, at least one of the
> following configurations should work, but none do.  What have
> I done wrong and how can I configure so that a connection can
> be successfully made?
>
>
> 1) The postgresql.conf file has (with everything else being
> the installation default values):
>
> listen_addresses = '*'
>
> 2) None of the following configurations of the pg_hba.conf
> file worked (the program runs on 192.168.2.120):
>
> # IPv4 local connections:
> #host    all         all         127.0.0.1/32          md5
> host    all         all            192.168.2.120/24       md5
>
> # IPv4 local connections:
> #host    all         all         127.0.0.1/32          md5
> host    all         all            192.168.2.120
> 255.255.255.255       md5
>
> # IPv4 local connections:
> host    all         all         127.0.0.1/32          md5
> host    all         all         192.168.2.120/24       md5
>
> # IPv4 local connections:
> host    all         all         127.0.0.1/32          md5
> host    all         all            192.168.2.120
> 255.255.255.255       md5
>
> I have a Symantec personal firewall installed which I turned
> off during testing.
>
> The program runs fine on localhost.
>
> Am using the Npgsql .NET library.  The Npgsql.Npgsql.Open()
> call throws an exception, the error text of which is
> "System.Net.Sockets.SocketException: NO connection could be
> made because the target machine actively refused it."

Check:
1) the listen_address='*' didn't "take". Make sure you remembered to
remove the comment sign (yup, i've seen that mistake manu times). Also,
you need to restart the service after you've changed that, perhaps you
forgot it?
2) Is there any chance that the postmaster is running on a non-default
port? Or that the client is connecting on a non-standard port?
3) Verify that the IP Npgsql connects to is correct. If you're using a
DNS name, make sure it resolves right.

If all those look right, run a "netstat -na" on the commandline and see
if there is a listener to port 5432 and what IP that one is bound to.

//Magnus

---------------------------(end of broadcast)---------------------------
TIP 6: explain analyze is your friend


In response to

pgsql-admin by date

Next:From: Jerry CadetDate: 2005-09-28 15:13:43
Subject: pg_dump error
Previous:From: sandhyaDate: 2005-09-28 11:02:28
Subject: Re: database access queries

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group