pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: mike g <mike@thegodshalls.com>
To: LSanchez@ameritrade.com
Cc: xzilla@users.sourceforge.net
Cc: pgsql-admin@postgresql.org
Subject: Re: pg_hba.conf
Date: Tue, 25 May 2004 23:51:29 -0500
Message-ID: <1085547089.1556.12.camel@localhost.localdomain> (raw)
In-Reply-To: <1085544723.1556.5.camel@localhost.localdomain>
References: <2898C2526ECBEB448D434BA1F3027909034D9778@scsdcmail1.ameritrade.com>
	<1085544723.1556.5.camel@localhost.localdomain>

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



view thread (53+ messages)  latest in thread

Message-ID: <1085547089.1556.12.camel@localhost.localdomain>
Permalink:  ../1085547089.1556.12.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1085547089.1556.12.camel@localhost.localdomain

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-admin@postgresql.org
  Cc: mike@thegodshalls.com, LSanchez@ameritrade.com, xzilla@users.sourceforge.net
  Subject: Re: pg_hba.conf
  In-Reply-To: <1085547089.1556.12.camel@localhost.localdomain>
  References: <2898C2526ECBEB448D434BA1F3027909034D9778@scsdcmail1.ameritrade.com> <1085544723.1556.5.camel@localhost.localdomain> <1085547089.1556.12.camel@localhost.localdomain>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox