| From: | "Tahira Aslam" <taslam(at)etrisoft(dot)net> |
|---|---|
| To: | "pgsql-admin" <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Could not connect to remote socket |
| Date: | 2002-07-29 10:31:13 |
| Message-ID: | 006101c236eb$1ae4ec60$1b00a8c0@trisoft.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
I have my postgresql DB on linux machine. and i have 2 windows clients for this DB.Things were working fine until this morning when client machines started giving error
Could not connect to server
Could not connect to remote socket
I have taken care of each thing like
1) Starting postmaster with -i option
2) pgaccess is running successfully
3) windows client machines can ping server.
4) windows client machines can access server's shared folders through samba services
5) pg_hba.conf file has 2 entries for my clients
6) i have uncommeted tcpip_socket=false in /var/lib/pgsql/data/postgresql.conf file and set it to true.
what else should i do to connect my windows clients machines with my linux server ??
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Sullivan | 2002-07-29 12:44:13 | Re: log sql? |
| Previous Message | Gaetano Mendola | 2002-07-29 08:21:55 | Re: cpu_tuple_cost WRONG -> After an "analyze" or "vacuum full" indexes are not used anymore!!! |