| From: | "Nicolas Gignac" <gignacnic(at)gmail(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Client connection: Port 5432 / Postgres |
| Date: | 2007-02-09 01:01:01 |
| Message-ID: | 172264ae0702081701g74095ca3jfae8a467abf22fc7@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Thanks. Finally, I discovered one line not uncomment, stupid typos error.
Nicolas
2007/2/7, Nicolas Gignac <gignacnic(at)gmail(dot)com>:
>
> Hello,
>
> I have installed Postgres 8.2 on a internal server having Windows Server
> 2003 (IIS 6) up and running.
> - I have configure the hp_config file to: host
> all 0.0.0.0./0
> md5
> - I have change the listening address to '*' in the postgres.conf file
> - No Firewall activated on this internal server
> - I have restart the server and I can connect to postgres from remote
> computer, PostgreSQL works only from the local host
> - When I do a Netstat I got this: TCP 127.0.0.0.1:5432
> 0.0.0.0.0 LISTENING 440
> - When I tried to connect from local host to the port with telnet
> localhost 5432, I got an error: on port 23, connect failed.
>
> What are the options/ways to allow connection by PostgreSQL remote Clients
> to the 5432 port on my server in this internal network? Or is there any
> problem with my steps, something I missed?
>
> Thanks for your help.
>
> Nicolas Gignac
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Chad Wagner | 2007-02-09 01:22:40 | Re: Move data between two databases SQL-ASCII to UTF8 |
| Previous Message | Dean Grubb | 2007-02-09 00:49:59 | Headache with a plpgsql function |