Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [209.114.166.2])
	by hub.org (8.9.3/8.9.3) with ESMTP id KAA80262
	for <pgsql-interfaces@hub.org>; Wed, 28 Jul 1999 10:16:03 -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 KAA09715;
	Wed, 28 Jul 1999 10:14:20 -0400 (EDT)
To: "Jonathan davis" <haj@idianet.net>
cc: "Tim Allen" <tim@proximity.com.au>, pgsql-interfaces@hub.org
Subject: Re: [INTERFACES] libpq problem (really libpq feature request) 
In-reply-to: Your message of Wed, 28 Jul 1999 12:06:03 +0200
	<000a01bed8e0$cd3aa880$0601a8c0@kosovo.idianet.net>
Date: Wed, 28 Jul 1999 10:14:20 -0400
Message-ID: <9713.933171260@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>

"Jonathan davis" <haj@idianet.net> writes:
> the postgresql client is running under win98 and the server under FreeBSD3.1
> when I'm trying to connect to the server and the server is not running, the
> error message is:
> connectDB() -- socket() failed:
> errno=0
> No error
> and when the password is incorrect, i have the same error
> it is no way to difference the errors !!!

That's because they are the same error --- if the socket() call is
failing then the client is not getting as far as attempting to contact
the server, let alone checking the password.  I do not know why you
are not getting a useful errno value; probably another deficiency of
the Windoze socket code :-(.  But I'd suggest looking at whether
TCP support is turned on, whether there is a problem linking the socket
support library into the application, etc.  Any Win experts here with
an idea what could make socket() fail?

			regards, tom lane