[freetds] Domain Login Support, connecting to MSSQL issue

B. Bell bradleyb at u.washington.edu
Mon Aug 4 09:51:29 EDT 2003


On Mon, 4 Aug 2003, Lowden, James K wrote:

> > From: ZIGLIO Frediano [mailto:Frediano.Ziglio at vodafone.com]
> > Sent: August 4, 2003 4:36 AM
> >
> > > [ENCPPP]
> > >         host = encppp.encompass.enc
> > >          port = 1433
> > >          tds version = 7.0
> > > 	 try domain login = yes
> > > 	 try server login = no
> ...
> > > Note to list:  Does anyone want to test this, and preferably
> > > fix it?  A server may be configured to accept both kinds of
> > > logins.  It would be nice to try both in turn before
> > > reporting a failure, because per-connection there's no way to
> > > specify the type.
> >
> ...
> > Another way is to leave all blank and use "domain\username" syntax for
> > user.
>
> I like that idea.  If the username has either of the the forms:
>
> 	domain\username

> 	\\domain\username
is this valid syntax for a username?  I don't think I've ever seen it that
way before.  It looks like a share name (i.e. \\myserver\public)
also, starting with win2k, logins are often written email address-style,
i.e. username at domain or username at fully.qualified.domain.name

Which brings me to my problem:  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.  Should this be a problem with
freetds?
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 server is in Mixed Mode, and server logins work fine.  (and domain
logins work fine, from win2k workstations)

-brad




More information about the FreeTDS mailing list