Hi Mir,
thanks for your quick answer. We will try this.
For my unterstanding: Why should i use
trust instead of
md5 ? A configuration at another customer (with a
domain setting) using
md5 works fine ?
mit freundlichen Grüßen / best regards,
Josef Springer
(Geschäftsleitung/Management)
| -- the software company --
|
Shoaib Mir wrote:
I can understand the exact error as its not in english :) but it seems like an authentication problem. Please change 'md5' to 'trust' in pg_hba.conf file and then use:
pg_ctl -D <path to data folder> reload
That will reload the settings for authentication.
Now once the settings are reloaded try reconnecting to the database and it should go fine this time....
----------------
Shoaib Mir
EnterpriseDB ( www.enterprisedb.com )
On 1/15/07, Josef Springer <Josef.Springer@joops.com > wrote: Hi folks,
i have a workgroup (not a classic server) with Windows-XP-machines:
the database server machine contains the line
host all all 0.0.0.0 0.0.0.0 md5 in the file pg_hba.conf
and
listen_addresses = '*' in the file postgresql.conf.
The clients' host file contain the line
nnn.nnn.nnn.nnn Labor where nnn.nnn.nnn.nnnn is the IP-adress of
the database server machine and /Labor /is the machine's name.
If i start PGAdmin III on the 'client' machine i can not connect to
the database on the machine Labor no matter wether i use the machine's name
or the IP-adress. Instead i get the message
"Zum Server ist keine Verbindung möglich,
oder Login/Passwort sind falsch.
Die Anmeldung wurde abgelehnt."
Please help me. What to do ?
mit freundlichen Grüßen / best regards,
Josef Springer
(Geschäftsleitung/Management)
| -- the software company --
|