Your best bet is to look in the log files, to see why postgresql doesn't
start up. Now I have no clue where you would find them on windows, but..
that's where I would look.
On Tue, 2004-08-24 at 10:12, Secrétariat wrote:
> I already receive 8 times this message, not responding to my question !
> The question is :
> Why when I enable "tcpip_socket = true" in the postgresql.conf it becomes
> impossible to restart the service ?! (so hosts conections are impossible).
> Secrétariat wrote:
> > Hello !
> > I've corrected my win32 pg_hba.conf, it contains :
> > host all all 127.0.0.1 255.255.255.255 md5
> > host all all 192.168.0.0 255.255.255.0 md5
> > but I can't connect from my W2k client at IP 192.168.0.11 !
> Open a command-prompt on the client and try to telnet to your server,
> port 5432.
> Type "aa" and hit return - you should get an error message complaining
> about a bad "startup packet".
> Do the same from the server to the external IP address and then 127.0.0.1
> If none of these work, then PG probably isn't listening. If 127.0.0.1
> works but one or more of the others don't then check your firewall.
519 939 0336
ICQ # 14675561
In response to
pgsql-general by date
|Next:||From: mike||Date: 2004-08-24 14:42:53|
|Subject: Invalid input for integer on VIEW|
|Previous:||From: Richard Huxton||Date: 2004-08-24 14:37:56|
|Subject: Re: No connection to a PG 8.0 Beta 1 win32 server|