Message-ID: <3984F5B5.DCE92A11@mascari.com>
Date: Sun, 30 Jul 2000 23:42:45 -0400
From: Mike Mascari <mascarm@mascari.com>
Organization: Mascari Development Inc
MIME-Version: 1.0
To: Red Pineseed <yue207@home.com>
CC: David Lloyd-Jones <david.lloyd-jones@attcanada.ca>,
	pgsql-interfaces@postgresql.org
Subject: Re: PSQL Working, but PGAccess Not Connecting.
References: <200007301621.SAA02908@beertje.william.bogus>
	<000601bffa64$a38bb960$46647bd8@WORKGROUP>
	<1655.964993215@sss.pgh.pa.us>
	<000701bffa74$88159790$406c7bd8@WORKGROUP>
	<7628.964996485@sss.pgh.pa.us> <3984DC50.BF5B2D2D@home.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Red Pineseed wrote:
> 
> It looks like you don't have the user permission set up
> properly. Here is a jpg much like what you have descrbibed
> in the message. What the postmaster is not running in the
> background or the user permission is not set properly, you
> get a message like that.
> 
> use the createuser command to create user and set proper
> permision and connect the db like.
> 
> Philip

Except that there's a difference between "Connection refused",
which is typical of the postmaster not being started with the -i
option, and "Network unreachable", which is typical of a TCP/IP
application where the kernel cannot resolve the route to the
destination host. The user never did specify the success/failure
of testing loop-back via telnet on 127.0.0.1. My bet is it didn't
work. My money's on Tom Lane.

Mike Mascari