FreeTDS Development Group

[Brian Bruns <camber AT ais.org>]

Hmmm, can you test with SQSH to see if it happens there too? Or whether 
this is specific to the ODBC driver?

By way of techical information, 4000 is the default for the driver as 
configured --with-tdsver=5.0 (the default). This is overridden in a few 
places: 1) the freetds.conf file 2) the TDSPORT environment variable 3) 
the login structure as set by the application (the ODBC driver in this 
case).

So, it would appear the config routines are not reading the 'port =' from 
the freetds.conf file correctly for unknown reasons. 

or

If your server name is the same as the host it is on (ie the hosts name is 
'foo' and you called your server entry 'foo') then by a series of defaults 
the IP address will be correct (gethostbyname() will be called on the 
servername to get an IP) but the port will be the default.  If this is the 
case, then the freetds.conf file is not being found/is unable to be 
opened.

Brian

On Tue, 6 Nov 2001, Robert Tuttle wrote:

> Using RH Linux 6.2, unixODBC (w/isql), and FreeTDS-0.53pre1, always
> getting a dump file entry of:
> 
> 2001-11-06 20:36:14 Connecting addr xxx.xxx.xxx.xxx port 4000
> (hidden IP address, it is the correct one though).  
> 
> No matter where I set the communication information (server, port) it
> still comes up trying to connect ot port 4000.
> 
> - I tried using the freetds.conf file:
> [Foo]
> host = xxx.xxx.xxx.xxx
> port = 1433
> tds version = 4.2
> 
> - I tried using interfaces file also:
> [Foo]
> query tcp 4.2 xxx.xxx.xxx.xxx 1433
> 
> Don't have the time to get into CVS to get latest snapshot and this is not
> a high priority for me right now, so should I wait until the next .53
> release to try again, or is this a known issue with a quick fix somewhere?
> 
> Thanks.
> 
> ---
> You are currently subscribed to freetds as: [camber AT ais.org]
> To unsubscribe, forward this message to $subst('Email.Unsub')
>