Skip site navigation (1) Skip section navigation (2)

Re: Problem to connect to the Windows Port

From: Doug McNaught <doug(at)mcnaught(dot)org>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Cornelia Boenigk" <poppcorn(at)cornelia-boenigk(dot)de>,"Magnus Hagander" <mha(at)sollentuna(dot)net>,"pgsql-general" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Problem to connect to the Windows Port
Date: 2004-08-24 21:15:23
Message-ID: 87n00k1bmc.fsf@asmodeus.mcnaught.org (view raw or flat)
Thread:
Lists: pgsql-general
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> "Cornelia Boenigk" <poppcorn(at)cornelia-boenigk(dot)de> writes:
>> C:\>psql -h 192.168.1.8 -U postgres -d minitest
>> psql: could not connect to server: Connection refused
>>         Is the server running on host "192.168.1.8" and accepting
>>         TCP/IP connections on port 5432?
>
> "Connection refused" suggests that you've got a firewall-type problem,
> ie the operating system is rejecting the connection rather than letting
> the postmaster receive it.  Check packet filtering rules...

It's also possible that the postmaster is listening on a port other
than 5342...

-Doug
-- 
Let us cross over the river, and rest under the shade of the trees.
   --T. J. Jackson, 1863

In response to

pgsql-general by date

Next:From: Frank van VugtDate: 2004-08-24 21:16:37
Subject: NAB : insert into <table> select distinct <fields> => when used on null, distinct causes loss of type knowledge
Previous:From: Peter EisentrautDate: 2004-08-24 21:09:44
Subject: Re: Is this legal SQL? Is it a good practice?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group