Skip site navigation (1) Skip section navigation (2)

Re: Authentication problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com>
Cc: "'pgsql-novice(at)postgresql(dot)org'" <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Authentication problem
Date: 2005-04-18 19:44:45
Message-ID: 25091.1113853485@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-novice
"Walker, Jed S" <Jed_Walker(at)cable(dot)comcast(dot)com> writes:
> I have the postgresql.conf listen_addresses='*'
> and in pg_hba.conf I have
> host   VRNJED    all      2.30.0.0   255.255.0.0    md5

That looks fine ...

> I have three clients on Windows PCs each on a different subnet (2.30.50,
> 2.30.190, 2.30.31). One of them connects just fine, the password is asked
> for and the logon succeeds, but the other two get

> C:\dev\PostgreSQL>psql -h robux -d VRNJED -U vrngui
> psql: FATAL:  password authentication failed for user "vrngui"

> I'm not sure why these two fail when the others work.

Odd.  One possibility is that the postmaster isn't using the pg_hba.conf
file you think it is (did you signal it to reload its configuration, or
else stop and restart it, after editing the file?).  Another idea that
comes to mind is some sort of packet filtering at the network or OS
level ... though I'm not sure how packet filtering could cause this
particular error message.

			regards, tom lane

In response to

pgsql-novice by date

Next:From: Walker, Jed SDate: 2005-04-18 20:09:45
Subject: Re: Authentication problem
Previous:From: tövisDate: 2005-04-18 19:11:24
Subject: characters with accent

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group