Solved

The target principal name is incorrect. Cannot generate SSPI context. (Microsoft SQL Server, Error: 0)

Posted on 2014-04-22
5
19,818 Views
Last Modified: 2014-04-24
Hi,

I have added a new PC to the domain where the SQL server resides,
However, when I try to login to the sql server using windows authentication I get the following error:

Cannot connect to a2\a.

------------------------------
ADDITIONAL INFORMATION:

The target principal name is incorrect.  Cannot generate SSPI context. (Microsoft SQL Server, Error: 0)

Now,
1. I am able to connect from the same pc using SQL AUTH without any problems.
2. I have other PC's I added to the domain and I was able to login to the SQL server using windows auth without an issue.
3. on this PC I am unable to login using windows auth with ANY domain user, even with users that I confirm working from other PC's on the domain.
4. I tested ping , dns and such its all good.

How to proceed?
Thanks.
0
Comment
Question by:kelso109
5 Comments
 
LVL 6

Expert Comment

by:Dulton
ID: 40015120
Sounds like your new client PC may have a domain issue. It's not being trusted by the domain controller.


You mention that you can't connect with windows authentication... have you tried a SQL server login?  if you can connect with a SQL login (not windows credentials), it would reinforce that the client isn't being trusted by the Domain.
0
 
LVL 29

Accepted Solution

by:
becraig earned 500 total points
ID: 40015133
1.. Verify you do not have a duplicate SPN (This more seems like your issue)
Very detailed info on resolving spn issues:
http://social.technet.microsoft.com/wiki/contents/articles/717.service-principal-names-spns-setspn-syntax-setspn-exe.aspx

Your new computer might not be properly registered in the AD.

I would just disjoin and rejoin the domain and re-test
0
 

Author Comment

by:kelso109
ID: 40015187
Thanks, I will give it a try.
0
 
LVL 7

Expert Comment

by:Mohammed Tahir
ID: 40015205
It seems secure channel is broken, so disjoin and rejoin the PC from domain.


Tahir
0
 

Author Closing Comment

by:kelso109
ID: 40020447
di join and re join to the domain worked!
0

Featured Post

Is Your Active Directory as Secure as You Think?

More than 75% of all records are compromised because of the loss or theft of a privileged credential. Experts have been exploring Active Directory infrastructure to identify key threats and establish best practices for keeping data safe. Attend this month’s webinar to learn more.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I have a large data set and a SSIS package. How can I load this file in multi threading?
This article shows gives you an overview on SQL Server 2016 row level security. You will also get to know the usages of row-level-security and how it works
This videos aims to give the viewer a basic demonstration of how a user can query current session information by using the SYS_CONTEXT function
With the advent of Windows 10, Microsoft is pushing a Get Windows 10 icon into the notification area (system tray) of qualifying computers. There are many reasons for wanting to remove this icon. This two-part Experts Exchange video Micro Tutorial s…

910 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

20 Experts available now in Live!

Get 1:1 Help Now