Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6])
	by hub.org (8.9.2/8.9.1) with ESMTP id LAA90450
	for <pgsql-interfaces@postgreSQL.org>;
	Sun, 11 Apr 1999 11:39:34 -0400 (EDT)
	(envelope-from tgl@sss.pgh.pa.us)
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.9.1/8.9.1) with ESMTP id LAA12539;
	Sun, 11 Apr 1999 11:38:52 -0400 (EDT)
To: Joe Dieckert <dieckert@cabnet.net>
cc: "pgsql-interfaces@postgreSQL.org" <pgsql-interfaces@postgreSQL.org>
Subject: Re: [INTERFACES] cant connect 
In-reply-to: Your message of Sun, 11 Apr 1999 09:58:09 -0700
	<3710D4A0.2966128A@cabnet.net>
Date: Sun, 11 Apr 1999 11:38:52 -0400
Message-ID: <12537.923845132@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

Joe Dieckert <dieckert@cabnet.net> writes:
> The backend start okay and we can access the data on the local machine
> runing psql but cannont on another machine on the same net.  We tried
> adding PAM modules and adding the tcp port to the services files.  We
> tried to log in as many different users but it just keeps telling us on
> the remote and local machine that authenication has failed.

Sounds like the pg_hba.conf file on the server machine is not set up
to allow access from anywhere except that same machine.  It has to
contain an entry matching the IP address of the machine you want to
connect from.  See the administrator documentation, or check the
archives of this list --- I recall the same problem being discussed
just a week or two back.

			regards, tom lane