|
|
|
|
||||||
| ms.sqlserver.setup Questions about SQL Server. |
![]() |
|
|
LinkBack | Outils de la discussion |
|
|
#1 |
|
Messages: n/a
Hébergeur: |
Hi all,
I have SQL Server 2005 installed on my PC. I haven't touched any of the settings that came "out of the box". In particular, I verified that SQL Server is configured to allow Windows Authentication (the default setting). If I run SQL Server Management Studio from my non-privileged domain account and attempt to connect to the server using Windows Authentication, it complains that "Login failed ...". ! |
|
|
|
#2 |
|
Messages: n/a
Hébergeur: |
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. ================================================== ==== |
|
|
|
#3 |
|
Messages: n/a
Hébergeur: |
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@online.microsoft.com> wrote in message news:6WgJ9QCTHHA.2356@TK2MSFTNGHUB02.phx.gbl... > 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. > ================================================== ==== > |
|
|
|
#4 |
|
Messages: n/a
Hébergeur: |
I called MS tech support and got an answer I like better. In Management
Studio, I added my domain account under the Security\Logins page. Works like a champ. - Bob "Bob Altman" <rda@nospam.com> wrote in message news:es7BmUGTHHA.4844@TK2MSFTNGP03.phx.gbl... > 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@online.microsoft.com> wrote in message > news:6WgJ9QCTHHA.2356@TK2MSFTNGHUB02.phx.gbl... >> 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. >> ================================================== ==== >> > > |
|
|
|
#5 |
|
Messages: n/a
Hébergeur: |
Hi Bob,
Thanks for your response. I am sorry that I had misunderstood your issue. I had thought that your client and SQL Server are located in different domains. In that case, the domain trust relationship should be established first. From your response, I know that I made the easy things complex. Sorry for bringing you any inconvenience. Anyway, I am glad to hear that you have resolved this issue by opening an support incident. If you have any other questions or concerns, please feel free to let me know. Have a good day! Charles Wang Microsoft Online Community Support |
|
|
|
#6 |
|
Messages: n/a
Hébergeur: |
No problem. That's the challenge of working in a terse, non-real-time
medium like this. - Bob "Charles Wang[MSFT]" <changliw@online.microsoft.com> wrote in message news wakMYNTHHA.2356@TK2MSFTNGHUB02.phx.gbl...> Hi Bob, > Thanks for your response. > > I am sorry that I had misunderstood your issue. I had thought that your > client and SQL Server are located in different domains. In that case, the > domain trust relationship should be established first. > > From your response, I know that I made the easy things complex. Sorry for > bringing you any inconvenience. Anyway, I am glad to hear that you have > resolved this issue by opening an support incident. > > If you have any other questions or concerns, please feel free to let me > know. Have a good day! > > Charles Wang > Microsoft Online Community Support > |
|
![]() |
| Outils de la discussion | |
|
|