Skip to Content.
Sympa Menu

freetds - Re: [freetds] SQL Server 200, Windows Server 2003 and FreeTDS

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Mark Larsen" <larsenmtl AT gmail.com>
  • To: "FreeTDS Development Group" <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] SQL Server 200, Windows Server 2003 and FreeTDS
  • Date: Fri, 25 Aug 2006 16:45:30 -0400

Thanks everyone, we've found a solution.

It turns out that the fix described in
http://www.freetds.org/userguide/domains.htm#DOMAINDETAILS did in fact
work. For some reason, though, the server borked and the group policy.
Once it was recreated, everybody's happy.

Mark

On 8/25/06, ZIGLIO, Frediano, VF-IT <Frediano.Ziglio AT vodafone.com> wrote:

>
> 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

You should first try with tsql. Note that you MUST use tds 7.0 or 8.0. I
think \ is double, you should use something like

TDSVER=8.0 tsql -H<hostname.dnsdomain> -p<your_port> -U 'bdx\MDMedTrans'
-P <yourpassword>

hostname.dnsdomain is the host you can ping while your_port is the mssql
port (1433 for default mssql instance). yourpassword is MDMedTrans
domain password (case sensitive!)

> [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
>

:(
Not that updated but should work. Which operating system and version are
using?

> 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- |........|
>
....
>
> Any ideas?
>

bye
freddy77

_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds





Archive powered by MHonArc 2.6.24.

Top of Page