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

Re: Problem to connect to the Windows Port

From: "Anony Mous" <A(dot)Mous(at)shaw(dot)ca>
To: "'Jan Wieck'" <JanWieck(at)Yahoo(dot)com>,"'Cornelia Boenigk'" <poppcorn(at)cornelia-boenigk(dot)de>
Cc: "'pgsql-general'" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Problem to connect to the Windows Port
Date: 2004-08-26 13:35:59
Message-ID: 00c601c48b71$9f7903d0$6902a8c0@PETER (view raw or flat)
Thread:
Lists: pgsql-general
OK, I've found what worked for me.

By default, the pg_hba file installs like so: 

# TYPE DATABASE USER IP-ADDRESS IP-MASK METHOD 
local all all trust 
# IPv4-style local connections: 
host all all 127.0.0.1 255.255.255.255 trust 
# IPv6-style local connections: 
host all all ::1 ffff:ffff:ffff:ffff:ffff:ffff:ffff:ffff trust 

Once I removed the IPv6-style line, then I could add my own IP + Mask
combination and it worked fine (in my case this is 192.168.0.0
255.255.0.0)

Perhaps upon installation the IPv6 line should be "remmed" out by default? 


-----Original Message-----
From: Anony Mous [mailto:A(dot)Mous(at)shaw(dot)ca] 
Sent: August 26, 2004 5:55 AM
To: 'Jan Wieck'; 'Cornelia Boenigk'
Cc: 'pgsql-general'
Subject: RE: Problem to connect to the Windows Port

I've been watching this thread because I am experience exactly the same
thing.  I can also repeat all the diagnostic results of Conni.  Postmaster
resides on a Win 2K box.  I can telnet to the server no problem.  My pg_hba
file line entries will allow access from all hosts, all users, all databases
on ip 192.168.0.0 with a mask of 0.0.0.0 method=trust.

Connection to the postmaster on the local machine works just fine, but I
just cannot get it to connect remotely.


-----Original Message-----
From: Jan Wieck [mailto:JanWieck(at)Yahoo(dot)com] 
Sent: August 25, 2004 8:27 PM
To: Cornelia Boenigk
Cc: pgsql-general
Subject: Re: Problem to connect to the Windows Port

On 8/25/2004 3:11 PM, Cornelia Boenigk wrote:
> Hi all
> 
>> "Connection refused" suggests that you've got a firewall-type
> problem,

Hi Conni,

Gruß aus Philadelphia

connection refused means at least that the machine responded to the 
connection attempt, but that (it pretended?) nobody is listening on the 
port.

The firewall I would set up would not respond at all, but simply drop 
the packet. So I doubt you're facing a firewall problem here. Are you 
sure that you are trying to contact the right host?


Jan

> 
> The port 5432 is open in bith directions.
> I can connect to remote databases from all machines and all OS without
> any problem. Inside the local network I can access the databases in a
> Cygwin-installation on another machine from the Windows Port but not
> vice versa.
> 
>> netstat -an and look for the row that say LISTENING on port 5432 ?
> 
> On both machines there is the line
> TCP    0.0.0.0:5432           0.0.0.0:0              LISTENING
> 
> Regards
> Conni
> 
> 
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster


-- 
#======================================================================#
# It's easier to get forgiveness for being wrong than for being right. #
# Let's break this rule - forgive me.                                  #
#================================================== JanWieck(at)Yahoo(dot)com #


Responses

pgsql-general by date

Next:From: Leonardo FrancalanciDate: 2004-08-26 13:51:04
Subject: space taken by a row & compressed data
Previous:From: Graeme HinchliffeDate: 2004-08-26 13:13:53
Subject: detecting a dead db not seeming to work

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