Re: Windows Authentication from a workgroup to a domain sql server
- From: "Russell Fields" <russellfields@xxxxxxxxxx>
- Date: Tue, 27 Mar 2007 08:58:39 -0400
Hello,
I would not have expected this to work. (If it did, it would seem to me like
a great big security hole.)
The "trust" is in your domain. The workgroup login is outside the trust,
despite any naming conventions you might use, and the domain knows that.
If you search TechNet for "domain workgroup trust" you will find several
articles discussing them. One article is:
http://www.microsoft.com/technet/archive/winntas/maintain/acctgrps.mspx?mfr=true
RLF
"Sumon" <sumon.net@xxxxxxxxx> wrote in message
news:1174881992.771015.222320@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
I have got a user from a diff subnet and his computer is not part of
our domain, just a workgroup. But the workgroup name is the same as
our domain name.
The user has a local account, which I have also added in our AD with
the same name and password.
Example Setup:
DOMAIN NAME: abc
SQL Part of abc domain (running as a cluster)
Client Machine Workgroup Name: abc
Not part of any domain.
Local user account name: test
Domain abc also contains a user called abc with same password.
When the user tries to connect the SQL server comes back with:
System.Data.SqlClient.SqlException: Login failed for user ''. The user
is not associated with a trusted SQL Server connection.
What am i missing here.. would this work?
Thanks
Sazzad
.
- References:
- Prev by Date: Re: owned schema or role members?
- Next by Date: Re: User ID issue - urgent
- Previous by thread: Windows Authentication from a workgroup to a domain sql server
- Next by thread: User ID issue - urgent
- Index(es):
Relevant Pages
|