Thread: MS Access error "could not connect to remote socket"

MS Access error "could not connect to remote socket"

From
"chor kim seng"
Date:
dear sir,
 
i'm trying to set up a win2k client to connect to postgreSQL running on redhat 7.2.
but every time i try to connect MS Access, the error pops up. error:
"ODBC --call failed.
could not connect to server;
could not connect to remote socket."
 
i've checked that firewall on redhat 7.2 was disable via lokkit.
i've created root as a postgreSQL user.
i've aslo allow host ip win2k to access postgreSQL. 
i've used the latest ODBC driver for postgreSQL
i use root account to connect MS Access to postgreSQL.
 
win2k can ping and see redhat on the network browser.
win2k can also access the shared samba files.
 
i've tried to connect to MySQL but also can't connect.
error:
host 192.168.100.110 not allow to connect to this MySQL server.
 
pls help me. thanks!
 
 

Re: MS Access error "could not connect to remote socket"

From
Richard Huxton
Date:
On Friday 12 March 2004 07:08, chor kim seng wrote:
> dear sir,
>
> i'm trying to set up a win2k client to connect to postgreSQL running on
> redhat 7.2. but every time i try to connect MS Access, the error pops up.
> error: "ODBC --call failed.
> could not connect to server;
> could not connect to remote socket."
>
> i've checked that firewall on redhat 7.2 was disable via lokkit.
> i've created root as a postgreSQL user.
> i've aslo allow host ip win2k to access postgreSQL.
> i've used the latest ODBC driver for postgreSQL
> i use root account to connect MS Access to postgreSQL.

You don't need root as a PostgreSQL user, but you've taken most of the obvious
steps.

One thing to try is open up a command-prompt and type something like:
  telnet 192.168.1.2:5432
Where 192.168.1.2 is the IP address of your PostgreSQL machine. Type a few
characters and hit return once or twice and you should get an error message
back from PG saying connection refused.

If you can't connect using telnet, then either:
  1. The firewall is still there
  2. PG isn't listening on socket 5432
Check your postgresql.conf file and make sure you are accepting tcp/ip
connections. Also check your settings in pg_hba.conf

Hope that gets you started - reply back to the list if you still have
problems.

--
  Richard Huxton
  Archonet Ltd