FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

SRV in the PWD file refers to the symbolic name listed in the freetds.conf
or interfaces file, not to a host name.

So in this case, it is defaults to using the server name as a host when it
doesn't find one, however the default port (4000...compile time
default) is wrong for your server 

Brian

On Sat, 22 Sep 2001 listaccount AT earthlink.net wrote:

> To All,
> 
> I have recently downloaded and compiled FreeTDS ver .51 and .52.  When I
> try to run the 'make check', all the checks fail. I am getting the
> following error:
> 
> connect: Connection refused
> tds_connect() failed
> try_tds_login() failed
> 
> My system is as follows:
> 
> FreeBSD 4.3
> FreeTDS configured with --with-tdsver=42  and  --with-tdsver=70  (not at
> the same time, but tests were tried with each compile)
> 
> A PWD file that looks like:
> UID=sa
> PWD=sybase
> SRV=10.10.10.101
> DB=freetds
> 
> On .52 a freetds.conf file with the following changes:
> comment out [JDBC] section
> added:
> [freetds]
>         host = 10.10.10.101
>         port = 1433
>         tds version = 7.0      (version was changed depending on what
> version was compiled)
> 
> The MS SQL Server is as follows:
> Win 2000 Pro (IP 10.10.10.101)
> SQL Server 7
> freetds database I created (with one junk table)
> login set to both database and system
> sa account password changed to 'sybase'
> 
> 
> Below is a quick tcpdump of the interface when I kick off the check.  I
> wanted to see if my machine was at least trying to talk to the SQL server.
>  If anyone can help me get this fixed I would greatly appreciate it.  If I
> have left out some inportant information please let me know and I will
> supply that as quickly as possible.
> 
> Thanks in advance,
> 
> Scott
> 
> 
> Output from tcpdump:
> 
> 19:25:18.700947 arp who-has 10.10.10.1 tell 10.10.10.199
> 19:25:18.701220 arp reply 10.10.10.1 is-at 0:80:29:ed:d1:43
> 19:25:18.701234 10.10.10.199.1261 > 10.10.10.1.domain:  55854+ PTR?
> 106.10.10.10.in-addr.arpa. (43)
> 19:25:18.702460 10.10.10.1.domain > 10.10.10.199.1261:  55854 NXDomain*
> 0/1/0 (112)
> 19:25:19.700254 10.10.10.199.1262 > 10.10.10.1.domain:  55855+ PTR?
> 1.10.10.10.in-addr.arpa. (41)
> 19:25:19.701520 10.10.10.1.domain > 10.10.10.199.1262:  55855* 1/1/1 PTR 
> (113)
> 19:25:21.627071 10.10.10.199.1172 > 10.10.10.101.4000: S
> 2771345704:2771345704(0) win 16384 <mss 1460> (DF)
> 19:25:21.627643 10.10.10.101.4000 > 10.10.10.199.1172: R 0:0(0) ack
> 2771345705 win 0
> 19:25:21.671172 10.10.10.199.1173 > 10.10.10.101.4000: S
> 2523990690:2523990690(0) win 16384 <mss 1460> (DF)
> 19:25:21.671577 10.10.10.101.4000 > 10.10.10.199.1173: R 0:0(0) ack
> 2523990691 win 0
> 19:25:21.700549 10.10.10.199.1263 > 10.10.10.1.domain:  55856+ PTR?
> 101.10.10.10.in-addr.arpa. (43)
> 19:25:21.701581 10.10.10.1.domain > 10.10.10.199.1263:  55856 NXDomain*
> 0/1/0 (112)
> 19:25:21.715752 10.10.10.199.1174 > 10.10.10.101.4000: S
> 4092997914:4092997914(0) win 16384 <mss 1460> (DF)
> 19:25:21.716156 10.10.10.101.4000 > 10.10.10.199.1174: R 0:0(0) ack
> 4092997915 win 0
> 19:25:21.759620 10.10.10.199.1175 > 10.10.10.101.4000: S
> 3748089963:3748089963(0) win 16384 <mss 1460> (DF)
> 19:25:21.760021 10.10.10.101.4000 > 10.10.10.199.1175: R 0:0(0) ack
> 3748089964 win 0
> 19:25:21.802953 10.10.10.199.1176 > 10.10.10.101.4000: S
> 3794863539:3794863539(0) win 16384 <mss 1460> (DF)
> 19:25:21.803365 10.10.10.101.4000 > 10.10.10.199.1176: R 0:0(0) ack
> 3794863540 win 0
> 19:25:21.847095 10.10.10.199.1177 > 10.10.10.101.4000: S
> 4157088539:4157088539(0) win 16384 <mss 1460> (DF)
> 19:25:21.847495 10.10.10.101.4000 > 10.10.10.199.1177: R 0:0(0) ack
> 4157088540 win 0
>