FreeTDS Development Group

["Gil Darves" <gil AT darves.net>]

I apologize, I am able to connect now using the NT account.

 

However, I am still curious why the bourne osql utility is failing.

 

Also, any prior discussions (links) related to benefits of ODBC-combined
configuration versus ODBC-only? Along this line, any discussions regarding
best practices related to setting up DSN in a multiple-user environment
without a gui? Can a Global DSN be contemplated? Or should each user use the
odbcinst utility?

 

Again, Thank you.

Gil Darves

 

From: Gil Darves [mailto:gil AT darves.net] 
Sent: Monday, July 13, 2009 12:12 PM
To: 'freetds AT lists.ibiblio.org'
Subject: NT Authentication Failing for an ODBC-Only Configuration

 

Hello,

 

I am able to connect to a SQLServer 2008 database using SQL Authentication
but am receiving a SQLConnect error when attemping a domain\username
connection for an ODBC-Only Configuration.

 

Here is the sequence.

 

1.       I implemented an installation on a Red Hat Enterprise Linux Server
release 5.2 (Tikanga) by following Peter Harvey's "How to use unixODBC with
FreeTDS".

2.       I have not configured the /usr/local/etc/freetds.conf configuration
file.

3.       I am able to connect using NT Authenticaion using FreeTDS tsql
utility

tsql -H 10.7.22.22 -p 1433 -U 'domain\gdarves'

4.       I am able to connect using isql using sql account

isql MSSQLTestServer gdarves mypassword

5.       But when I attempt the following

Isql MSSQLTestServer domain\gdarves mypassword

                                       'domain\gdarves' mypassword

                                     "domain\gdarves" mypassword

 

The message [ISQL] ERROR: Could not SQLConnect

 

 

Here is my odbcinst.ini configuration file located at /usr/local/etc

 

[FreeTDS]

Description     = freetds v0.82

Driver      = /usr/local/lib/libtdsodbc.so

UsageCount      = 2

 

Here is my .odbc.ini config file located in my home directory

 

[MSSQLTestServer]

Driver      = FreeTDS

Description     = zGilSandbox

Trace       = No

Server      = 10.7.22.22

Port        = 1433

Database        = zGilSandbox

 

Here is my compile-time configuration parameters

gild (dev) bin: tsql -C

Compile-time settings (established with the "configure" script)  Version:
freetds v0.82

 freetds.conf directory: /usr/local/etc

 MS db-lib source compatibility: no

 Sybase binary compatibility: no

 Thread safety: yes

  iconv library: yes

 TDS version: 8.0

  iODBC: no

 unixodbc: yes

 

 

I attempted to diagnose using the osql utility. Here is the output:

 

gild (dev) ~: osql -S MSSQLTestServer -U 'dm\gdarves' -P mypassword!

looking for odbc.ini and odbcinst.ini in /usr/local/etc

        reading "/home/v-gil.darves/.odbc.ini"

[MSSQLTestServer] found in "/home/v-gil.darves/.odbc.ini"

found this section:

        [MSSQLTestServer]

        Driver          = FreeTDS

        Description             = zGilSandbox

        Trace           = No

        Server          = 10.7.22.22

        Port            = 1433

        Database                = zGilSandbox

 

looking for driver for DSN [MSSQLTestServer]

driver "FreeTDS" found for [MSSQLTestServer] in .odbc.ini

found driver named "FreeTDS"

FreeTDS is not a readable file

looking for entry named [FreeTDS] in /usr/local/etc/odbcinst.ini

driver "/usr/local/lib/libtdsodbc.so" found for [FreeTDS] in odbcinst.ini

/usr/local/lib/libtdsodbc.so is a readable file

"Server" found, not using freetds.conf

FreeTDS servername is "10.7.22.22"

10.7.22.22 has address Host 22.22.7.10.in-addr.arpa not found: 3(NXDOMAIN)

 

 DSN: MSSQLTestServer

 Server's hostname: 10.7.22.22

                       Address: Host

       22.22.7.10.in-addr.arpa: not

                        found:: 3(NXDOMAIN)

                        Driver: /usr/local/lib/libtdsodbc.so

 

Attempting connection as dm\gdarves...

[S1000][unixODBC][FreeTDS][SQL Server]Unable to connect to data source

[37000][unixODBC][FreeTDS][SQL Server]Login failed. The login is from an
untrusted domain and cannot be used with Windows authentication.

[ISQL]ERROR: Could not SQLConnect

 

 

Note: the osql utility fails when I use the sql authenticated account as
well!!!. Same message about in-addr.arpa not found.

 

Please advise.

 

Thank you,

Gil Darves