user '(null)'. Reason: Not associated with a trusted SQL
Server Connection".
We have a WinForms application written in VB.NET 2003 and
connect to a SQL Server 2000 (SP3) DB with the following
connection string:
gstrConn = _
"Server=SQL2000;" & _
"DataBase=dbname;" & _
"Integrated Security=SSPI;"
The application works perfectly for the users on one
network domain, but the error listed above appears when
trying to access the DB application from a user's
workstation on another domain. The user has a SQL Server
account. We have even tried to have the user run the DB
application in a smart client "trusted assembly"
environment but also get the error. What must be
configured differently and how?
A poor state employee-
Jeromeprevious message: "The application works perfectly for the users on one
network domain, but the error listed above appears when
trying to access the DB application from a user's
workstation on another domain. The user has a SQL Server
account. "
To make a Trusted connection the domains need to have a Trust between them.
The users need to be defined as either a domain user or from a domain
group.
If the user has a SQL Server account, then you are not using Integrated
Security. This is SQL Security. If you want to use SQL Security then you
need to change your connection string. If you want to keep the connection
string as is, then make sure the clients in the other domain can make a
Trusted Connection to SQL. Add the users from the other domain in SQL
Enterprise Manager.
Then, either load the SQL client tools on one of the workstations & test
connections from Query Analyser or try creating a sample ODBC DSN and
request Windows Authentication.
Read this information and it will make more sense.
http://www.microsoft.com/technet/tr...chnet/prodtechn
ol/sql/maintain/security/sp3sec/default.asp
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.|||Thanks Cheif!
Unfortunately, I am not the network or SQL Server
Administrator but I am passing the information on to the
LAN/SQL Administrator. Hopefully, they will know how to
set up the trust between the domains since they are all
within our same division.
My connection string is fine for using Windows
Authentication right?
Also- All users no matter what domain they are on should
be able to access the DB if the domains are trusted, right?
(and the users have SQL Server IDs)
Sorry- I am LAN ignorant and overwhelmed at present trying
to get a grip on VB.NET. (Some finger pointing going own
here but we are civil and friendly).
Ailing in Alabama
Jrome
Merry Christmas from Dixie!
quote:
>--Original Message--
>previous message: "The application works perfectly for
the users on one
quote:
>network domain, but the error listed above appears when
>trying to access the DB application from a user's
>workstation on another domain. The user has a SQL Server
>account. "
>To make a Trusted connection the domains need to have a
Trust between them.
quote:
> The users need to be defined as either a domain user or
from a domain
quote:
>group.
>If the user has a SQL Server account, then you are not
using Integrated
quote:
>Security. This is SQL Security. If you want to use SQL
Security then you
quote:
>need to change your connection string. If you want to
keep the connection
quote:
>string as is, then make sure the clients in the other
domain can make a
quote:
>Trusted Connection to SQL. Add the users from the other
domain in SQL
quote:
>Enterprise Manager.
>Then, either load the SQL client tools on one of the
workstations & test
quote:
>connections from Query Analyser or try creating a sample
ODBC DSN and
quote:
>request Windows Authentication.
>
>Read this information and it will make more sense.
>http://www.microsoft.com/technet/treeview/default.asp?
url=/technet/prodtechn
quote:
>ol/sql/maintain/security/sp3sec/default.asp
>
>Thanks,
>Kevin McDonnell
>Microsoft Corporation
>This posting is provided AS IS with no warranties, and
confers no rights.
quote:|||Previous post questions:
>
>.
>
My connection string is fine for using Windows
Authentication right?
-- Yes.
Also- All users no matter what domain they are on should
be able to access the DB if the domains are trusted, right?
-- Yes. They should have SQL logins defined by NT users or groups.
Thanks,
Kevin McDonnell
Microsoft Corporation
This posting is provided AS IS with no warranties, and confers no rights.
No comments:
Post a Comment