FreeTDS Development Group

[Samuel Bayer <sam AT mitre.org>]

Samuel Bayer wrote:

> Victory, of a sort. It worked - once. I did a clean checkout, "make",
> "make install", and then the installed version allowed me to connect to
> the DB - but I'd installed on top of a previous build from last week's
> checkout. THAT worked. As soon as I removed the previous install and did
> a clean "make install", it failed in the same way it did previously.
>
> I'm mystified, to say the least. I can't reconstruct what I might have
> done to get it to work in that one case.
>
> But we're getting SOMEwhere. I'm going to go try this on Linux and see
> what happens.
>
> Thanks again -
> Sam Bayer

And I have my answer. I was experimenting with the Python ODBC bindings, 
and I was omitting my password, and the connection was failing 
(obviously), and eventually my administrator locked me out of the 
Windows domain because my password had been wrong too many times. I've 
done a clean build from source and confirmed that this was the problem. 
I can now contact my server reliably.

For the record, here's my configuration:

Dual-processor, dual-core Intel Mac Pro, 7GB of memory
MacOS X 10.6.5
Python 2.6
Apple-provided iODBC manager
SQL Server 2008 RTM, authenticating via NTLMv2 ONLY

freetds.conf entry:

[<configname>]
        tds version = 8.0
        use ntlmv2 = yes
        host = <hostname>
        port = 1433

Contents of /Library/ODBC/odbcinst.ini:

[ODBC Drivers]
FreeTDS = Installed

[FreeTDS]
Driver = <installdir>/lib/libtdsodbc.0.so
Setup  =

pyodbc connection string:

"DRIVER=FreeTDS;SERVERNAME=<configname>;DATABASE=<dbname>;UID=<user>;PWD=<password>"

where <configname>, <hostname>, <dbname>, <installdir>, <user> and 
<password> are the appropriate values.

Thanks for your help.

Sam  Bayer