![]() | |
![]() |
| | Thread Tools | Display Modes |
#1
| |||
| |||
|
#2
| |||
| |||
|
|
Hi Rotsey, As you mentioned you make your users connect to SQL Server in Integrated Security mode, then your users' windows domain accounts are used for login to SQL Server as Windows Authentication. If that user is in a different Domain\Global Group which is restricted to connect to SQL Server or do not have permission for SQL Server login then he\she cannot connect to SQL Server. I suggest you to set up a Windows Global Group and put your .Net 2.0 app users in to that group and give that group the necessary permissions in SQL Server login so that they are going to be able to reach resources as they need. So, you will not bother yourself with individual accounts. -- Ekrem Önsoy "Rotsey" <malcolm_smith (AT) RemoveThis (DOT) optusnet.com.au> wrote in message news:ubyItqr6HHA.2632 (AT) TK2MSFTNGP06 (DOT) phx.gbl... Hi, I have a .Net 2.0 windows app that connects to a SQL Express DB. I have 2 Clients using it fine. It accesses stored procs to update data. The clients use integrated security. data source='SQLSERVER\SQLEXPRESS';initial catalog=tbrPData;integrated security=SSPI The problem is on the third client I get Exsecute perimission denied on sp message. It also uses integrated security. How do I find out what user this client is accessing the DB with??? rotsey |
![]() |
| Thread Tools | |
| Display Modes | |
| |