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

Unable to connect on W2K

From: Paul Lambert <paul(dot)lambert(at)autoledgers(dot)com(dot)au>
To: pgsql-odbc(at)postgresql(dot)org
Subject: Unable to connect on W2K
Date: 2007-02-21 03:36:44
Message-ID: 45DBBE4C.2000404@autoledgers.com.au (view raw or flat)
Thread:
Lists: pgsql-odbc
I'm having some troubles getting a connection going in W2K.

I have Postgres 8.2.3 running, ODBC driver version 8.02.02.

The server has no firewall software.

When I set up a System DSN and try to 'test' the connection, it returns 
"Could not connect to the server;
No connection could be made because the target machine refused it.
[172.17.152.207:5432]"

My pg_hba.conf file looks like this:
host    all    all      127.0.0.1/32          password
host    all    all      172.0.0.0/8           password

All servers on our network are on 172.* addresses.

The connection I am attempting is from the server itself. I've tried 
numerous alterations to the pg_hba.conf file, putting different 
addresses, CIRD masks, authentication methods etc but cannot get it to work.

The psqlodbc_1948.log file is as follows:
========================================================================
DSN info: 
DSN='AutoDRS',server='FOOTPRINTS',port='5432',dbase='AutoDRS',user='AutoDRS',passwd='xxxxx'
 
onlyread='0',protocol='7.4',showoid='0',fakeoidindex='0',showsystable='0'
           conn_settings='',conn_encoding='OTHER'
           translation_dll='',translation_option=''
Global Options: Version='08.02.0200', fetch=100, 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 NAMEDATALEN=64
                 extra_systable_prefixes='dd_;', conn_settings='' 
conn_encoding='OTHER'
CONN ERROR: func=original_CC_connect, desc='', errnum=101, errmsg='Could 
not connect to the server'
             ------------------------------------------------------------
             henv=00000000, conn=00A73D28, status=0, num_stmts=16
             sock=00A72138, stmts=00A72200, lobj_type=-999
             ---------------- Socket Info -------------------------------
             socket=-1, reverse=0, errornumber=4, errormsg='No 
connection could be made because the target machine actively refused it.
  [172.17.152.207:5432]'
             buffer_in=10971248, buffer_out=10975352
             buffer_filled_in=0, buffer_filled_out=0, buffer_read_in=0
========================================================================

And the mylog_1948.log file is as follows:
========================================================================
[1948.1776(Wed Feb 21 12:26:39 2007)]DETACHING PROCESS
[1776-0.000]globals.extra_systable_prefixes = 'dd_;'
[1776-0.000]exe name=odbcad32 plaformId=2
[1776-0.016]aszKey='DSN', value='AutoDRS'
[1776-0.016]copyAttributes: 
DSN='AutoDRS',server='',dbase='',user='',passwd='xxxxx',port='',onlyread='',protocol='',conn_settings='',disallow_premature=-1)
[1776-0.031]getDSNinfo: DSN=AutoDRS overwrite=0
[1776-0.031]rollback_on_error=1
[1776-0.031]force_abbrev=0 bde=0 cvt_null_date=0
[1776-0.031]globals.extra_systable_prefixes = 'dd_;'
[1776-0.047]calling getDSNdefaults
[1776-0.063]checking libpq library
[1776-0.094]hmodule=63100000
[1776-0.094]libpq_exist=1
[1776-0.516]GetProcAddres for GetMsdtclog
[1948.1776(Wed Feb 21 12:26:50 2007)]DETACHING PROCESS
[1776-1.469]GetProcAddres for SetMsdtclog
[1776-2.094]CC_connect: entering...
[1776-2.094]sslmode=disable
[1776-2.094]original_CC_connect: entering...
[1776-2.125]original_CC_connect: DSN = 'AutoDRS', server = 'FOOTPRINTS', 
port = '5432', database = 'AutoDRS', username = 'AutoDRS', password='xxxxx'
[1776-2.125]connecting to the server socket...
[1776-3.250]No connection could be made because the target machine 
actively refused it.
  [172.17.152.207:5432][1776-3.250](4)No connection could be made 
because the target machine actively refused it.
  [172.17.152.207:5432] ERRNO=0
[1776-3.250]CC_error_statements: self=00A73D28
[1776-3.266]CONN ERROR: func=original_CC_connect, desc='', errnum=101, 
errmsg='Could not connect to the server'
[1776-3.297]enter CC_get_error
[1776-3.297]enter CC_create_errormsg
[1776-3.297]msg = 'Could not connect to the server'
[1776-3.297]exit CC_create_errormsg
[1776-3.313]exit CC_get_error
[1776-3.797]enter CC_Destructor, self=00A73D28
[1776-3.797]in CC_Cleanup, self=00A73D28
[1776-3.797]after CC_abort
[1776-3.797]SOCK_Destructor
[1776-3.797]after SOCK destructor
[1776-3.797]exit CC_Cleanup
[1776-3.813]after CC_Cleanup
[1776-3.813]after free statement holders
[1776-3.813]exit CC_Destructor
[1776-47.344]DETACHING PROCESS
========================================================================

The server runs no firewall, no virus scanner, if I run a tcpviewer I 
can see the postgres.exe process listening on port 5432, but I never see 
any outgoing connection attempts when I try to test the connection.

Any suggestions on what might be malfunctioning?

This is just the second to last thing I need done before I can launch 
our new product and release it to our customers - who are quite eagerly 
awaiting its arrival so any assistance would be greatly appreciated.

Regards,
Paul.

-- 
Paul Lambert
Database Administrator
AutoLedgers

Responses

pgsql-odbc by date

Next:From: Ludek FinstrleDate: 2007-02-21 07:04:55
Subject: Re: Unable to connect on W2K
Previous:From: noreplyDate: 2007-02-19 19:50:18
Subject: [ psqlodbc-Bugs-1001999 ] PSQLODBC folds identifiers to lower case, causing Excel (MS Query) to fail.

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