freetds AT lists.ibiblio.org
Subject: FreeTDS Development Group
List archive
- From: "Jay Sauls" <jaysauls AT hotmail.com>
- To: "'TDS Development Group'" <freetds AT franklin.oit.unc.edu>
- Subject: Re: How to compile SQSH with FreeTDS .60?
- Date: Mon, 7 Oct 2002 14:53:02 -0700
Well, that's starting to narrow down the problem a bit, maybe.
I changed the entry in my freetds.conf to the following:
# jay's SQLServer
[jays]
host = jays.corp.digimine.com
port = 1433
tds version = 8.0
try domain login = yes
try server login = no
nt domain = corp
; cross domain login = yes
dump file = /home/jays/jays.tdsdump.txt
debug level = 99
Now when I run sqsh, I get this:
[jays@jays-linux src]$ ./sqsh -S jays -U corp\\jays
sqsh-2.1 Copyright (C) 1995-2001 Scott C. Gray
This is free software with ABSOLUTELY NO WARRANTY
For more information type '\warranty'
Password:
Server jays not found!
[jays@jays-linux /]$
So I suspect that my problem all along has been that sqsh isn't reading
the freetds.conf file.
Now I'm trying to track down where the freetds.conf file is supposed to
be.
Right now, I've got freetds.conf files in the following locations:
/usr/local/etc/freetds.conf
/home/jays/freetds.conf
The two files are identical and contain the [jays] entry above.
Specifying -I with an explicit path gives this result:
[jays@jays-linux src]$ sqsh -S jays -U jays -I /home/jays/freetds.conf
sqsh-2.1 Copyright (C) 1995-2001 Scott C. Gray
This is free software with ABSOLUTELY NO WARRANTY
For more information type '\warranty'
Password:
Msg 18452, Level 14, State 1
Login failed for user 'jays'. Reason: Not associated with a trusted
SQL Server connection.
Login Incorrect.
[jays@jays-linux /]$
specifying -U corp\\jays gives the same failure....
So I'm wondering if the freetds.conf file isn't being parsed correctly?
-----Original Message-----
From: bounce-freetds-149810 AT franklin.oit.unc.edu
[mailto:bounce-freetds-149810 AT franklin.oit.unc.edu] On Behalf Of Lowden,
James K
Sent: Monday, October 07, 2002 1:53 PM
To: TDS Development Group
Subject: [freetds] Re: How to compile SQSH with FreeTDS .60?
> From: Jay Sauls [mailto:jaysauls AT hotmail.com]
> Sent: October 7, 2002 3:05 PM
>
> [jays@jays-linux src]$ ./sqsh -S jays.corp.digimine.com -U corp\\jays
> sqsh-2.1 Copyright (C) 1995-2001 Scott C. Gray
> This is free software with ABSOLUTELY NO WARRANTY
> For more information type '\warranty'
> Password:
> Msg 18452, Level 14, State 1
>
> Login failed for user 'corp'. Reason: Not associated with a
> trusted SQL
> Server
> connection.
> Login incorrect.
>
> # jay's SQLServer
> [jays.corp.digimine.com]
> host = jays.corp.digimine.com
> port = 1433
> tds version = 8.0
> try domain login = yes
> try server login = no
> nt domain = corp
> ; cross domain login = yes
> dump file = /home/jays/jays.tdsdump.txt
> debug level = 99
Jay,
I don't know what the rule for servernames was when sqsh was being
actively
maintained. Yours has embedded '.' characters and is 22 characters
long.
Might be a sqsh limitation or ct-lib dunderheadedness.
Does it help to change '[jays.corp.digimine.com]' to '[bluejay]'? The
name
in freetds.conf is purely clientside; it's used to look up the server's
address via its hostname. So there's no change you'd need to make at
the
server to try this.
(BTW, you did "turn on logging" by setting the dump file in
freetds.conf.
That's what I meant. Too bad the pre-login data aren't logged.) :(
--jkl
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 for certain accounts we do not accept
orders and/or instructions by e-mail, and for those accounts we will not
be
responsible for carrying out such orders and/or instructions. Kindly
refrain
from sending orders or instructions by e-mail unless you have confirmed
that
we accept such communications for your account. Please also note that to
satisfy regulatory requirements we review the outgoing and incoming
correspondence of staff members serving certain functions.
---
You are currently subscribed to freetds as: [jaysauls AT hotmail.com]
To unsubscribe, forward this message to
$subst('Email.Unsub')
-
Re: How to compile SQSH with FreeTDS .60?
, (continued)
- Re: How to compile SQSH with FreeTDS .60?, James K. Lowden, 10/03/2002
- Re: How to compile SQSH with FreeTDS .60?, Jay Sauls, 10/04/2002
- Re: How to compile SQSH with FreeTDS .60?, Lowden, James K, 10/06/2002
- Re: How to compile SQSH with FreeTDS .60?, Steve Langasek, 10/06/2002
- Re: How to compile SQSH with FreeTDS .60?, James K . Lowden, 10/06/2002
- Re: How to compile SQSH with FreeTDS .60?, Steve Langasek, 10/06/2002
- Re: How to compile SQSH with FreeTDS .60?, Jay Sauls, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, Steve Langasek, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, Jay Sauls, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, Lowden, James K, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, Jay Sauls, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, Jay Sauls, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, Steve Langasek, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, James K. Lowden, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, Jay Sauls, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, Jay Sauls, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, James K . Lowden, 10/07/2002
- Re: How to compile SQSH with FreeTDS .60?, Jay Sauls, 10/08/2002
- Re: How to compile SQSH with FreeTDS .60?, Lowden, James K, 10/08/2002
- Re: How to compile SQSH with FreeTDS .60?, Jay Sauls, 10/08/2002
- Re: How to compile SQSH with FreeTDS .60?, Steve Langasek, 10/08/2002
Archive powered by MHonArc 2.6.24.