FreeTDS Development Group

["Brian Morton" <bmorton AT secureworks.com>]

At a certain level they do present security risks.  Here is the guide
section on domain logins.  It looks like your isql differs slightly from
the tsql example.

http://freetds.org/userguide/domains.htm

-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org
[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of Mark Larsen
Sent: Thursday, August 24, 2006 1:05 PM
To: FreeTDS Development Group
Subject: Re: [freetds] SQL Server 200, Windows Server 2003 and FreeTDS

Thanks for the reply.

We actually want to use domain logins.  Our DBA thinks that server
logins
present a security risk.  This did work as a domain login before the
migration.

Thanks.

On 8/24/06, Brian Morton <bmorton AT secureworks.com> wrote:
>
> It looks like when they migrated they may have disabled SQL server
> logins and only left domain login as an option.  Your isql syntax
> suggests that you are trying to connect with SQL server credentials.
> Check out the freetds manual section on domain logins.  If you require
> SQL server login access, have your sysadmin check your security entry
in
> enterprise manager and verify that you are set up for a sql server
login
> and not domain.
>
> -----Original Message-----
> From: freetds-bounces AT lists.ibiblio.org
> [mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of Mark Larsen
> Sent: Thursday, August 24, 2006 12:45 PM
> To: freetds AT lists.ibiblio.org
> Subject: [freetds] SQL Server 200, Windows Server 2003 and FreeTDS
>
> List Members,
>
> We've been using FreeTDS and unixODBC to talk to a SQL Server 2000
> running
> on a Windows Server 2000 for a long time now.  Recently the server was
> migrated to server 2003.  Connections now fail with:
>
> isql 'DNS' 'bdx\\MDMedTrans' 'password' -v
> [S1000][unixODBC][FreeTDS][SQL Server]Unable to connect to data source
> [28000][unixODBC][FreeTDS][SQL Server]Login incorrect.
> [][unixODBC][FreeTDS][SQL Server]Login failed for user '(null)'.
Reason:
> Not
> associated with a trusted SQL Server connection.
> [ISQL]ERROR: Could not SQLConnect
>
> I've tried what's described here
> http://www.freetds.org/userguide/domains.htm#DOMAINDETAILS but this
has
> no
> effect.
>
> We are using versions:
> FreeTDS 0.62.3
> unixODBC-2.2.6
>
> The TDSDump is:
>
> Starting log file for FreeTDS 0.62.3
>         on 2006-08-24 12:38:14 with debug level 99.
> names for ISO-8859-1: ISO-8859-1
> names for UTF-8: UTF-8
> names for UCS-2LE: UCS-2LE
> names for UCS-2BE: UCS-2BE
> iconv to convert client-side data to the "ISO-8859-1" character set
> 12:38:14.593728 tds_iconv_info_init: converting
"ISO-8859-1"->"UCS-2LE"
> 12:38:14.593790 tds_iconv_info_init: converting
"ISO-8859-1"->"UCS-2LE"
> 12:38:14.593831 Connecting to 10.3.3.68 port 1433, TDS 8.0.
> 12:38:14.594175 tds_put_string converting 10 bytes of "mdrnd11910"
> 12:38:14.594223 tds_put_string wrote 20 bytes
> 12:38:14.594252 tds_put_string wrote 0 bytes
> 12:38:14.594275 tds_put_string converting 12 bytes of "NAMD00MED001"
> 12:38:14.594300 tds_put_string wrote 24 bytes
> 12:38:14.594323 tds_put_string wrote 0 bytes
> 12:38:14.594345 tds_put_string converting 10 bytes of "us_english"
> 12:38:14.594369 tds_put_string wrote 20 bytes
> 12:38:14.594392 tds_put_string converting 6 bytes of "DNS"
> 12:38:14.594416 tds_put_string wrote 12 bytes
> 12:38:14.594466 tds_process_login_tokens()
> Received header @ 12:38:14.595137
> 0000 04 01 00 d8 00 00 01 00-                        |........|
>
>
> Received packet @ 12:38:14.595183
> 0000 aa c4 00 14 48 00 00 01-0e 5c 00 4c 00 6f 00 67 |....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 28 00 6e 00 75 00 6c |.e.r. .'
.(.n.u.l|
> 0040 00 6c 00 29 00 27 00 2e-00 20 00 52 00 65 00 61 |.l.).'.. .
.R.e.a|
> 0050 00 73 00 6f 00 6e 00 3a-00 20 00 4e 00 6f 00 74 |.s.o.n.: .
.N.o.t|
> 0060 00 20 00 61 00 73 00 73-00 6f 00 63 00 69 00 61 |. .a.s.s
.o.c.i.a|
> 0070 00 74 00 65 00 64 00 20-00 77 00 69 00 74 00 68 |.t.e.d.
.w.i.t.h|
> 0080 00 20 00 61 00 20 00 74-00 72 00 75 00 73 00 74 |. .a. .t
.r.u.s.t|
> 0090 00 65 00 64 00 20 00 53-00 51 00 4c 00 20 00 53 |.e.d. .S .Q.L.
.S|
> 00a0 00 65 00 72 00 76 00 65-00 72 00 20 00 63 00 6f |.e.r.v.e .r.
.c.o|
> 00b0 00 6e 00 6e 00 65 00 63-00 74 00 69 00 6f 00 6e |.n.n.e.c
.t.i.o.n|
> 00c0 00 2e 00 00 00 00 00 fd-02 00 00 00 00 00 00 00 |........
........|
>
>
> 12:38:14.595331 looking for login token, got  aa(ERROR)
> 12:38:14.595358 tds_process_default_tokens() marker is aa(ERROR)
> tds_get_string: reading 184 from wire to give 92 to client.
> 12:38:14.595424 looking for login token, got  fd(DONE)
> 12:38:14.595448 tds_process_default_tokens() marker is fd(DONE)
> 12:38:14.595473 tds_process_end: more_results = 0
>                 was_cancelled = 0
>                 error = 1
>                 done_count_valid = 0
> 12:38:14.595503 tds_process_end() state set to TDS_IDLE
> 12:38:14.595526 leaving tds_process_login_tokens() returning 0
> 12:38:14.595583 tds_client_msg: #20014: "Login incorrect.".
Connection
> state is now 2.
>
> Any ideas?
>
> Thanks,
>
> Mark
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
> _______________________________________________
> FreeTDS mailing list
> FreeTDS AT lists.ibiblio.org
> http://lists.ibiblio.org/mailman/listinfo/freetds
>
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds