freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
Re: [freetds] Question: configuration of FreeTDS 0.64 with unixODBC-2.2.12 to MS SQL Server 2000
- From: "Jan Lubbers" <jl75 AT xs4all.nl>
- To: "James K. Lowden" <jklowden AT freetds.org>
- Cc: FreeTDS Development Group <freetds AT lists.ibiblio.org>
- Subject: Re: [freetds] Question: configuration of FreeTDS 0.64 with unixODBC-2.2.12 to MS SQL Server 2000
- Date: Tue, 19 Dec 2006 16:06:11 +0100 (CET)
Hi all,
I found the solutions to my problems.
1] On Windows XP, the standard exception in Windows Firewall for
MSSQLServer is set to 1443. This should be set to 1433.
2] On Windows 2000, there is a bug somewhere by which the port number for
SQL Server is not assigned. This can be detected with:
netstat -an
And can be corrected with:
svrnetcn
Solution:
1. Set the port number to a bogus number, e.g. 0. Then, stop and restart
SQL Server.
2. Set the port number to the correct number, i.e. 1433. Then, stop and
restart SQL Server.
Check again with netstat -an to verify that the port is now correctly
assigned.
Maybe this problem + solution can be added to one of the FAQs?
Everything works like a breeze now. I'm off the list for now. Thanks!
Kind regard,
Jan Lubbers
> Jan Lubbers wrote:
>> Hi all,
>>
>> I'm new to this list...
>>
>> I need some help to get going as I'm lost now.
>>
>> I want to query a SQL Server database from Linux. This should be fairly
>> easy, reading the docs. However, I still cannot get it to work.
> ...
>> -----------------------------------------------------------------------
>> -------- /usr/local/etc/freetds.conf
>> <no changes made>
>> -----------------------------------------------------------------------
>> -------- tsql -C:
>> Compile-time settings (established with the "configure" script):
>> Version: freetds v0.64
>> MS db-lib source compatibility: yes [ALSO TRIED: no]
>> Sybase binary compatibility: unknown
>> Thread safety: yes
>> iconv library: yes
>> TDS version: 5.0 [ALSO TRIED: 8.0]
>> iODBC: no
>> unixodbc: yes
>> -----------------------------------------------------------------------
>> --------
>
> Using tsql without adding your server to ${HOME}/.freetds.conf is tricky,
> because without it, the library doesn't know which TDS version the server
> uses. It tries with the compiled-in default (unless TDSVER is set), which
> gives you roughly 50-50 odds of making a connection.
>
> Try adding a freetds.conf entry like this:
>
> [lt06040]
> host = lt06040
> ### port = 1433
> tds version = 8.0
>
> (I think the default port these days is inferred from the TDS version.)
>
> Then you should be able to connect:
>
> $ tsql -S lt06040 -U sa -P sa
>
> If that doesn't work,
>
> $ export TDSDUMP=dump
> $ tsql -S lt06040 -U sa -P sa
> $ less dump
>
> to make sure it's using the file and connecting to (or trying) the right
> address and port.
>
> Once you have that working, ODBC is the next step. Recent snapshot
> include my "osql" shell script, which tests your configuration files
> before invoking unixODBC's isql. You can just download last night's
> snapshot and extract the script. If you try it, please let me know how it
> works out for you.
>
> HTH.
>
> --jkl
>
-
[freetds] Question: configuration of FreeTDS 0.64 with unixODBC-2.2.12 to MS SQL Server 2000,
Jan Lubbers, 12/06/2006
-
Re: [freetds] Question: configuration of FreeTDS 0.64 with unixODBC-2.2.12 to MS SQL Server 2000,
James K. Lowden, 12/07/2006
- Re: [freetds] Question: configuration of FreeTDS 0.64 with unixODBC-2.2.12 to MS SQL Server 2000, Jan Lubbers, 12/07/2006
- Re: [freetds] Question: configuration of FreeTDS 0.64 with unixODBC-2.2.12 to MS SQL Server 2000, Jan Lubbers, 12/19/2006
-
Re: [freetds] Question: configuration of FreeTDS 0.64 with unixODBC-2.2.12 to MS SQL Server 2000,
James K. Lowden, 12/07/2006
Archive powered by MHonArc 2.6.24.