Hello, I finally got it to work and as some have mentioned it was not the encryption level.
I had setup my pg_hba.conf originally like this: host all all 10.15.0.0 255.255.255.0 trust I was under the impression that the .0 was supposed to be equivalent to a wildcard entry so that any connection from 10.15 would be able to connect. This was not so. By changing my pg_hba.conf to this: host all all 10.15.13.0 255.255.255.0 trust I was able to connect successfully. The .0 works as a wildcard entry for the last part but not the one prior. Hope that helps you. Mike On Wed, 2004-05-26 at 10:25, [EMAIL PROTECTED] wrote: > Thanks so much! :) > > -----Original Message----- > From: Bruce Momjian [mailto:[EMAIL PROTECTED] > Sent: Wednesday, May 26, 2004 10:56 AM > To: [EMAIL PROTECTED] > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED]; > [EMAIL PROTECTED] > Subject: Re: [ADMIN] pg_hba.conf > > [EMAIL PROTECTED] wrote: > > Thanks Mike! > > > > Do you know if pgSQL will be supporting higher level of encryption in > > the near future? Most of us here at Ameritrade work from home via VPN. > > > We support SSL so you don't need VPN encryption. However, we should > work with whatever VPN encryption you are already using too. ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
