FreeTDS Development Group

["ZIGLIO, Frediano, VF-IT" <Frediano.Ziglio AT vodafone.com>]

> 
> Freddy,
> 
> Yes, I'm using protocol version 8.  Here's my freetds config:
> [SERVER]
>          host = xyz.district125.k12.il.us
>          port = 1433
>          tds version = 8.0
> 
> Here's the debugging output from TDSDUMP=stdout /usr/local/bin/tsql 
> -Sserver -Uuser -Ppasswd
> 
> locale is "C"
> locale charset is "US-ASCII"
> util.c:261Starting log file for FreeTDS 0.64.dev.20050209
>          on 2005-02-14 11:45:58 with debug flags 0x4fff.
> iconv.c:198names for ISO-8859-1: ISO-8859-1
> iconv.c:198names for UTF-8: UTF-8
> iconv.c:198names for UCS-2LE: UCS-2LE
> iconv.c:198names for UCS-2BE: UCS-2BE
> iconv.c:349iconv to convert client-side data to the "US-ASCII" 
> character set
> iconv.c:501tds_iconv_info_init: converting "US-ASCII"->"UCS-2LE"
> iconv.c:501tds_iconv_info_init: converting "ISO-8859-1"->"UCS-2LE"
> net.c:149Connecting to 216.125.128.177 port 1433.
> net.c:636Sending packet
> 0000 12 01 00 34 00 00 00 00-00 00 15 00 06 01 00 1b 
> |...4.... ........|
> 0010 00 01 02 00 1c 00 0c 03-00 28 00 04 ff 08 00 01 
> |........ .(......|
> 0020 55 00 00 00 4d 53 53 51-4c 53 65 72 76 65 72 00 
> |U...MSSQ LServer.|
> 0030 c1 3c 00 00            -                        |.<..|
> 
> net.c:423Received header
> 0000 04 01 00 25 00 00 01 00-                        |...%....|
> 
> net.c:517Received packet
> 0000 00 00 15 00 06 01 00 1b-00 01 02 00 1c 00 01 03 
> |........ ........|
> 0010 00 1d 00 00 ff 08 00 02-fe 00 00 00 00          |........ .....|
> 
> login.c:943detected flag 0
> util.c:117Changing query state from TDS_IDLE to TDS_DEAD
> Msg 20014, Level 9, State 0, Server OpenClient, Line 0
> Login incorrect.
> token.c:2431tds_client_msg: #20014: "Login incorrect.".  Connection 
> state is now 4.
> mem.c:478tds_free_all_results()
> There was a problem connecting to the server
> 
> Hope this helps.  Thanks for the recommendation on the version to use 
> in production systems.  We're using FreeTDS on an internal web 
> applications server, and it's been quite an asset to our school 
> district.
> 
> Michael
> 

Opps.... no, I tested by myself. If server has a certificate it wants an
encrypted login... You have to enable SSL support (still in development,
it require gnutls with a patch). See
https://lists.ibiblio.org/sympa/arc/freetds/2005q1/017951.html and
https://lists.ibiblio.org/sympa/arc/freetds/2005q1/017972.html.

freddy77