Re: Using Windows Authentication to access SQL Server from non-domain
- From: "David Browne" <davidbaxterbrowne no potted meat@xxxxxxxxxxx>
- Date: Thu, 27 Apr 2006 09:08:08 -0500
"Stephen Schaub" <Stephen Schaub@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6FE36564-6CB4-4B8C-BC79-84A3B598CA70@xxxxxxxxxxxxxxxx
We have SQL Server 2000 installed on Windows Server 2003 SP 1. The server
is
a member of a domain.
We have developers on workstations not part of the domain who need to use
a
Trusted Connection to access a database on the server. I've read some
other
posts that suggest this is possible. The developers created a local
account
on their workstation with the username/password credentials that match
those
of a domain user. When logged in under that account on their local
workstation, I believe they should be able to establish a trusted
connection
to SQL Server using Enterprise Manager. But the authentication fails with
the
message "Logon failed for user '(null)'."
Any suggestions would be appreciated.
That's not quite right. The users should create a local account with
username and password matching a _local_ account on the server, not a domain
account.
David
.
- Prev by Date: Re: SQL Server Logins do not have database access
- Next by Date: Re: Speed of SQL Authenication vs. Trusted Connection
- Previous by thread: Re: SQL Server Logins do not have database access
- Next by thread: Change Password
- Index(es):
Relevant Pages
|