FreeTDS Development Group

["David Nordenberg" <dnordenberg AT users.sourceforge.net>]

>So, this points at a connection outbound from FreeTDS to a port and IP
>address that isn't valid. This might be because FreeTDS cannot find the
>IP address in the configuration file, or because it has two
>configuration files to choose from and has chosen wrongly.
I do not have two config files.

>Check the configuration file. Consider running tcpdump on your primary
>network interface, monitoring port 1433. e.g. tcpdump -i eth0 port 1433
dna.utb.net is a internal computer so I changed -i to eth1. No packets
going though there when I try sqsh -H dna.utb.net or the correct ip
192.168.1.97 :( It looks like freetds simply isn't trying to do abything
to connect at all :(

>Meanwhile I'll look at improving the connection refusal message to
>indicate where it really went.
Yeah, Well describing error messages are always nice :)