Received: from tor-smtp1.netcom.ca (tor-smtp1.netcom.ca [207.181.101.69]) by hub.org (8.10.1/8.10.1) with ESMTP id e6UMFwB99836 for ; Sun, 30 Jul 2000 18:15:58 -0400 (EDT) Received: from widgette (trt-on69-64.netcom.ca [216.123.108.64]) by tor-smtp1.netcom.ca (8.8.7-s-4/8.8.7) with SMTP id SAA26335; Sun, 30 Jul 2000 18:14:59 -0400 (EDT) Message-ID: <000701bffa74$88159790$406c7bd8@WORKGROUP> From: "David Lloyd-Jones" To: "David Lloyd-Jones" , "Tom Lane" Cc: References: <200007301621.SAA02908@beertje.william.bogus> <000601bffa64$a38bb960$46647bd8@WORKGROUP> <1655.964993215@sss.pgh.pa.us> Subject: Re: PSQL Working, but PGAccess Not Connecting. Date: Sun, 30 Jul 2000 18:21:27 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.50.4133.2400 X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400 X-Archive-Number: 200007/205 "Tom Lane" writes > "David Lloyd-Jones" writes: > > PGAccess, the GUI, refuses to open it. The open command gives me the error > > message "Connection to database failed connect DBStart() -- connect() > > failed: network is unreachable > ^^^^^^^^^^^^^^^^^^^^^^ > Your networking configuration is broken: the kernel does not believe it > can contact itself. I can't give you much help about specific fixes, > but until you can do local loopback (such as "telnet 127.0.0.1") you > won't have any luck contacting the postmaster via TCP --- which is > what PGAccess wants to do. > > I'd suggest reading some basic networking HOWTOs ... > Tom, Thanks for your note. Not to be ungracious, (RTFM would always be good advice, were it not for the fact that manuals are written at greater speed than one can read them) but I don't see how this adds up: I'm not on a network, and PSQL, which is a front end to PostgreSQL, just like PGAccess is supposed to be, is running fine. Let me rephrase the question this way: since PSQL works, why wouldn't PGAccess? Cheers, -dlj.