Bugs item #1000414, was opened at 2005-11-07 21:59
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000414&group_id=1000125
Category: None
Group: None
>Status: Closed
Resolution: None
Priority: 3
Submitted By: Nobody (None)
Assigned to: Nobody (None)
Summary: file based dns does not connect
Initial Comment:
Hiho
I just tried the combination of
8.1.100 => 8.0.4debian
and
8.1.100 => 8.1win
Im unable to connect by mean of a file based dns entry.
I just get the error "could not connect to the server (#113)
Using the computer-dns with the same connection options works really well.
Unable to find a configuration fault. Also using pgadmin or jdbc3 as client
works proper.
hth
Cybernd aka Neuhauser Bernhard
----------------------------------------------------------------------
>Comment By: Dave Page (dpage)
Date: 2005-11-24 14:24
Message:
This occurs when the File DSN is being created, if it cannot be verified.
Elements of the connect string are generated only after the connection has been
made, so if you don't fully connect, only the 'Driver={PostgreSQL xxx}' section
is written to the file DSN.
To create usable DSNs, when prompted to enter the server details, make sure
that all details required to connect are entered and that the server is
configured to allow the incoming connection. The file DSN will then be saved
with all required parameters *except* the password.
----------------------------------------------------------------------
Comment By: Nobody (None)
Date: 2005-11-15 11:43
Message:
Just tried the 8.1.101 odbc driver.
The error message changed to "fe_sendauth: no password supplied (#113)"
Still it works proper with user/system based dns. File based DNS seem to fail
(Access 2003 used as Client)
hth
Neuhauser Bernhard
----------------------------------------------------------------------
You can respond by visiting:
http://pgfoundry.org/tracker/?func=detail&atid=538&aid=1000414&group_id=1000125
---------------------------(end of broadcast)---------------------------
TIP 9: In versions below 8.0, the planner will ignore your desire to
choose an index scan if your joining column's datatypes do not
match
|
Try Searching:
servers, voip, java, networking, microsoft ...
|
|
|
|