Re: ODBC and unknown i.p.
| От | Michael Weaver | 
|---|---|
| Тема | Re: ODBC and unknown i.p. | 
| Дата | |
| Msg-id | 3B663B41B350D311AEEF00A0C9254563201A6D@VISION1 обсуждение исходный текст | 
| Ответ на | ODBC and unknown i.p. (Mike Alford <mikea@syscon-intl.com>) | 
| Ответы | Re: ODBC and unknown i.p. | 
| Список | pgsql-admin | 
Mike,
Have you tried adding an entry for the entire Internet?
eg: IP: 127.0.0.1(could be anything) Mask: 0.0.0.0
Mike.(also)
> -----Original Message-----
> From: Mike Alford [mailto:mikea@syscon-intl.com]
> Sent: Monday, 10 February 2003 9:44 PM
> To: pgsql-admin@postgresql.org
> Subject: [ADMIN] ODBC and unknown i.p.
> 
> 
> I am using postgres 7.3.1 on a slackware linux server and psqlodbc.exe
> version 07.02.0005. I am a novice at both linux and postgres
> administration.  We are in the process of converting from a 
> SCO unix server
> with Ingres1.2 database to the aforementioned linux/postgres 
> server. Our
> application is distributed to customers around the world and uses ODBC
> connections in VB applications. With our old system, we only 
> had to be able
> to connect to the database server through ODBC and 
> user/password security.
> It appears that there is another level with postgres--namely 
> the addition
> of entries into pg_hba.conf, which include the i.p.and 
> subnet. Since this
> is a distributed application, we have no way to know in 
> advance what the ip
> and subnet of users at a given site will be, much less when a customer
> changes his local network. I tried a VB app without an entry 
> in pg_hba.conf
> and failed, but succeed when the entry is added.
> 
> Is there an easy way around the pg_hba.conf problem? If not, 
> has anyone who
> has dealt with this issue have any suggestions? 
> Do not try to solve all life's problems at once -- learn to dread each
> day as it comes.
> 
> 
> ---------------------------(end of 
> broadcast)---------------------------
> TIP 5: Have you checked our extensive FAQ?
> 
> http://www.postgresql.org/users-lounge/docs/faq.html
> 
		
	
В списке pgsql-admin по дате отправления: