FreeTDS Development Group

["Chris Hettinger" <chettinger AT encompas.com>]

I removed (commented out) the two lines:
  try domain login = yes
  try server login = no

And tried the following tsql tests:

# tsql -S ENCPPP -U 'encompass.enc\chettinger'
Password:
Msg 10019, Level 9, State 0, Server OpenClient, Line 0
Server ENCPPP not found!
There was a problem connecting to the server


I was having a issue resolving the name on the network, so I thought I would 
try by IP.

# tsql -S 192.168.1.235 -U 'encompass.enc\chettinger'
Password:
src/tds/login.c: tds_connect: 192.168.1.235:1433: No route to host
Msg 20009, Level 9, State 0, Server OpenClient, Line 0
Server is unavailable or does not exist.
There was a problem connecting to the server



Thanks, I really appreciate the recommendations

Chris



-----Original Message-----
From: Lowden, James K [mailto:LowdenJK AT bernstein.com]
Sent: Monday, August 04, 2003 1:36 PM
To: 'FreeTDS Development Group'
Subject: RE: [freetds] Domain Login Support, connecting to MSSQL issue


> From: Chris Hettinger [mailto:chettinger AT encompas.com]
> Sent: August 4, 2003 12:39 PM
> 
> I added the line : try server login = no to my freetds.conf

Per Frediano's suggestion, let's remove all "try ... login" lines from
freetds.conf.  Instead, let's use the 'domain\username' form.  

I think there's some possibility that FreeTDS is not reading the
freetds.conf you think it is, because 

> # tsql -S ENCPPP -U chettinger
> Password:
> Msg 10019, Level 9, State 0, Server OpenClient, Line 0
> Server ENCPPP not found!
> There was a problem connecting to the server

indicates it didn't find a machine for servername 'ENCPPP'.  No login was
attempted.  You might want to "export TDSDUMPCONFIG=dumpconfig" and look at
the log.  

> # tsql -S ENCPPP -U encompass.enc\chettinger
                      ^^^^^^^^^^^^^^^^^^^^^^^^
I doubt this will work without single quotes.  Most shells interpret the
backslash:

        $ echo encompass.enc\chettinger
        encompass.encchettinger
        $ echo 'encompass.enc\chettinger'
        encompass.enc\chettinger

> # tsql -S encppp.encompass.enc -U chettinger
> Password:
> Msg 18452, Level 14, State 1, Server , Line 0
> Login failed for user 'chettinger'. Reason: Not associated 
> with a trusted SQL Server connection.
> Msg 20014, Level 9, State 0, Server OpenClient, Line 0
> Login incorrect.
> There was a problem connecting to the server

In this case, I think you bypassed freetds.conf completely.  FreeTDS failed
its lookup of 'encppp.encompass.enc' and decided to try to connect to it as
a machine name (relying on compile-time defaults for any adjustable
settings).  It succeeded, but had no indication you wanted a domain login.
This might work:

# tsql -S encppp.encompass.enc -U 'encompass.enc\chettinger'

if you configured --with-tds-version=7.0.  

But as I said, the "Server ENCPPP not found!" means the freetds.conf files
that were consulted contained no entry (or an invalid entry) for ENCPPP.  

--jkl


> On Fri, 1 Aug 2003 16:05:40 -0500, "Chris Hettinger"
>
> [ENCPPP]
>         host = encppp.encompass.enc
>          port = 1433
>          tds version = 7.0
-----------------------------------------
The information contained in this transmission may contain privileged and 
confidential information and is intended only for the use of the person(s) 
named above. If you are not the intended recipient, or an employee or agent 
responsible for delivering this message to the intended recipient, any 
review, dissemination, distribution or duplication of this communication is 
strictly prohibited. If you are not the intended recipient, please contact 
the sender immediately by reply e-mail and destroy all copies of the original 
message. Please note that we do not accept account orders and/or instructions 
by e-mail, and therefore will not be responsible for carrying out such orders 
and/or instructions.


_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds


CONFIDENTIALITY NOTICE:  This communication, including any attachment, may 
contain confidential information and is intended only for the individual or 
entity to whom it is addressed.  Any review, dissemination, or copying of 
this communication by anyone other than the intended recipient is strictly 
prohibited.  If you are not the intended recipient, please contact the sender 
by reply email, delete and destroy all copies of the original message.'