Skip to Content.
Sympa Menu

freetds - RE: [freetds] Domain Login Support, connecting to MSSQL issue

freetds AT lists.ibiblio.org

Subject: FreeTDS Development Group

List archive

Chronological Thread  
  • From: "Lowden, James K" <LowdenJK AT bernstein.com>
  • To: 'FreeTDS Development Group' <freetds AT lists.ibiblio.org>
  • Subject: RE: [freetds] Domain Login Support, connecting to MSSQL issue
  • Date: Mon, 4 Aug 2003 15:03:48 -0400

> From: B. Bell [mailto:bradleyb AT u.washington.edu]
> Sent: August 4, 2003 11:51 AM
>
> also, starting with win2k, logins are often written email
> address-style,
> i.e. username@domain or username AT fully.qualified.domain.name

Thank you for that bit of intelligence, Brad. I hadn't seen that.

> I have MS SQL server running on win2k, in
> a win2k domain. We have no NT workstations in our domain, so
> all "legacy" protocols and such have been disabled.

What means "legacy"? And remind me, you're using 0.61 or later?

We speak tcp/ip only, no named pipes. We should be able to perform a domain
login via tcp/ip to a W2K server.

> Whenever I try to get domain logins working, I get the error: "Login
> failed for user 'example'. Reason: Not associated with a trusted SQL
> Server connection"

(The username is really 'example', right?)

If this fails, I think folks here would like to see you TDSDUMP log:

$ tsql -S servername -U 'domain\example' -P password

If I undstand Frediano rightly, 'domain\example' forces a domain login
irrespective of what's in freetds.conf. It's supposed to be a working
feature, and some people are definitely using it.

--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 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.






Archive powered by MHonArc 2.6.24.

Top of Page