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

Re: Basic ODBC Connect Problem

From: "Henshall, Stuart - WCP" <SHenshall(at)westcountrypublications(dot)co(dot)uk>
To: "'Stuart'" <stuart(at)theallisons(dot)freeserve(dot)co(dot)uk>, pgsql-odbc(at)postgresql(dot)org
Subject: Re: Basic ODBC Connect Problem
Date: 2002-01-08 16:23:34
Message-ID: E2870D8CE1CCD311BAF50008C71EDE8E01F74774@MAIL_EXCHANGE (view raw or flat)
Thread:
Lists: pgsql-odbc
Try a port scanning utility (I think multiscan is available on sourceforge).
Also in postgresql.conf (in the data directory) try:
tcpip_socket = True
Antoher possibility is the pg_hba file isn't properly set up. Having a
pg_hba.conf of this:
host  all  0.0.0.0  0.0.0.0  password
will allow anyone to connect from anywhere using a password.
Hope this helps
- Stuart


-----Original Message-----
From: Stuart [mailto:stuart(at)theallisons(dot)freeserve(dot)co(dot)uk]
Sent: 06 January 2002 16:28
To: pgsql-odbc(at)postgresql(dot)org
Subject: Basic ODBC Connect Problem


Hi
 
Apologies for a rather basic query:
 
Having stripped out my old SuSE 6.2 and replaced this with SuSE 7.3 (note
everything was reformatted), I now cannot connect to my newly created
database via ODBC from Paradox.
 
ODBC version: 07_01_0008
PostgreSQL version 7.1.3 (as installed from SuSE 7.3)
 
Windows psqlodbc log file shows:
 
Global Options: Version='07.01.0008', fetch=1, socket=4096, unknown_sizes=0,
max_varchar_size=254, max_longvarchar_size=8190

disable_optimizer=1, ksqo=1, unique_index=1, use_declarefetch=0

text_as_longvarchar=1, unknowns_as_longvarchar=0, bools_as_char=1

extra_systable_prefixes='dd_;', conn_settings='' conn_encoding='OTHER'

CONN ERROR: func=PGAPI_DriverConnect, desc='Error from CC_Connect',
errnum=101, errmsg='Could not connect to the server'

------------------------------------------------------------

henv=92802928, conn=91701824, status=0, num_stmts=16

sock=92802880, stmts=92802800, lobj_type=-999

---------------- Socket Info -------------------------------

socket=-1, reverse=0, errornumber=4, errormsg='Could not connect to remote
socket.'

buffer_in=91712708, buffer_out=91716808

buffer_filled_in=0, buffer_filled_out=0, buffer_read_in=0

 
 
How can I check the remote socket? The postmaster has been started with the
'-i' option. 
Is/will there be a PAM issue here as well, which is/will reject the
connection? I haven't figured out PAM yet and can't ftp or telnet (at least
in SuSE 6.2 I got telnet to work!)
 
Thanks for ANY help on this rather basic issue.
 
Stuart

Responses

pgsql-odbc by date

Next:From: Henshall, Stuart - WCPDate: 2002-01-08 16:33:11
Subject: Re: Sending lot of records
Previous:From: Hiroshi InoueDate: 2002-01-08 02:20:30
Subject: Re: Problem with view and fetch_fields

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