January 7, 2016 at 2:30 pm
I have a SQL 2012 Server that I am not able to access from my workstation using SQL MGMT Studio with my Active Directory username. However, I am able to access the SQL MGMT Studio when I am logged directly on the server. I am also able to access the server remotely using a local SQL account from my workstation. I am unable to find out why the SQL Server Authentication is working remotely but Windows Authentication only works when logged on directly to the SQL server.
January 7, 2016 at 2:46 pm
CELLIOTT-497809 (1/7/2016)
I have a SQL 2012 Server that I am not able to access from my workstation using SQL MGMT Studio with my Active Directory username. However, I am able to access the SQL MGMT Studio when I am logged directly on the server. I am also able to access the server remotely using a local SQL account from my workstation. I am unable to find out why the SQL Server Authentication is working remotely but Windows Authentication only works when logged on directly to the SQL server.
Are you on the same domain as the server?
Can you access other servers?
Can anybody else on your domain access the server?
Can you ping the server from your workstation?
How are you logging in directly to the server?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
January 7, 2016 at 2:47 pm
CELLIOTT-497809 (1/7/2016)
I have a SQL 2012 Server that I am not able to access from my workstation using SQL MGMT Studio with my Active Directory username. However, I am able to access the SQL MGMT Studio when I am logged directly on the server. I am also able to access the server remotely using a local SQL account from my workstation. I am unable to find out why the SQL Server Authentication is working remotely but Windows Authentication only works when logged on directly to the SQL server.
wierd...is it just you, or can NOONE use domain credentials?
if it's just you, it might be your password expired today, and until you lock your computer, or reboot you don't noticve, but the server knows you are no longer valid.
if it's everyone, you'll want to loop in the netwrok guys, because the server's unable to authenticate tokens for permissions. can't say i've seen that in a long while, maybe the domain controller is out?
Lowell
January 7, 2016 at 2:56 pm
Are you on the same domain as the server? Yes
Can you access other servers? Yes
Can anybody else on your domain access the server? Server is reachable via RDP with my user account. I am able to access SQL MGMT Studio via the RDP Session, just not from the SQL MGMT Studio local install on my PC
Can you ping the server from your workstation? Yes
How are you logging in directly to the server? Yes
January 7, 2016 at 3:03 pm
CELLIOTT-497809 (1/7/2016)
Are you on the same domain as the server? YesCan you access other servers? Yes
Can anybody else on your domain access the server? Server is reachable via RDP with my user account. I am able to access SQL MGMT Studio via the RDP Session, just not from the SQL MGMT Studio local install on my PC
Can you ping the server from your workstation? Yes
How are you logging in directly to the server? Yes
Not a valid answer for: How are you logging in directly to the server?
For: Can anybody else on your domain access the server? I meant are you the only one with this problem? Can others connect with SSMS?
For best practices on asking questions, please read the following article: Forum Etiquette: How to post data/code on a forum to get the best help[/url]
January 7, 2016 at 3:03 pm
Lowell (1/7/2016)
CELLIOTT-497809 (1/7/2016)
I have a SQL 2012 Server that I am not able to access from my workstation using SQL MGMT Studio with my Active Directory username. However, I am able to access the SQL MGMT Studio when I am logged directly on the server. I am also able to access the server remotely using a local SQL account from my workstation. I am unable to find out why the SQL Server Authentication is working remotely but Windows Authentication only works when logged on directly to the SQL server.wierd...is it just you, or can NOONE use domain credentials?
if it's just you, it might be your password expired today, and until you lock your computer, or reboot you don't noticve, but the server knows you are no longer valid.
if it's everyone, you'll want to loop in the netwrok guys, because the server's unable to authenticate tokens for permissions. can't say i've seen that in a long while, maybe the domain controller is out?
My domain credentials are fine because I am able to use my domain account to access SQL MGMT Studio when I am logged onto the SQL server locally/RDP. It is only remotely that it doesn't work. Other guys on my team have the same issue with this server. I have attached to 35+ other SQL servers in our domain without issue from my desktop. It seems like I have had this issue before and a "magic" check box needs to be changed. I can't recall though.
January 7, 2016 at 3:05 pm
CELLIOTT-497809 (1/7/2016)
I have a SQL 2012 Server that I am not able to access from my workstation using SQL MGMT Studio with my Active Directory username. However, I am able to access the SQL MGMT Studio when I am logged directly on the server. I am also able to access the server remotely using a local SQL account from my workstation. I am unable to find out why the SQL Server Authentication is working remotely but Windows Authentication only works when logged on directly to the SQL server.
WHAT A NEWBIE!!!!! I failed to post the error.... sorry. :hehe:
Error: Cannot connect to <server name>
Additional information:
Cannot generate SSPI context. (Microsoft SQL Server)
January 8, 2016 at 7:06 am
Verified with 2 other users and they are getting the same error. One of the users was a Domain admin account. BTW... I forgot to add the error message, so I added below.
January 8, 2016 at 7:34 am
CELLIOTT-497809 (1/8/2016)
Verified with 2 other users and they are getting the same error. One of the users was a Domain admin account. BTW... I forgot to add the error message, so I added below.
ahh the error is the key here, i just saw that.... "Cannot generate SSPI context" part! it's a network Service Principal Name issue, i think.
loop your network guys in on this.
The "Cannot generate SSPI context" error is generated when SSPI uses Kerberos authentication to delegate over TCP/IP and Kerberos authentication cannot complete the necessary operations to successfully delegate the user security token to the destination computer that is running SQL Server.
How to troubleshoot the "Cannot generate SSPI context" error message
Lowell
Viewing 9 posts - 1 through 9 (of 9 total)
You must be logged in to reply to this topic. Login to reply