Re: How to access SQL Server from a non-privileged domain account

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hi Charles,

Let me make sure I understand this correctly. My PC is a member of a
domain. I have SQL Server 2005 running on my PC, using Windows
Authentication. If I log on to my PC (that is, the PC hosting SQL Server)
as local admin, I can connect to the server. But if I log in to that same
PC as a non-privileged domain user, I can't.

If I understand your answer correctly, I can't configure SQL Server to allow
my non-privileged account access to it (short of using SQL Server
Authentication); I must grant some set of privileges to my non-privileged
account on my PC in order to allow that account to connect to the server.

Is this correct?

"Charles Wang[MSFT]" <changliw@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:6WgJ9QCTHHA.2356@xxxxxxxxxxxxxxxxxxxxxxxxx
Hi,
Per my understanding, your SQL Server 2005 was configured to run with
Windows Authentication mode, but you wanted your non-privileged domain
account to be able to access the SQL Server.
If I have misunderstood, please let me know.

Since your SQL Server 2005 has been running with Windows Authentication
mode, previledged domain accounts are neccesary for connectivity.
For your situation, you may consider the following resolutions:
1. Contact your network administrator to add your domain account to the
trusted users and assign permissions on it;
For different domains, it is required to establish domain trust
relationship first and you may have a new post at:
microsoft.public.windows.server.active_directory

2. Change your SQL Server 2005 authentication mode to Mix mode so that you
can use a SQL Server account to connect to the instance.
Please refer to:
How to: Change Server Authentication Mode
http://msdn2.microsoft.com/en-us/library/ms188670.aspx

If you have any other questions or concerns, please feel free to let me
know.
Look forward to your response.

Charles Wang
Microsoft Online Community Support

======================================================
When responding to posts, please "Reply to Group" via
your newsreader so that others may learn and benefit
from this issue.
======================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
======================================================



.

Relevant Pages

  • Re: Utter madness!
    ... It is just Windows security stuff. ... You can get a trusted connection back to SQL server. ... ASP.NET account (either processModel or app pool identity depending on ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Passthrough authenication w/ SQL trusted connection
    ... separate connection will be used for each security context (each user ... account will have it's own pool). ... if you are using a Windows 2000 Domain, ... backend SQL Server. ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Search services not available
    ... Let me clarify that our SQL server uses Windows Authentication, ... account, even if it was just for now to get it working, that would be easier ... I have configured the Search service to use this ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Permissions!
    ... This account is used because your web ... application is configured for anonymous access instead of integrated ... The details on how to use Windows ... SQL Server MVP ...
    (microsoft.public.sqlserver.security)
  • connecting to sql server with windows authentication
    ... using windows authentication. ... Use delegation to leverage the current user's account. ... development machine, a live machine, and local installs of IIS for all your ... our DBA wants to keep SQL Server authentication ...
    (microsoft.public.dotnet.framework.aspnet.security)