X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (unknown [200.46.204.2]) by svr1.postgresql.org (Postfix) with ESMTP id 814B8D1B57A for ; Wed, 26 May 2004 01:52:14 -0300 (ADT) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (neptune.hub.org [200.46.204.2]) (amavisd-new, port 10024) with ESMTP id 62959-10 for ; Wed, 26 May 2004 01:51:55 -0300 (ADT) Received: from rwcrmhc11.comcast.net (rwcrmhc11.comcast.net [204.127.198.35]) by svr1.postgresql.org (Postfix) with ESMTP id 93266D1B3AD for ; Wed, 26 May 2004 01:51:53 -0300 (ADT) Received: from localhost.localdomain (c-67-162-79-220.client.comcast.net[67.162.79.220]) by comcast.net (rwcrmhc11) with ESMTP id <2004052604515301300f4hl2e>; Wed, 26 May 2004 04:51:53 +0000 Received: from localhost.localdomain (localhost.localdomain [127.0.0.1]) by localhost.localdomain (8.12.11/8.12.11) with ESMTP id i4Q4pTSa001767; Tue, 25 May 2004 23:51:29 -0500 Received: (from spike@localhost) by localhost.localdomain (8.12.11/8.12.11/Submit) id i4Q4pTij001764; Tue, 25 May 2004 23:51:29 -0500 X-Authentication-Warning: localhost.localdomain: spike set sender to mike@thegodshalls.com using -f Subject: Re: pg_hba.conf From: mike g Reply-To: mike@thegodshalls.com To: LSanchez@ameritrade.com Cc: xzilla@users.sourceforge.net, pgsql-admin@postgresql.org In-Reply-To: <1085544723.1556.5.camel@localhost.localdomain> References: <2898C2526ECBEB448D434BA1F3027909034D9778@scsdcmail1.ameritrade.com> <1085544723.1556.5.camel@localhost.localdomain> Content-Type: text/plain Content-Transfer-Encoding: 7bit Message-Id: <1085547089.1556.12.camel@localhost.localdomain> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.4.5 (1.4.5-7) Date: Tue, 25 May 2004 23:51:29 -0500 X-Virus-Scanned: by amavisd-new at postgresql.org X-Spam-Status: No, hits=0.1 tagged_above=0.0 required=5.0 tests=RCVD_IN_SORBS X-Spam-Level: X-Archive-Number: 200405/269 X-Sequence-Number: 13585 Hello, I believe I found my problem. The Cisco VPN client I use encrypts data at a 168 bit level. Postgres only supports up to 128 bit correct? Mike On Tue, 2004-05-25 at 23:12, mike g wrote: > Hmm.... > > Looks like I am still in the same boat you are. > > I still cannot log into my db over a VPN connection using pgadminIII. > > Everytime I try and connect I get a "Server terminated connection > unexpectedly error". > > I originally received the pg_hba.conf entry complaint as well but after > adding and restarting the system the above is all I get. > > I tried specifying pgadmin to prefer SSL connection, and changed > pg_hba.conf entry to expect SSL from my VPN connection entry. > > > On Tue, 2004-05-25 at 08:42, LSanchez@ameritrade.com wrote: > > Thanks Mike! > > > > I already specified the IP address that was specified by my VPN > > connection. I read through the docs and found nothing about anything > > special with VPN connections. > > > > Regards, > > - Lily Anne > > > > -----Original Message----- > > From: Mike G [mailto:mike@thegodshalls.com] > > Sent: Monday, May 24, 2004 10:23 PM > > To: LSanchez@ameritrade.com > > Cc: xzilla@users.sourceforge.net; pgsql-admin@postgresql.org > > Subject: Re: [ADMIN] pg_hba.conf > > > > Your ip address range is probably different when connecting via a VPN > > rather than in the office. By default postgres will not allow > > connections from other locations even if tcpip_socket is true without > > specifying an ip address range, database etc. > > > > Checkout the docs. There is a section on pg_hba.conf. > > > > Mike > > > > On Mon, May 24, 2004 at 01:02:12PM -0400, LSanchez@ameritrade.com wrote: > > > Yes I can ping the server if not connected via VPN. > > > > > > I'm using EMS PostgreSQL Manager, which works if not via VPN. > > > > > > Yes, postgresql.conf's tcpip_socket = true. > > > > > > The log says: FATAL: No pg_hba.conf entry for host 10.29.15.113, user > > > postgres, database TEST. > > > > > > Thanks for your help! > > > > > > Regards, > > > - Lily Anne > > > > > > > > > -----Original Message----- > > > From: Robert Treat [mailto:xzilla@users.sourceforge.net] > > > Sent: Friday, May 21, 2004 8:04 PM > > > To: LSanchez@ameritrade.com > > > Cc: pgsql-admin@postgresql.org > > > Subject: Re: [ADMIN] pg_hba.conf > > > > > > can you ping the server that postgresql is living on? or maybe your > > > misrepresenting the error message... what program are you using to > > try > > > and > > > connect? can you verify that tcpip_sockets is turned on the server? > > > also, if > > > it is a database problem there will be an exact error message being > > > reported > > > in the logs of type FATAL, can you send us that? > > > > > > Robert Treat > > > > > > On Friday 21 May 2004 17:01, LSanchez@ameritrade.com wrote: > > > > Thanks Robert! > > > > > > > > I did that as well and still didn't work. Any other ideas? > > > > > > > > -----Original Message----- > > > > From: Robert Treat [mailto:xzilla@users.sourceforge.net] > > > > Sent: Friday, May 21, 2004 4:41 PM > > > > To: LSanchez@ameritrade.com > > > > Cc: pgsql-admin@postgresql.org > > > > Subject: Re: [ADMIN] pg_hba.conf > > > > > > > > On Thu, 2004-05-20 at 19:52, LSanchez@ameritrade.com wrote: > > > > > I'm trying to access our test postgreSQL server via VPN and even > > > > > > > > though > > > > > > > > > I already setup the host for the vpn's ip address, I'm still > > getting > > > > > > > > an > > > > > > > > > error similar to "host for vpn address does not exist" > > > > > > > > > > What am I doing incorrectly? > > > > > > > > The error similar to that that I am thinking of would indicate that > > > the > > > > ip address of your client machine does not fall into the scheme laid > > > out > > > > in your pg_hba.conf. Most likely you need to add your home machines > > ip > > > > into the pg_hba.conf (or open up one of the existing entries to > > > include > > > > the machine your connecting from) > > > > > > > > HTH > > > > > > > > Robert Treat > > > > > > -- > > > Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL > > > > > > ---------------------------(end of > > broadcast)--------------------------- > > > TIP 4: Don't 'kill -9' the postmaster > > > > ---------------------------(end of broadcast)--------------------------- > > TIP 7: don't forget to increase your free space map settings