Or it might be a security issue with how our VPN is setup. I'll talk to our security folks and see what they will find.
Thanks! -----Original Message----- From: Sanchez, Lily Sent: Tuesday, May 25, 2004 2:55 PM To: 'Tom Lane' Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: RE: [ADMIN] pg_hba.conf Um, I restarted postmaster so many times already after I made the entry and this is the only pg_hba.conf file in our server (you're right, $PGDATA/pg_hba.conf). It's a brand new server that had just been built. Have you tried connecting to your pgSQL server via VPN? Thanks! -----Original Message----- From: Tom Lane [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 25, 2004 2:51 PM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [ADMIN] pg_hba.conf <[EMAIL PROTECTED]> writes: > Here it is.... > host all all 10.29.15.0 255.255.255.0 trust That line certainly ought to match your connection. I think this has got to be pilot error: either you didn't SIGHUP the postmaster or you are editing the wrong copy of the file. (The right copy is $PGDATA/pg_hba.conf.) regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
