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.
-----Original Message----- From: mike g [mailto:[EMAIL PROTECTED] Sent: Wednesday, May 26, 2004 12:51 AM To: [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] Subject: Re: [ADMIN] pg_hba.conf 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, [EMAIL PROTECTED] 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:[EMAIL PROTECTED] > > Sent: Monday, May 24, 2004 10:23 PM > > To: [EMAIL PROTECTED] > > Cc: [EMAIL PROTECTED]; [EMAIL PROTECTED] > > 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, [EMAIL PROTECTED] 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:[EMAIL PROTECTED] > > > Sent: Friday, May 21, 2004 8:04 PM > > > To: [EMAIL PROTECTED] > > > Cc: [EMAIL PROTECTED] > > > 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, [EMAIL PROTECTED] wrote: > > > > Thanks Robert! > > > > > > > > I did that as well and still didn't work. Any other ideas? > > > > > > > > -----Original Message----- > > > > From: Robert Treat [mailto:[EMAIL PROTECTED] > > > > Sent: Friday, May 21, 2004 4:41 PM > > > > To: [EMAIL PROTECTED] > > > > Cc: [EMAIL PROTECTED] > > > > Subject: Re: [ADMIN] pg_hba.conf > > > > > > > > On Thu, 2004-05-20 at 19:52, [EMAIL PROTECTED] 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 ---------------------------(end of broadcast)--------------------------- TIP 9: the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match
