Skip to Content.
Sympa Menu

freetds - Re: [freetds] Trouble logging into SQL Server using tsql

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Naman Sheth" <nsheth AT windwardcg.com>
  • To: <freetds AT lists.ibiblio.org>
  • Subject: Re: [freetds] Trouble logging into SQL Server using tsql
  • Date: Thu, 23 Feb 2006 11:07:47 -0600

Try using the UserID without quotes as you are doing. I assume you have
already but the entry for the host in the conf file.

-N

----------------------------------------------------------------------

Message: 1
Date: Wed, 22 Feb 2006 20:48:02 -0500
From: "James K. Lowden" <jklowden AT freetds.org>
Subject: Re: [freetds] Trouble logging into SQL Server using tsql
To: FreeTDS Development Group <freetds AT lists.ibiblio.org>
Message-ID: <20060222204802.144421b8.jklowden AT freetds.org>
Content-Type: text/plain; charset=US-ASCII

Chris Haag wrote:
>
> I am having trouble with what should be a simple authentication issue.
> I have attempted to do my homework and hope I am not missing something
> obvious. Thanks to anyone who takes a look!
>
> At a high level I get "login failed"
>
> -bash-3.00$ tsql -S BUSSYS -U 'CustomerSupport'
> locale is "en_US.UTF-8"
> locale charset is "UTF-8"
> Password:
> Msg 18456, Level 14, State 1, Server , Line 0
> Login failed for user 'CustomerSupport'.
> Msg 20014, Level 9, State 0, Server OpenClient, Line 0
> Login incorrect.
> There was a problem connecting to the server
>
> Obviously, I'd think bad credentials. However, from an XP laptop,
> using ODBC connections I can authenticate fine.

A little known "trick": if you use TDS 4.2, you will see the login packet
-- which includes your username and password -- transmitted to the
server. That packet is not logged by default with TDS 7.0+. In theory,
you should be able to set the debug flags to see it regardless, but that's
a future feature so far.

In my experience, some versions of Microsoft's tools ignore the non-domain
login if a domain login exists. If you use 4.2 and see the correct
username+password in the TDSDUMP log, then double check that the account
is really useable. I should oughta work.

HTH.

--jkl






Archive powered by MHonArc 2.6.24.

Top of Page