Re: SQLConnect failure

From: greg(at)bryantrecording(dot)com
To: pgsql-general(at)postgresql(dot)org
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: SQLConnect failure
Date: 2007-04-02 22:38:58
Message-ID: 20070402153858.9e7bc6c5a28434177d7b431073d619b9.35ad08669f.wbe@email.secureserver.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

> -------- Original Message --------
> Subject: Re: [GENERAL] SQLConnect failure
> From: Bill Moran <wmoran(at)potentialtech(dot)com>
> Date: Mon, April 02, 2007 2:54 pm
> To: greg(at)bryantrecording(dot)com
> Cc: pgsql-general(at)postgresql(dot)org
>
> In response to greg(at)bryantrecording(dot)com:
>
> > We have code that has been using MSDE/SQL Server successfully for
> years,
> > and are adding Postgres support. Doing a SQLConnect to connect to a
> > local Postgres server works fine, but if we try to connect to a remote
> > system, the SQLConnect fails, and we get an error code that seems to
> > indicate "The value specified for the argument UserName or the value
> > specified for the argument Authentication violated restrictions defined
> > by the data source.".
> >
> > We can connect via pgadmin to the remote system, so we believe all the
> > little .conf files should be correct, but can't get in
> > programmatically. Any pointers on where to look?
>
> The logs on the PostgreSQL server would be a good place to start.
>
> This sounds suspiciously like a pg_hba.conf misconfig. You might want
> to verify its correctness.
>

Thanks guys. I can connect to the remote server via pgadmin on a
different machine, so I'm pretty sure that the .conf files are correct
(that took awhile, but there are very good diagnostic messages when
they are wrong). When I set the hba, the encryption is set to MD5 -
does that need to be set somewhere on the client side?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Raymond O'Donnell 2007-04-02 23:22:12 Re: Working between Windows and Unix
Previous Message Bill Moran 2007-04-02 21:54:53 Re: SQLConnect failure