FreeTDS Development Group

["James K. Lowden" <jklowden AT schemamania.org>]

On Mon, 4 Aug 2003 16:24:13 -0500, "Chris Hettinger"
<chettinger AT encompas.com> wrote:
> 
> If I ping enctux, it return host not found, but it responds just fine to
> ping enctux.encompass.enc.

Let's talk about DNS domains for just a minute.  

Such machine is misconfigured.  The resolver is responsible for forming a
complete DNS name and sending it to the nameserver and/or searching
/etc/hosts.  The resolver has to know what DNS domain to append to
unqualified names.  IOW, when you say, "ping enctux" it's the resolver's
job to convert "enctux" to "enctux.encompass.enc", and ask its nameserver
to look up the IP address for that machine.  Of course, the name may be in
the /etc/hosts file, too (and M$ boxes also have a hosts file).  Whether
the DNS is queried before or after /etc/hosts is usually configurable.  

On my NetBSD machine, the resolver learns its domain name from
/etc/resolv.conf:

$ grep search  /etc/resolv.conf 
search schemamania.org

so if I say "ping www" it knows I mean "ping www.schemamania.org".  

> Part of my trouble with this, I think, is my inability to see the whole
> network picture and understand how each machine communicates. I'm
> getting there, and again thanks for the attention on this issue.
> 
> I issued the net config cmd on my box and it returned:
> Workstation domain                    ENCOMPASS
> Workstation Domain DNS Name           encompass.enc       <-- *
> Logon Domain                          ENCOMPASS

There's another kind of domain, too, known as an "NT domain".  It's
unrelated to the DNS domain.  DNS domains are used for address resolution.
 NT domains are used for authentication.  

In the FreeTDS context of "domain login", we're not interested in the DNS
domain (encompass.enc).  The SQL Server belongs to an "NT domain", and
FreeTDS is providing an encrypted password that the server will ask the
Primary Domain Controller (PDC) to verify.  In short, the "domain" in
question is "ENCOMPASS".  

That leads me to suggest:

        $tsql -S encppp.encompass.enc -U 'ENCOMPASS\chettinger'

> ... I also attemtped to export TDSDUMPCONFIG=dumpconfig. I was returned
> to the prompt, so did it do anything, or where did it put the export?

Oh, you just need to rtfm. :-)   Once you do "export
TDSDUMPCONFIG=dumpconfig" and then run tsql, you'll find a file called
"dumpconfig" in your current working directory.  It will have a verbose
description of where it looked and what it found in its effort to identify
the servername you attempted to connect to.  In the present case, this
would be interesting:

        $tsql -S ENCPPP -U 'ENCOMPASS\chettinger'

Cf. http://www.freetds.org/userguide/x2275.htm

HTH.  

--jkl