FreeTDS Development Group

["Lowden, James K" <LowdenJK AT bernstein.com>]

> 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 e-mail
correspondence of staff members serving certain functions.