Skip to Content.
Sympa Menu

freetds - Re: FreeTDS woes..

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: Jez Humble <jez AT whatsonwhen.com>
  • To: 'TDS Development Group' <freetds AT franklin.oit.unc.edu>
  • Subject: Re: FreeTDS woes..
  • Date: Wed, 5 Dec 2001 11:30:51 -0000


Now here's one I _am_ sure about. You can make SQL Server work with mixed
authentication, so it won't mess up people who are already using NT
authentication, and it will let you use FreeTDS as well. You just need to
convince your sysadmin it's not a security hole (which it isn't if set up
properly)...

-----Original Message-----
From: Casey Allen Shobe [mailto:cshobe AT secureworks.net]
Sent: 05 December 2001 01:31
To: TDS Development Group
Subject: [freetds] Re: FreeTDS woes..


Damn...is this a systemwide setting on the SQL server? I don't have direct
access to it, and doubt that setting can be changed because the client
software that the entire company uses may rely upon how it's set up now.

- Casey

On 4 December 2001 22:24, Brian Bruns spaketh unto ye recipient:
> Bingo! I was suspecting this, but didn't want to jump to conclusions.
> Your SQL Server is set up in 'Windows NT Authentication' sometimes called
> 'Domain Authentication'. This needs to be changed to 'SQL Server' or
> 'Standard' authentication.
>
> From SQL Server Enterprise Manager (SQL Server 7, not sure how different
> 2000 is), navigate to the server, right mouse click and select
> 'Properties'. Flip to the 'Security' tab and change the Authentication
> field to 'SQL Server and Windows NT', apply your changes and be happy.
>
> Brian
>
> On Tue, 4 Dec 2001, Casey Allen Shobe wrote:
> > I really appreciate your help...here's the dump:
> >
> > cshobe@sliver:/tmp$ cat freetds.log
> > 2001-12-04 22:16:01 Connecting addr 192.168.24.6 port 1433
> > 2001-12-04 22:16:01 inside tds_process_login_tokens()
> > Received packet @ 2001-12-04 22:16:01
> > 0000 aa dc 00 14 48 00 00 01 0e 68 00 4c 00 6f 00 67
> > |....H....h.L.o.g| 0010 00 69 00 6e 00 20 00 66 00 61 00 69 00 6c 00 65

> > |.i.n. .f.a.i.l.e| 0020 00 64 00 20 00 66 00 6f 00 72 00 20 00 75 00
73
> > |.d. .f.o.r. .u.s| 0030 00 65 00 72 00 20 00 27 00 53 00 45 00 43 00
> > 55 |.e.r. .'.S.E.C.U| 0040 00 52 00 45 00 57 00 4f 00 52 00 4b 00 53
> > 00 5c |.R.E.W.O.R.K.S.\| 0050 00 63 00 73 00 68 00 6f 00 62 00 65 00
> > 27 00 2e |.c.s.h.o.b.e.'..| 0060 00 20 00 52 00 65 00 61 00 73 00 6f
> > 00 6e 00 3a |. .R.e.a.s.o.n.:| 0070 00 20 00 4e 00 6f 00 74 00 20 00
> > 61 00 73 00 73 |. .N.o.t. .a.s.s| 0080 00 6f 00 63 00 69 00 61 00 74
> > 00 65 00 64 00 20 |.o.c.i.a.t.e.d. | 0090 00 77 00 69 00 74 00 68 00
> > 20 00 61 00 20 00 74 |.w.i.t.h. .a. .t| 00a0 00 72 00 75 00 73 00 74
> > 00 65 00 64 00 20 00 53 |.r.u.s.t.e.d. .S| 00b0 00 51 00 4c 00 20 00
> > 53 00 65 00 72 00 76 00 65 |.Q.L. .S.e.r.v.e| 00c0 00 72 00 20 00 63
> > 00 6f 00 6e 00 6e 00 65 00 63 |.r. .c.o.n.n.e.c| 00d0 00 74 00 69 00
> > 6f 00 6e 00 2e 00 00 00 00 00 fd |.t.i.o.n........| 00e0 02 00 00 00
> > 00 00 00 00 |........|
> >
> >
> > 2001-12-04 22:16:01 inside tds_process_default_tokens() marker is aa
> > 2001-12-04 22:16:01 Msg 18452, Level 14, State 1, Server , Line 0
> > Login failed for user 'SECUREWORKS\cshobe'. Reason: Not associated with
a
> > trusted SQL Server connection.
> > 2001-12-04 22:16:01 inside tds_process_default_tokens() marker is fd
> > 2001-12-04 22:16:01 leaving tds_process_login_tokens() returning 0
> >
> > On 4 December 2001 17:56, Brian Bruns spaketh unto ye recipient:
> > > Well it got further. set the TDSDUMP variable and run:
> > >
> > > export TDSDUMP=/tmp/freetds.log
> > >
> > > and then run and post the log file (please remove your
> > > username/password if they are important).
> > >
> > > Brian
> > >
> > > On Tue, 4 Dec 2001, Casey Allen Shobe wrote:
> > > > Added to odbe.ini under [pivotal]:
> > > >
> > > > Servername = pivotal
> > > >
> > > > Added to freetds.conf:
> > > > [pivotal]
> > > > host = 192.168.24.6
> > > > port = 1433
> > > > tds version = 7.0
> > > >
> > > > Now the script generates:
> > > >
> > > > Warning: SQL error: tds_connect failed, SQL state 08001 in
SQLConnect
> > > > in test.php...
> > > >
> > > > - Casey
> > > >
> > > > On 4 December 2001 17:08, Brian Bruns spaketh unto ye recipient:
> > > > > You need a entry in the odbc.ini file (under the pivotal section)
> > > > >
> > > > > [pivotal]
> > > > > ...
> > > > > Servername = <yourservername>
> > > > > ...
> > > > >
> > > > > Where <yourservername> is the server alias listed in your
> > > > > freetds.conf file. I would highly recommend grabbing sqsh
> > > > > (www.sqsh.org) and building it to make sure your freetds install
> > > > > and freetds.conf file are correct.
> > > > >
> > > > > This was discussed about a week ago on the list and a change was
> > > > > checked in then to say 'Servername' instead of 'Database'. i.e.
> > > > > There's an error in the error message. :-/
> > > > >
> > > > > Cheers,
> > > > >
> > > > > Brian
> > > > >
> > > > > P.S. Is it just me, or has there been a whole rash of ODBC
> > > > > questions lately?
> > > > >
> > > > > On Tue, 4 Dec 2001, Casey Allen Shobe wrote:
> > > > > > I'm still in utter failure after a full day's work.
> > > > > >
> > > > > > I finally got the thing to seemingly install correctly (at least
> > > > > > to the point that I could start Apache/PHP and still use DB2) by
> > > > > > using iODBC. I pointed iODBC at my db2 stuff and db2 queries
> > > > > > work fine!
> > > > > >
> > > > > > However, the FreeTDS stuff seems to be getting nowhere...
> > > > > >
> > > > > > odbc.ini:
> > > > > > [ODBC Data Sources]
> > > > > > sw_p = IBM DB2 Connect Driver
> > > > > > pivotal = FreeTDS Driver
> > > > > >
> > > > > > [Default]
> > > > > > driver = /usr/lib/oplodbc.so.1
> > > > > >
> > > > > > [sw_p]
> > > > > > Description = DB2 Production Database
> > > > > > Options = sw_p
> > > > > > Port = 523
> > > > > > Protocol = TCP/IP
> > > > > > Driver = /usr/DBMdb2/V7.1/lib/libdb2.so.1
> > > > > > Database = sw
> > > > > > FetchBufferSize = 99
> > > > > >
> > > > > > [pivotal]
> > > > > > Description = Pivotal Production Database
> > > > > > Options = sw_enterprise_data
> > > > > > Port = 1433
> > > > > > Host = 192.168.24.6
> > > > > > ServerType = SQLServer 2000
> > > > > > Protocol = TCP/IP
> > > > > > Driver = /usr/lib/libtdsodbc.so
> > > > > > Database = sw_enterprise_data
> > > > > > FetchBufferSize = 99
> > > > > > Trace = No
> > > > > >
> > > > > >
> > > > > >
> > > > > > odbcinst.ini:
> > > > > > [ODBC Drivers]
> > > > > > IBM DB2 Connect Driver = Installed
> > > > > > FreeTDS Driver = Installed
> > > > > >
> > > > > > [IBM DB2 Connect Driver]
> > > > > > Driver = /usr/IBMdb2/V7.1/lib/libdb2.so.1
> > > > > > Setup = /usr/IBMdb2/V7.1/lib/libdb2.so.1
> > > > > >
> > > > > > [FreeTDS Driver]
> > > > > > Driver = /usr/lib/libtdsodbc.so
> > > > > > Setup = /usr/lib/libtdsodbc.so
> > > > > >
> > > > > >
> > > > > >
> > > > > > test.php:
> > > > > > <?php
> > > > > >
> > > > > > $piv_conn = odbc_connect ('pivotal', 'SECUREWORKS\cshobe',
> > > > > > 'password'); $dbtest = odbc_exec ($piv_conn, 'select * from
> > > > > > company');
> > > > > >
> > > > > > ?>
> > > > > >
> > > > > >
> > > > > >
> > > > > > I get the following when I try to load it:
> > > > > >
> > > > > > Warning: SQL error: Could not find Database parameter, SQL state
> > > > > > 08001 in SQLConnect in test.php on line 3.
> > > > > > Warning: Supplied argument is not a valid ODBC-Link resource in
> > > > > > test.php on line 4.
> > > > > >
> > > > > >
> > > > > > Help please!! I'm stuck and don't know where to go from here.
> > > > >
> > > > > ---
> > > > > You are currently subscribed to freetds as: [cshobe AT softhome.net]
> > > > > To unsubscribe, forward this message to
> > > > > $subst('Email.Unsub')
> > >
> > > ---
> > > You are currently subscribed to freetds as: [cshobe AT softhome.net]
> > > To unsubscribe, forward this message to
> > > $subst('Email.Unsub')
>
> ---
> You are currently subscribed to freetds as: [cshobe AT softhome.net]
> To unsubscribe, forward this message to
> $subst('Email.Unsub')

--
Casey Allen Shobe, Network Security Analyst
SecureWorks, Inc. / Phone: 404.327.6339 x213
cshobe AT secureworks.net / http://www.secureworks.net
Dynamic Network Security Monitoring / Intrusion Prevention

---
You are currently subscribed to freetds as: [jez AT whatsonwhen.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')




Archive powered by MHonArc 2.6.24.

Top of Page